Switch to using higher resolution (10km) GDPS data in Morecast
- Dominant language
- Python
- Stars
- 65
- Forks
- 11
- Avg merge
- 21h 25m
- Merged PRs (30d)
- 70
Description
**As a** *Forecaster* **I want** *GDPS models based with 10km resolution* **So That** *the GDPS values I'm considering are more accurate*
**Additional Context**
- When Morecast was implemented, the highest available resolution for GDPS was 15km in GRIB format. Environment Canada has since started publishing 10km resolution files in NetCDF format (.nc) files: https://dd.weather.gc.ca/model_gem_global/10km/
- We haven't used the NetCDF format before.
- There are also more model runs! There are now 4 model runs instead of just one.
- We should probably have a look at the new file format (a spike?) before estimating this story - maybe our assumptions are wrong, there's no documentation that I can find about these files.
**Acceptance Criteria**
- [ ] All new GDPS data I see in graphs, tables etc. in MoreCast are sourced from the 10km source.
- [ ] When looking at any GDPS data, it is clear what the source is (15km vs. 10km resolution)
Contributor guide
Research direction
Start by examining how Morecast currently obtains and labels the 15km GDPS GRIB data, then inspect the 10km NetCDF files at the Environment Canada source. Determine how the four model runs differ and identify the tests or graph and table paths that cover GDPS values. Done means all displayed GDPS data uses the 10km source and clearly identifies its resolution.
Written by the indexing model from the issue text.
Assessment
- Domain
- data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100