Release: static-wx v0.2.0

Changelog

  • Added Threatcast infographic with categorical hazard probabilities by @crhowell3 in #19
  • Performed project structural overhaul by @crhowell3 in #19
  • Modified temperature and precipitation display by @crhowell3 in #23
  • Improved severe weather indicator for forecast infographic by @crhowell3 in #24
  • Improved Threatcast infographic visuals by @crhowell3 in #25
  • Added Threatcast data entry form by @crhowell3 in #25

Synopsis

The v0.2.0 release introduces a new infographic: the Threatcast! This is a common graphic that weather stations will use when discussing severe weather potentials. It is usually shown a couple days before or even the day of a severe weather event. It gives a probabilistic breakdown of common severe weather phenomena, including tornadoes, wind, hail, and flooding. This is an example produced by static-wx:

The probabilities range from none to “HIGH”, and each category is based on the NOAA Storm Prediction Center (SPC) outlook probabilities.

  • MRGL = Marginal
  • SLGT = Slight
  • ENH = Enhanced
  • MDT = Moderate
  • HIGH = High

Unlike the 7-day forecast graphic which currently takes data from a YAML configuration file, the Threatcast graphic can be dynamically edited from the browser via a simple form!

When a value is updated in the dropdown, the infographic automatically updates. Similar to the 7-day forecast, there is a “Save as PNG” button that converts the graph into a PNG format and downloads it.

The project structure was also revamped, but this only affects development and does not impact the UI/UX at all.

With v0.2.0 now out, work will begin on v0.3.0 shortly. This will probably carry with it more infographics, and it may also introduce a form for dynamically updating the 7-day forecast data, thus rendering the YAML configuration obsolete. As I always say, I will post here once the update comes out. If you decide to test this out for yourself and discover any bugs, or if you desire a feature that isn’t added yet, please make a corresponding issue on the GitHub. Thanks, and I’ll be back with v0.3.0!