Zone Forecast

Today there’s no point forecast in San Diego, instead of seeing the backup zone forecast I get these wild forecasts.
When I paste my point forecast into the Weather.Gov site it gives me the zone forecast, but using the Saratoga templates with latest advforecast.php it doesn’t revert to the zone forecast. An example of what I see is listed below.
After years of no problem, this has occurred now several times over the last month.

Example of forecast text:

Tonight

Clear, with a low around 9.96921E+36. Heat index values as high as 9.96921E+36. Southwest wind around 1.1472352069703E+37 mph. Chance of precipitation is 9.96921E+36%. New rainfall amounts in excess of 4 inches possible.
Monday

Sunny, with a high near 9.96921E+36. Heat index values as high as 9.96921E+36. Southwest wind around 1.1472352069703E+37 mph. Chance of precipitation is 9.96921E+36%. New rainfall amounts in excess of 4 inches possible.
Monday Night

Mostly clear, with a low around 9.96921E+36. Heat index values as high as 9.96921E+36. Southwest wind around 1.1472352069703E+37 mph. Chance of precipitation is 9.96921E+36%. New rainfall amounts in excess of 4 inches possible.
Tuesday

Sunny, with a high near 9.96921E+36. Heat index values as high as 9.96921E+36. Southwest wind around 1.1472352069703E+37 mph. Chance of precipitation is 9.96921E+36%. New rainfall amounts in excess of 4 inches

Link to the latest forecast, although the point forecast may be back in effect when viewed: http://wx4mt.com/wxforecast.php

I’ve seen this condition previously and it appears to be a NWS issue and nothing involving the forecast scripts. Give it some time and it will most likely return to normal.

It usually does clear up after a day or so.
I thought I may have missed something in the latest script update.
Thanks for the response.

You can force a zone forecast load by using ?force=2 on the URL (with wxforecast.php or advforecast2.php).

Don’s correct. Sometimes really garbage data sneaks into the api for point forecasts, and the api returns it faithfully. When the point-forecasts are being loaded, generally an api request will result in a 4xx or 5xx HTTP response, and the script detects that and loads the zone instead. If the Zone is also not available, you’ll get the box saying no forecasts are available.

Good thing their ‘beta’ is still underway with api.weather.gov.

I think I’ll go with the zone forecasts until the “beta” is ready. I have had those wacky forecasts 3 or 4 times in the last month.

Thanks Ken :wink:

Also, you could revert to V4.02 of the script to avoid the beta entirely, and switch back to V5.02 when the NWS decides to actually implement the new forecast.weather.gov based on the API. Still unknown when that will occur.