Topic: Missing heat warning in forecast

[jgillett]

An excessive heat warning for Phoenix has been in effect for at least 2 days but is not showing up in the forecasts or alerts. Two other counties with the same warning do show up. Thoughts on why not here appreciated.

[saratogaWX]

Hard to tell.. currently both the point and Zone forecasts for Phoenix on api.weather.gov seem to be unavailable

<!-- advforecast2.php (JSON) - V5.02 - 22-May-2017 on PHP 5.6.11-->
<!-- RAW NWS URL: http://forecast.weather.gov/MapClick.php?CityName=Phoenix&state=AZ&site=PSR&textField1=33.646&textField2=-112.007&e=0&TextType=2 -->
<!-- zone=AZZ023 -->
<!-- corrected NWS API URL='https://api.weather.gov/points/33.646,-112.007/forecast' -->
<!-- curl fetching 'https://api.weather.gov/points/33.646,-112.007/forecast' -->
<!-- HTTP stats:  RC=500 dest=23.197.96.136 port=443 (from sce=192.168.1.104)
      Times: dns=0.031 conn=0.031 pxfer=0.078 get=0.234 total=0.312 secs -->
<!-- headers returned:
HTTP/1.1 500 Internal Server Error
Server: nginx
Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
Content-Type: application/problem+json
X-Powered-By: PHP/5.6.5
Cache-Control: no-cache
Access-Control-Allow-Origin: *
X-Server-ID: vm-lnx-nids-apiapp8.ncep.noaa.gov
X-Correlation-ID: a8db63c2-4481-432d-b5eb-321229aa5cb0
X-Request-ID: a8db63c2-4481-432d-b5eb-321229aa5cb0
Date: Wed, 07 Jun 2017 19:49:59 GMT
Connection: close
Vary: Accept
 -->
<!-- Oops.. point forecast unavailable RC=500 - using Zone instead -->
<!-- curl fetching 'https://api.weather.gov/zones/JSON-LD/AZZ023/forecast' -->
<!-- HTTP stats:  RC=404 dest=23.197.96.136 port=443 (from sce=192.168.1.104)
      Times: dns=0.000 conn=0.016 pxfer=0.031 get=0.235 total=0.266 secs -->
<!-- headers returned:
HTTP/1.1 404 Not Found
Server: nginx
Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
Content-Type: application/problem+json
X-Powered-By: PHP/5.6.5
Cache-Control: no-cache
Access-Control-Allow-Origin: *
X-Server-ID: vm-lnx-nids-apiapp12.ncep.noaa.gov
X-Correlation-ID: 7c5c0dc8-9a38-470c-bfb5-daca95bfa0e6
X-Request-ID: 7c5c0dc8-9a38-470c-bfb5-daca95bfa0e6
Date: Wed, 07 Jun 2017 19:49:59 GMT
Content-Length: 320
Connection: keep-alive
Vary: Accept
 -->

The production version at https://forecast.weather.gov/MapClick.php?lat=33.448377164000476&lon=-112.07403634999969 does show the warning.

[jgillett]

Thanks for the quick reply, Ken. Just spoke with the head forecaster at PSR and he's not seeing any problems there. I did send him your error output which he indicated he would forward to Salt Lake City.

[jgillett]

Am now getting "The detailed point forecast weather data is not currently available." message. On 23 Jan a message came out re: changes to zone numbers at PSR effective 4 Apr - http://www.nws.noaa.gov/os/notification/scn17-02psrzonechanges.htm. Maybe they're still messing around with those? One confusing aspect at that URL is the new zone IDs. What used to be AZZ023 for Phoenix is now listed as "AZ023    Greater Phoenix Area". Did they really drop the one "Z"?

Thanks.

[saratogaWX]

The api.weather.gov response of '500' to a point forecast query causes the script to try the zone forecast instead (and you get the "The detailed point forecast weather data is not currently available." message plus the iconized zone forecast).

I think the AZ023 is a typo on their part.. to match the other codes using the naming scheme it would be AZZ023 AFAIK

[jgillett]

I understand the messages. It was the missing "Z" that confused me.

Thanks, Ken.

[jgillett]

PSR just confirmed NWS messed up the SCN mailing.

Thanks.