Oooh... that is strange.
The JSON for the forecast via api.weather.gov shows
"periods": [
{
"number": 1,
"name": "Today",
"startTime": "2017-06-24T07:00:00-07:00",
"endTime": "2017-06-24T18:00:00-07:00",
"isDaytime": true,
"temperature": 98,
"temperatureUnit": "F",
"temperatureTrend": null,
"windSpeed": "-146 mph",
"windDirection": "N",
"icon": "https://api.weather.gov/icons/land/day/few?size=medium",
"shortForecast": "Sunny",
"detailedForecast": "Sunny, with a high near 98. North wind around -146 mph, with gusts as high as 1.1472352069703E+37 mph. New snow accumulation of 2.990763E+37 to 2.990763E+37 inches possible."
},
{
"number": 2,
"name": "Tonight",
"startTime": "2017-06-24T18:00:00-07:00",
"endTime": "2017-06-25T06:00:00-07:00",
"isDaytime": false,
"temperature": 56,
"temperatureUnit": "F",
"temperatureTrend": null,
"windSpeed": "-146 mph",
"windDirection": "N",
"icon": "https://api.weather.gov/icons/land/night/sct?size=medium",
"shortForecast": "Partly Cloudy",
"detailedForecast": "Partly cloudy, with a low around 56. North wind around -146 mph, with gusts as high as 1.1472352069703E+37 mph. New snow accumulation of 2.990763E+37 to 2.990763E+37 inches possible."
},
so it's an api.weather.gov issue I think.. the script just displays (without alteration) the "detailedForecast" value in the JSON for the text of the forecast.
Looks like they have an issue with the GFS->text conversion routines.
BTW, my point-forecast from the API appears ok, so it may be just an issue for some forecast points/areas.
Same issue shows on
https://forecast-v3.weather.gov/point/38.9541,-119.7657I clicked around on the foreacst-v3.weather.gov site in the Reno, NV WFO area, and all the ones tried had the same anomalies in the forecasts.