We shipped refreshed NWS gridpoints across the East Coast, rebuilt the Quality Alerts surface with a per-station forecast drawer, and made the Daily Insights CSV mathematically reproducible.

NWS gridpoints, refreshed for 61 East Coast stations

NWS occasionally extends a WFO’s grid domain, which can cause cached gridpoints to return forecasts for cells 18 to 80 kilometers from the actual station. We’ve refreshed 61 East Coast station gridpoints across six WFOs (OKX, BOX, CAR, ILM, MHX, PHI), and a nightly cache refresh at 21:30 UTC now catches future regrids within a day.

NWS scores for these stations are correct from the day of the refresh onward.

Quality Alerts, with a per-station forecast drawer

The Forecast Risks tab now has a Quality Alerts feature (formerly Data Issues). Email and UI are aligned: same rows, same values, same units, driven by the user’s unit-system preference. Per-row tooltips explain each flag. A “What counts as a Quality Alert?” modal documents the reason groups and value-rendering conventions. Pagination is 50 rows per page.

Clicking a row opens a side drawer with every forecast the active provider collected for that station on that create date — every lead time, both MOS and 24-hour pairs, including day-zero and beyond-max-days-out rows the alerts list excludes by design. Cells that tripped a check are ringed and tooltipped; rows with any issue are tinted. The flagged forecast and the rest of the provider’s forecasts for the same station are visible in one view.

A reproducible Daily Insights CSV

Daily Insights CSVs are now mathematically reproducible end-to-end. The smoothing constant ε in skill_ratio = (abs_diff + ε) / (market_avg + ε) is stated inline in the user’s display unit (0.5 °F / 0.278 °C / 1.852 km h⁻¹). The wind drilldown chart and table agree on the same skill-ratio values. Market-standard-deviation columns ship with three decimals. Z-score reconstructions from the CSV match the chart exactly.

A few smaller items:

• The Weather Channel and Weather Underground retired. We’ve stopped scoring both following IBM’s wind-down of the underlying data products. Methodology pages reflect the change.
• API key authentication on api.forecastwatch.com is now working as documented. If you previously tried a valid bearer token and got a 403, give it another try.
• Quality Digest invalidation totals are reported correctly per provider; a row-leak bug that occasionally produced values like 101%%%%% is fixed.