WXforum.net

Web Weather => Weather Website PHP/AJAX scripting => Topic started by: W3DRM on April 09, 2018, 06:01:47 PM

Title: NWS Forecasts down since April 5, 2018...
Post by: W3DRM on April 09, 2018, 06:01:47 PM
I have looked at other sites and see they are also showing the latest updates for the NWS Forecasts dated as Thursday, 05-April 2018. Is there a problem or have I missed an update or explanation somewhere?
Title: Re: NWS Forecasts down since April 5, 2018...
Post by: ValentineWeather on April 09, 2018, 06:27:43 PM
I looked at the clickable map for Reno area and it looks normal. https://www.weather.gov/rev/

Have you updated to latest advforecast2.php I'm using the older version
https://www.wxforum.net/index.php?topic=34110.msg346446#msg346446
Title: Re: NWS Forecasts down since April 5, 2018...
Post by: saratogaWX on April 09, 2018, 06:32:39 PM
Don,
You are using the V5.05 (JSON) advforecast2.php.  Here's what it is saying in the view-source of wxforecast.php
Quote
<!-- advforecast2.php (JSON) - V5.05 - 27-Feb-2018 on PHP 7.2.3-->
<!-- RAW NWS URL: https://forecast.weather.gov/point/39.038556,-119.721083 -->
<!-- zone=NVZ003 -->
<!-- corrected NWS API URL='https://api.weather.gov/points/39.0386,-119.7211/forecast' -->
<!-- loaded cache file ./cache/forecast-NVZ003-0-json.txt - 10593 bytes -->
<!-- point forecast more than 18hrs old (age h:m:s is 95:59:53) .. use Zone forecast instead -->
<!-- curl fetching 'https://api.weather.gov/zones/JSON-LD/NVZ003/forecast' -->
<!-- HTTP stats:  RC=200 dest=23.202.224.24 port=443 (from sce=198.71.62.63)
      Times: dns=0.028 conn=0.059 pxfer=0.125 get=0.033 total=0.158 secs -->
<!-- loaded (Zone forecast) https://api.weather.gov/zones/JSON-LD/NVZ003/forecast - 10593 bytes -->
<!-- wrote cache file ./cache/forecast-NVZ003-0-json.txt -->
<!-- meta info re: point='39.0386,-119.7211' zone='NVZ003' metacache= './cache/forecast-NVZ003-0-json-meta.txt' -->
<!-- metaZoneURL='https://api.weather.gov/zones/forecast/NVZ003' -->
<!-- loaded meta info from ./cache/forecast-NVZ003-0-json-meta.txt -->
<!-- META
Array
(
    [city] => 2 Miles S Johnson Lane
    [state] => NV
    [point] => 39.0386,-119.7211
    [forecastOfficeURL] => http://api.weather.gov/offices/REV
    [forecastZoneURL] => http://api.weather.gov/zones/forecast/NVZ003
    [forecastZone] => NVZ003
    [countyZoneURL] => http://api.weather.gov/zones/county/NVC005
    [countyZone] => NVC005
    [fireWeatherZoneURL] => http://api.weather.gov/zones/fire/NVZ450
    [fireWeatherZone] => NVZ450
    [timeZone] => America/Los_Angeles
    [radarStation] => KRGX
    [zoneName] => Greater Reno-Carson City-Minden Area
    [WFOname] => Reno, NV
)
 -->
<!-- ZONE forecast processing -->
so the problem is with your local NWS.. the gridpoint forecast for you has not been updated by them... or the cache hasn't refreshed.

I ran your wxforecast.php?force=1 and got
Quote
<!-- advforecast2.php (JSON) - V5.05 - 27-Feb-2018 on PHP 7.2.3-->
<!-- RAW NWS URL: https://forecast.weather.gov/point/39.038556,-119.721083 -->
<!-- zone=NVZ003 -->
<!-- corrected NWS API URL='https://api.weather.gov/points/39.0386,-119.7211/forecast' -->
<!-- curl fetching 'https://api.weather.gov/points/39.0386,-119.7211/forecast' -->
<!-- note: fetched 'https://api.weather.gov/gridpoints/REV/43,83/forecast' after redirect was followed. -->
<!-- HTTP stats:  RC=200 dest=23.202.224.24 port=443 (from sce=198.71.62.63)
      Times: dns=0.000 conn=0.000 pxfer=0.000 get=0.877 total=0.877 secs -->
<!-- loaded point-forecast https://api.weather.gov/points/39.0386,-119.7211/forecast - 11138 bytes -->
<!-- wrote cache file ./cache/forecast-NVZ003-0-json.txt -->
<!-- meta info re: point='39.0386,-119.7211' zone='NVZ003' metacache= './cache/forecast-NVZ003-0-json-meta.txt' -->
<!-- metaZoneURL='https://api.weather.gov/zones/forecast/NVZ003' -->
<!-- loaded meta info from ./cache/forecast-NVZ003-0-json-meta.txt -->
<!-- META
Array
(
    [city] => 2 Miles S Johnson Lane
    [state] => NV
    [point] => 39.0386,-119.7211
    [forecastOfficeURL] => http://api.weather.gov/offices/REV
    [forecastZoneURL] => http://api.weather.gov/zones/forecast/NVZ003
    [forecastZone] => NVZ003
    [countyZoneURL] => http://api.weather.gov/zones/county/NVC005
    [countyZone] => NVC005
    [fireWeatherZoneURL] => http://api.weather.gov/zones/fire/NVZ450
    [fireWeatherZone] => NVZ450
    [timeZone] => America/Los_Angeles
    [radarStation] => KRGX
    [zoneName] => Greater Reno-Carson City-Minden Area
    [WFOname] => Reno, NV
)
 -->
<!-- point forecast processing -->
and so a good gridpoint forecast was obtained.

Your advforecast2.php has
Code: [Select]
$refreshTime = 600; so it should be checking every 10 minutes for a new forecast and download it.  Don't know why it took 95hrs to get a new good forecast  :roll:  :shock:
Title: Re: NWS Forecasts down since April 5, 2018...
Post by: W3DRM on April 10, 2018, 12:26:40 AM
Ken - I am really puzzled over this one. I cannot get it to show a current forecast. I still see the 5 April date. I also looked at your NWS Forecast on your website and see a similar condition. See the attached screen capture. This was made using Pale Moon with all history and cache cleared. Makes no sense to me. I've tried using numerous other browsers and get the same results.

I did access using wxforecast.php?force=1 on my site and now it is showing current data on all of my browsers. It must have been an issue with my cache files but I don't understand why it happened. Will watch it for a while to see what happens. BTW, looking at your NWS forecast on your site still shows the 5-April date. Not sure where to clear out that cached file, if that is what the problem is.
Title: Re: NWS Forecasts down since April 5, 2018...
Post by: DaculaWeather on April 10, 2018, 05:56:54 AM
April 6, 3:51 am for me here in Atlanta. Doesn't matter if it's point or zone. Had the same problem with Florida forecast when I was there at the end of last week.

I sent another message to the NWS yesterday
Title: Re: NWS Forecasts down since April 5, 2018...
Post by: Jasiu on April 10, 2018, 07:52:18 AM
I'm seeing generally flaky results over the last few days for BOS. I can now get a point forecast again but haven't been able to pull a forecast discussion since April 7. There's a reason this is still in beta....
Title: Re: NWS Forecasts down since April 5, 2018...
Post by: DaculaWeather on April 10, 2018, 09:27:51 AM
Point is now working for me, zone is not. It went even further back in time to March 22.
Title: Re: NWS Forecasts down since April 5, 2018...
Post by: 92merc on April 10, 2018, 10:36:52 AM
I noticed mine was down late last night as well.  Still down this morning.  I flipped over to the V4 of the forecast and that is working normally.
Title: Re: NWS Forecasts down since April 5, 2018...
Post by: LFWX on April 10, 2018, 10:04:19 PM
Similar issues here.

I was stuck on a forecast for April 2...updated to version 5.05...now the forecast is current, but always ZONE.
Title: Re: NWS Forecasts down since April 5, 2018...
Post by: ValentineWeather on April 10, 2018, 10:58:50 PM
I've had better luck with 4.03. Occasionally have to force update but not near the 5.05 problems.

Title: Re: NWS Forecasts down since April 5, 2018...
Post by: LFWX on April 10, 2018, 11:54:28 PM
I've had better luck with 4.03. Occasionally have to force update but not near the 5.05 problems.

Here is 4.03 if you want to try

Thanks.

Not sure why, but that crashed my page.

I discovered I still had a copy of V4.01 and tried it, but it just left blank spaces where forecast info should have been.

Long story short, I'm back to V5.05 until I figure out what I did to mess things up...
Title: Re: NWS Forecasts down since April 5, 2018...
Post by: saratogaWX on April 11, 2018, 12:13:10 AM
Any version below V4.03 won't work with the current https-only weather.gov since the fetchUrlWithoutHanging() function used http sockets only.

The 'official' V4.03 is available at https://saratoga-weather.org/advforecast2-V4.03.php?sce=view
and I'll leave it available until it no longer works when weather.gov switches to the API-based design (sometime later this year, they say).
Title: Re: NWS Forecasts down since April 5, 2018...
Post by: daybreak on April 11, 2018, 10:11:46 AM
Good Morning,

I noticed my forecast wasn't working correctly either, it has March 20 for a date.  http://www.daybreakimagery.com/weather/forecast.php (http://www.daybreakimagery.com/weather/forecast.php) It says the point forecast isn't available but I checked on the web and it is. 

Ken my old link in the script to the forecast was: "http://forecast.weather.gov/MapClick.php?CityName=Alma&state=IL&site=LSX&textField1=38.7229&textField2=-88.9101&e=0&TextType=2"

I checked the current point forecast and it was this:  "https://forecast.weather.gov/MapClick.php?lat=38.717&lon=-88.9157&unit=0&lg=english&FcstType=text&TextType=2"

I changed it but it is still showing March 20.  Any thoughts?

Thank you,

Richard
Title: Re: NWS Forecasts down since April 5, 2018...
Post by: Jasiu on April 11, 2018, 11:14:05 AM
In case it isn't clear, anyone using the newest JSON code is subject to periodic flakiness because that API is still in beta phase. If you don't want to have to monitor this and deal with that flakiness, use the 4.03 version until the JSON API is officially up.
Title: Re: NWS Forecasts down since April 5, 2018...
Post by: DaculaWeather on April 11, 2018, 11:26:19 AM
And according to my source at the NWS, it's not the API that's not working correctly, it's when each office updates the forecast, it's not populating things correctly, there is something internal going on.

Or so they say...
Title: Re: NWS Forecasts down since April 5, 2018...
Post by: saratogaWX on April 11, 2018, 12:34:38 PM
Good Morning,

I noticed my forecast wasn't working correctly either, it has March 20 for a date.  http://www.daybreakimagery.com/weather/forecast.php (http://www.daybreakimagery.com/weather/forecast.php) It says the point forecast isn't available but I checked on the web and it is. 

Ken my old link in the script to the forecast was: "http://forecast.weather.gov/MapClick.php?CityName=Alma&state=IL&site=LSX&textField1=38.7229&textField2=-88.9101&e=0&TextType=2"

I checked the current point forecast and it was this:  "https://forecast.weather.gov/MapClick.php?lat=38.717&lon=-88.9157&unit=0&lg=english&FcstType=text&TextType=2"

I changed it but it is still showing March 20.  Any thoughts?

Thank you,

Richard
Sigh.  Your URL for the point-printable forecast should be
https://forecast.weather.gov/MapClick.php?lat=38.717&lon=-88.9157&unit=0&lg=english&FcstType=text&TextType=2

so it is compatible with the V4.03 and V5.05 versions of advforecast2.php.  That way, you can use either version of the script as it moves you.

Both Jasiu and DaculaWeather are also correct.  I noticed that the 'Coming soon...' type banner is now on the main forecast.weather.gov page saying
Quote
Notice of NWS' New Version of Forecast
A new version of Forecast is coming soon!
Click here to visit the new site for details.
and the https://forecast-v3.weather.gov/documentation?redirect=legacy site does say
Quote
Preview of NWS' New Version of Forecast
This preview is not operational and should not be used for support decisions.
but doesn't give a timeframe for implementation (nor has anything come along on the NWS notification emails).

So... I'll keep distributing the V5.05 (JSON) format advforecast2.php script as the main one (since it will work before and after they cutover to the new design).  For those not wanting to have the stress of occasionally having the API misbehave, you can revert to the V4.03 version, then convert when the NWS converts their site (you'll know because the V4.03 script will stop working).

Download:  V4.03 at https://saratoga-weather.org/advforecast2-V4.03.php?sce=view
Download:  V5.05 at https://saratoga-weather.org/advforecast2.php?sce=view  (and in the Base-USA template distribution)
Title: Re: NWS Forecasts down since April 5, 2018...
Post by: W3DRM on April 11, 2018, 01:23:03 PM
Quick comment and a question:

I just downloaded the v4.03 code and uploaded it to my website making no changes to it at all. I am using Ken's template, as I always have. When I did this, I now only see the very top of the forecast page with no data at all. I have reverted back to v5.05 and everything returned to normal.

The question is, is there something I need to do to v4.03 to make it work? All other code is up to date according to the check-fetch-time routine.

[EDIT]
You can the issue by comparing the two results below:
If I am supposed to be able simply exchange one piece of code for another, why the different results? I must be missing something.









Title: Re: NWS Forecasts down since April 5, 2018...
Post by: daybreak on April 11, 2018, 02:00:28 PM
Thanks Ken for the information.  I'll keep an eye on it.

Richard
Title: Re: NWS Forecasts down since April 5, 2018...
Post by: Jasiu on April 11, 2018, 02:36:18 PM
I just downloaded the v4.03 code and uploaded it to my website making no changes to it at all. I am using Ken's template, as I always have. When I did this, I now only see the very top of the forecast page with no data at all. I have reverted back to v5.05 and everything returned to normal.

The question is, is there something I need to do to v4.03 to make it work? All other code is up to date according to the check-fetch-time routine.
[EDIT]


See Ken's comment above regarding the URL.  It has to be of the "MapClick" variety to work with both versions.

This is set in the $SITE['fcsturlNWS'] variable in the settings file.
Title: Re: NWS Forecasts down since April 5, 2018...
Post by: saratogaWX on April 11, 2018, 02:57:59 PM
Quick comment and a question:

I just downloaded the v4.03 code and uploaded it to my website making no changes to it at all. I am using Ken's template, as I always have. When I did this, I now only see the very top of the forecast page with no data at all. I have reverted back to v5.05 and everything returned to normal.

The question is, is there something I need to do to v4.03 to make it work? All other code is up to date according to the check-fetch-time routine.

[EDIT]
You can the issue by comparing the two results below:
  • https://www.carsonvalleyweather.com/advforecast2-v5.05.php
  • https://www.carsonvalleyweather.com/advforecast2-v4.03.php
If I am supposed to be able simply exchange one piece of code for another, why the different results? I must be missing something.

Your forecast URLs in your 4.03 version are all in the format https://forecast.weather.gov/point/39.038556,-119.721083
which is for the JSON 5.05 version ONLY.
You have to use the MapClick.php forecast URL format to use with either script.  The 4.03 script can't handle the /point/<lat>,<long> format at all.
Title: Re: NWS Forecasts down since April 5, 2018...
Post by: W3DRM on April 12, 2018, 02:32:21 PM
Thanks guys! I just switched back to the mapclick.php format in my settings.php and all is well again on v4.03. I had forgotten about that format change.

[EDIT] Just thinking aloud with the following comment...

It would be nice if we could have a piece of code that would automatically pick the correct format to use in the settings.php file, based on which version of advforecast2.php is being used. With something like that, we wouldn't have to worry about which should be used. I'm no programmer but, am wondering if such a version detection routine would be possible? Ken's version detection routine (check-fetch-times.php) seems to be able to do that which is what triggered this thought.
Title: Re: NWS Forecasts down since April 5, 2018...
Post by: Jasiu on April 12, 2018, 05:30:31 PM
Whichever version of advforecast2.php you use does pick the right format, so long as it is in the MapClick format in the settings file. If you use that format, you don't have to modify it to use the 5.0* versions.

The code show this in the comments (view source) when you run the JSON version:

Code: [Select]
<!-- RAW NWS URL: https://forecast.weather.gov/MapClick.php?CityName=Lexington&state=MA&site=MTR&textField1=42.4399&textField2=-71.2405&e=1&TextType=2 -->

<!-- corrected NWS API URL='https://api.weather.gov/points/42.4399,-71.2405/forecast' -->
Title: Re: NWS Forecasts down since April 5, 2018...
Post by: saratogaWX on April 12, 2018, 06:05:28 PM
Correct, the advforecast2.php V5.x version does automatically translate the MapClick.php URLs to point forecast urls, so keep the URLs in that format until after the NWS changes the forecast.weather.gov to use the new addressing scheme.  Then I have built-in a quick converter in the script to mass-convert all the URLs to the V3 forecast.weather.gov format for an easy one-time conversion.  But.. DON'T convert until the NWS fully implements their new site.. stick with the MapClick.php URLs instead, and you can freely switch advforecast2.php V4.0X and V5.0X scripts as you like (or as the flaky API moves you to switch back).
Title: Re: NWS Forecasts down since April 5, 2018...
Post by: W3DRM on April 13, 2018, 01:02:30 AM
Okay, I think all of this is finally getting through this thick skull of mine. As I said, I'm no programmer and simply wasn't aware of all of the nuances of this package. I am going to stick with the MapClick.php url's and v4.0x for the time being. Will watch the WXFORUM for any updates/changes in the future.

Ken - sorry for causing such a stir on this topic. you have always done such a great job and I am not faulting anyone here. It must be very frustrating for you to have the NWS feeds constantly changing without much, if any, notice.
Title: Re: NWS Forecasts down since April 5, 2018...
Post by: saratogaWX on April 13, 2018, 01:20:24 PM
No worries, Don.  It has been complicated trying to stay ahead of the on-again/off-again/no-words-from-NWS conversion schedule with their forecast.weather.gov redesign.

I knew over a year ago (based on their preliminary documentation) that the MapClick.php form of the URL was going to be deprecated on their new site -- that's why I put in an auto-convert function in the JSON script (to convert MapClick format to /point format) just so everyone could LEAVE the existing URLs while the turmoil of the website conversion was underway.   AFTER their conversion is fully done, I also have a routine in the JSON script to present what your Settings.php entries should be with the new URLs (for easy conversion in the future).

What I wasn't expecting was for them to tweak the EXISTING forecast.weather.gov HTML instead of just completing their cutover to the new design.  Sigh...  Guess I'll have to keep up with both V4 and V5 updates for the forseeable futuire.  No problem.  Hakuna Matatta. :)
Title: Re: NWS Forecasts down since April 5, 2018...
Post by: W3DRM on April 13, 2018, 03:50:29 PM
The Lion King! - Hakuna Matatta - No Worries  :D

With you around, that is a very true saying! Thanks again.
Title: Re: NWS Forecasts down since April 5, 2018...
Post by: 92merc on April 13, 2018, 05:55:47 PM
Looks like my V5 forecast just started working.
Title: Re: NWS Forecasts down since April 5, 2018...
Post by: saratogaWX on April 14, 2018, 01:59:33 PM
I've done another set of enhancements to advforecast2.php V5.07 - 14-Apr-2018:

1) I've added an URL cache (forecast-URLcache.txt) for the point->gridpoint forecast to skip the access to api.weather.gov for a 302 redirect they provide for a /points/ request to a /gridpoints/ request.  The URL cache file will auto-update as needed.  This saves one HTTPS access when loading a freshened forecast.
2) I've added the WFO phone and email contact info and details about the gridpoint involved to the notice box when a Zone forecast is displayed due to a point forecast not being available.  The box now contains info like
Quote
The detailed point forecast weather data is not currently available.
The zone forecast data for CAZ513 (Santa Clara Valley Including San Jose) will be displayed
until the point forecast data is again available.
If this persists, contact the NWS San Francisco Bay Area/Monterey, CA WFO
at (831) 656-1725 or email at w-mtr.webmaster@noaa.gov
to have them update the point forecast for /gridpoints/MTR/97,101 on api.weather.gov
(area in italics is added). This allows you to contact the responsible NWS field office with the details about which gridpoint forecast is failing.. hopefully this will reduce the time to get the point forecast back.  I was hesitant to include the NWS phone and email, but after checking the real weather.gov pages, they already display that info in the footer, so it is 'public'.  Be aware that calling the phone number may result in a voice-response system, and not a person, but the voice may give an additional number to call to talk with a forecaster.. use that one instead.  Emails to the address shown may take longer to resolve those stale/unavailable gridpoint forecast issues.

Standalone users download from the script page (https://saratoga-weather.org/scripts-carterlake.php#carterlake)
Template users use the update tool page (https://saratoga-weather.org/wxtemplates/updates.php) with a query Base-USA, Plugin-*, 14-Apr-2018

Hopefully this update will improve (a bit) the load-time for the script by eliminating one HTTPS access and help you to resolve stale point forecasts easily.

Best regards,
Ken
Title: Re: NWS Forecasts down since April 5, 2018...
Post by: mikeym2m on April 15, 2018, 11:49:10 AM
Thanks Ken!  :grin:
Title: Re: NWS Forecasts down since April 5, 2018...
Post by: gwwilk on April 15, 2018, 01:06:58 PM
Thanks very much, Ken.  Note and appreciate the faster load times! \:D/ =D&gt; \:D/
Title: NWS Forecast acting up again
Post by: daybreak on May 03, 2018, 07:24:39 AM
Hi Ken,

My local NWS must be changing things again.  My forecast has been acting up the past couple of days.  http://www.daybreakimagery.com/weather/ (http://www.daybreakimagery.com/weather/) or this page http://www.daybreakimagery.com/weather/forecast.php (http://www.daybreakimagery.com/weather/forecast.php).

Yesterday the home page showed an old forecast from March and this morning it is showing yesterday's forecast.  Both pages are extremely slow to load.  I was running Version 5.05 but changed to Version 5.07, but no change.

Thanks for your help.

Richard
Title: Re: NWS Forecast acting up again
Post by: Jasiu on May 03, 2018, 07:54:20 AM
Hi Ken,

My local NWS must be changing things again.  My forecast has been acting up the past couple of days.  http://www.daybreakimagery.com/weather/ (http://www.daybreakimagery.com/weather/) or this page http://www.daybreakimagery.com/weather/forecast.php (http://www.daybreakimagery.com/weather/forecast.php).

Yesterday the home page showed an old forecast from March and this morning it is showing yesterday's forecast.  Both pages are extremely slow to load.  I was running Version 5.05 but changed to Version 5.07, but no change.

Thanks for your help.

Richard

Repeated from earlier in the thread... the 5.** version of the file uses a beta service from the NWS. It IS going to be flaky. If you want stable, stick with the 4.** until the new API has been declared ready for action.
Title: Re: NWS Forecasts down since April 5, 2018...
Post by: daybreak on May 03, 2018, 08:49:49 AM
Ok thanks.

Richard
Title: Re: NWS Forecasts down since April 5, 2018...
Post by: ValentineWeather on May 03, 2018, 11:27:33 AM
I tried the new script it still gives the weird numbers. Back on the older script at least I get zone numbers.

 [ You are not allowed to view attachments ]
Title: Re: NWS Forecasts down since April 5, 2018...
Post by: saratogaWX on May 06, 2018, 10:24:32 AM
That is a previously observed issue with the NWS API -- sometimes bad data is loaded in their servers from the GFS forecast.  Sometimes it's just temperatures.. other times it's wind speeds.

Not something you can fix except by calling the local NWS WFO and alerting them to the problem.  Version 5.07 of the script now pulls WFO info and you can see it by doing a view-source on the forecast page -- it will appear in HTML comments like this for my forecast
Quote
<!-- advforecast2.php (JSON) - V5.07 - 14-Apr-2018 on PHP 7.2.4-->
<!-- RAW NWS URL: http://forecast.weather.gov/MapClick.php?lat=37.26383&lon=-122.02301460000001&unit=0&lg=english&FcstType=text&TextType=2 -->
<!-- zone=CAZ513 -->
<!-- loaded URLcache from ./cache/forecast-URLcache.txt with 5 entries -->
<!-- corrected NWS API URL='https://api.weather.gov/points/37.2638,-122.023/forecast' -->
<!-- loaded cache file ./cache/forecast-CAZ513-0-json.txt - 9901 bytes -->
<!-- meta info re: point='37.2638,-122.023' zone='CAZ513' metacache= './cache/forecast-CAZ513-0-json-meta.txt' -->
<!-- metaZoneURL='https://api.weather.gov/zones/forecast/CAZ513' -->
<!-- loaded meta info from ./cache/forecast-CAZ513-0-json-meta.txt -->
<!-- META
Array
(
    [city] => Saratoga
    [state] => CA
    [point] => 37.2638,-122.023
    [forecastOfficeURL] => https://api.weather.gov/offices/MTR
    [forecastZoneURL] => https://api.weather.gov/zones/forecast/CAZ513
    [forecastZone] => CAZ513
    [forecastHourlyURL] => https://api.weather.gov/points/37.2638,-122.023/forecast/hourly
    [forecastGridDataURL] => https://api.weather.gov/gridpoints/MTR/97,101
    [observationStationsURL] => https://api.weather.gov/points/37.2638,-122.023/stations
    [countyZoneURL] => https://api.weather.gov/zones/county/CAC085
    [countyZone] => CAC085
    [fireWeatherZoneURL] => https://api.weather.gov/zones/fire/CAZ513
    [fireWeatherZone] => CAZ513
    [timeZone] => America/Los_Angeles
    [radarStation] => KMUX
    [zoneName] => Santa Clara Valley Including San Jose
    [WFOname] => San Francisco Bay Area/Monterey, CA
    [WFOphone] => (831) 656-1725
    [WFOemail] => w-mtr.webmaster@noaa.gov

)
 -->
Since you've reverted to the V4.03 version, you'll likely not see that issue since it is api.weather.gov specific.