This PR implements "first draft" versions of the following map + chart/table ARDAC items:
Deep Winter Days
Summer Days
Cold Day Threshold
Hot Day Threshold
Warm Spell Duration Index
Cold Spell Duration Index
Maximum 1-day Precipitation
Maximum 5-day Precipitation
Consecutive Dry Days
Consecutive Wet Days
Heavy Precipitation Days
Wet Days Per Year
Climate Protection from Spruce Beetles
Landfast Sea Ice
Degree Days Below 65°F
Degree Days Below 0°F
Freezing Index
Thawing Index
My understanding is that we will not be using our current set of WRF-based coverages & API endpoints, which impacts the following ARDAC items, but I've kept them in this PR for illustration/discussion purposes:
Degree Days Below 65°F
Degree Days Below 0°F
Freezing Index
Thawing Index
Some questions we'll need to think about generally in the future:
Do we want more/different layers for our maps? Currently most maps show a historical layer and two (mid-century and late-century) NCAR CCSM RCP 8.5 layers.
How much do we want our charts to correspond exactly with our map layers? For example, our degree-days-based components show map layers averaged over 30-year eras, but the charts average the data by decades.
Should the "gimme widget" provide CSV/JSON links to the data will full granularity (individual years where available?) or should we provide links that are pre-summarized into eras to match the map layers, where possible?
How do the map colormaps look? So far, most maps use the same number of color buckets, but with thresholds tailored towards the particular dataset. I'm currently reusing the same two color palettes for most maps, one for "warm" data and one for "cold" data. A few maps use exponential rather than linear color bucket thresholds where it seemed necessary to do so.
Also, there is a lot of code duplication in this PR that I haven't gotten around to improving yet. I think we can consolidate a lot of Leaflet configuration / data packaging code to considerable degree in the future, but probably in subsequent PRs.
To test, set the RASDAMAN_URL environment variable to point to Apollo directly. This is prevent WMS caching issues:
Each URL above has multiple map layers to try, and a lat/lon input that generates either a chart or a table. Try all of these! And note that all 18 items listed above also now use the new community + lat/lon place selector component.
This PR implements "first draft" versions of the following map + chart/table ARDAC items:
My understanding is that we will not be using our current set of WRF-based coverages & API endpoints, which impacts the following ARDAC items, but I've kept them in this PR for illustration/discussion purposes:
Some questions we'll need to think about generally in the future:
Also, there is a lot of code duplication in this PR that I haven't gotten around to improving yet. I think we can consolidate a lot of Leaflet configuration / data packaging code to considerable degree in the future, but probably in subsequent PRs.
To test, set the
RASDAMAN_URLenvironment variable to point to Apollo directly. This is prevent WMS caching issues:Then:
Then, visit each of the following URLs!
http://localhost:3000/item/indicator-dw http://localhost:3000/item/indicator-su http://localhost:3000/item/indicator-cd http://localhost:3000/item/indicator-hd http://localhost:3000/item/indicator-wsdi http://localhost:3000/item/indicator-csdi http://localhost:3000/item/indicator-rx1day http://localhost:3000/item/indicator-rx5day http://localhost:3000/item/indicator-cdd http://localhost:3000/item/indicator-cwd http://localhost:3000/item/indicator-r10mm http://localhost:3000/item/wet-days-per-year http://localhost:3000/item/climate-beetle-protection http://localhost:3000/item/landfast-sea-ice http://localhost:3000/item/dd-below-65 http://localhost:3000/item/dd-below-0 http://localhost:3000/item/freezing-index http://localhost:3000/item/thawing-index
Each URL above has multiple map layers to try, and a lat/lon input that generates either a chart or a table. Try all of these! And note that all 18 items listed above also now use the new community + lat/lon place selector component.