bcgov / bcgov/wps

MoreCast 2.0: Connect pipeline to push data into WF1

Open
#2,580 0 comments 0 reactions 0 assignees View on GitHub
4Refinement User Story
Dominant language
Python
Stars
65
Forks
11
Avg merge
21h 25m
Merged PRs (30d)
70

Description

**As a** weather forecaster

**I need** a feature to push a forecast into the WildfireOne Weather App

**So That** I no longer have to enter values manually.

**Acceptance Criteria**
- [ ] Given I have prepared and reviewed a weather forecast for each of the stations in my Fire Centre, When I select a submit button, Then the forecast data are published in the WildfireOne weather app.
- [ ] Given I submit a forecast, When the data are pushed to WildfireOne, Then I receive a message that either confirms the data were successfully published or alerts me that WildfireOne is non-responsive. If WildfireOne is non-responsive, I should have the option to save my forecast and submit later.
- [ ] Given I publish a new forecast that overlaps a previous forecast, When the data are pushed to WildfireOne, Then the old forecast is overwritten with the new forecast.

**Additional Context**
- An API may need to be developed by the Wildfire One team. This is apparently a top priority in the Weather App backlog.
- Extensive communication and collaboration will be required with the Wildfire One team. This work needs to start asap to ensure it is completed before fire season.

**Definition of Done**
https://github.com/bcgov/wps/wiki/Definition-of-Done

Contributor guide

Open the contributing guide

Research direction

No files or tests are named. Start by coordinating with the WildfireOne team to define the API contract and failure behavior, then trace the existing forecast submission flow and identify the UI entry point for publishing. Done means forecasts can be submitted, status or non-response is reported with later retry available, and overlapping forecasts replace older data.

Written by the indexing model from the issue text.

Assessment

Tech stack
fastapi, python, react
Domain
api, backend-api-design, frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.