coreypieper

Just went through and filled it in. Looks good to me.

I've spoken to Digital Strategy Lead in NOAA's Office of the Chief Information Officer. Long story short: - NOAA currently does not have schedules for web-based content - They've asked...

Note from NOAA CIO office today: > I have a meeting with NOAA Records Management next week to talk high-level digital retention - we will discuss creating NOAA retention schedules...

My NOAA CIO POC on this had a meeting with NOAA Records Management to talk about high-level digital retention - including creating NOAA retention schedules for web records and CMS...

JIRA ticket: https://nco-jira.atlassian.net/browse/API-543

Wind gusts info is now in #876 . There it notes that we should display gusts in the observation any time they're available in the obs API endpoint. Dew point...

New example: [North Platte, NE _ Weather.gov _ National Weather Service.pdf](https://github.com/weather-gov/weather.gov/files/15224070/North.Platte.NE._.Weather.gov._.National.Weather.Service.pdf) Currently, severe/tor watches (which are unique, as they're issued by SPC vs. WFO's) in beta, have the impacted counties...

Another: [Pierre, SD _ Weather.gov _ National Weather Service.pdf](https://github.com/weather-gov/weather.gov/files/15224503/Pierre.SD._.Weather.gov._.National.Weather.Service.pdf) API output: [active (3).txt](https://github.com/weather-gov/weather.gov/files/15224504/active.3.txt)

@shadkeene and I spoke today about this, and we're comfortable with sticking w/ just T for now and evaluating as we go. If we do have the opportunity to weight...

Right now only T is considered and the failure rate is acceptably low. Shad and I agreed on this order of importance: - T - Wind - Dewpoint (regarding heat...