Topic: digitalDWML XML hourly forecasts returning empty data?

[lem436]

eg: https://forecast.weather.gov/MapClick.php?lat=38.78&lon=-77.52&FcstType=digitalDWML

Returns valid XML but all the data elements are empty. Other MapClick XML forecasts still seem to have good data.

I wonder if this is nws finally beginning the retirement of the XML 'api', or an actual bug I should complain about (and if the latter, where?)

Anyone heard anything?

[openvista]

It would appear that, perhaps, the API forecast has finally launched. See https://www.weather.gov/documentation/services-web-api for more info. Previously (as of yesterday!) that link said that only the alerts endpoints were considered production level. But today they added a bunch of new text to the overview which makes it seem like they have gone ahead with all the endpoints including forecasts.

My hourly forecasts (marquetteweather.com) stopped working the morning of May 1st. My wife works in payroll taxes and can tell you that the federal government considers April to be the end of the first quarter -- probably because of the tax deadline on the 15th. So it could just be that they meant to get this out by the 2nd quarter of the year.

Ultimately, I'm guessing. But I've never seen the DWML hourly go down for 36 hours before. Sure would be nice if they were clear about what's (been) going on (for the past 5 years or so) with the API.

[openvista]

So, to your point, yes it seems they are sunsetting all non-HTML code on the website. I found this: https://rapidapi.com/theapiguy/api/national-weather-service/details. Note where it says at the top that the public-facing weather.gov website will only be returning HTML from now on. You cannot request XML (or JSON). Seems you have to use the API.

Good news is that it's free. Bad news is that it's a very different animal.

[lem436]

yeah, I started conversion work to move to the json API, not too bad.

It's just odd... Keeping the xml button on the forecast webpage and continuing to return xml with no data is an ...interesting choice

I found a contact point for the xml api and sent then an email, will post here if there's a response.

[openvista]

According to this: https://www.weather.gov/idp/forecastmigration

The digitalDWML (XML) and digitalJSON forecast types are listed as "known issues" that occurred when they migrated the forecasting website to a new platform. So, perhaps, those formats will be fixed at some point?? There's NO mention of the API on this page or mention that those features are deprecated.

It's confusing when you couple that information with what I've posted earlier from api.weather.gov.

¯\_(ツ)_/¯

[openvista]

Looks like DWML feed will be restored Monday morning (assuming no weather emergencies). See news at the top of https://www.weather.gov/idp/forecastmigration

[saratogaWX]

Two new messages on the NWS announcement list regarding DWML feeds:

SCN24-50: Migration of JSON and DWML Data Services to NWS’s API Application at api.weather.gov and Removal from forecast.weather.gov, Effective June 27, 2024
See: https://www.weather.gov/media/notification/pdf_2023_24/scn24-50_removal_of_digital_projects_from_forecast.pdf

SCN24-44: Updated: Migrate NWS weather.gov Website to New Infrastructure and Decommission Websites/URLs, Effective June 4, 2024
see: https://www.weather.gov/media/notification/pdf_2023_24/scn24-44_website_migration_legacy_decommission_aaa.pdf

The first PDF link has the details on what has to change in scripts using the MapClick.php DWML to use the api.weather.gov, and it's not a simple one-URL replacement, so buckle in...

[JPB]

SIGH. One of the solaces I've had this past year as I deal with health issues in extended family is making little updates and changes to my weather scripts. I've been extremely busy with the fore-mentioned issue this past week, then I ran into the URL change discussed in part '2' of Ken's note above, and now I will have to devote some time to addressing issue #1. I 'get' that deprecation can occur, and changes need to happen. I sure hope that the elements of data one can retrieve are not different here... we will see

I wonder what happens to the 'digital.weather.gov' sub-domain?