http://qs321.pair.com?node_id=11119005


in reply to Re^3: LWP::UserAgent Alternatives for API data
in thread LWP::UserAgent Alternatives for API data

Purely out of curiosity, can you be specific? Are you saying the API data differs from this XML source you have? Can you provide an example? If you believe there to be a discrepancy with the data have you reported this? It would likely be trivial to take the script provided and point it towards the XML source.

  • Comment on Re^4: LWP::UserAgent Alternatives for API data

Replies are listed 'Best First'.
Re^5: LWP::UserAgent Alternatives for API data
by johnfl68 (Scribe) on Jul 07, 2020 at 23:23 UTC

    When I started using the NWS API regularly about 2 months ago, the Current Obs were consistently coming back 4 or more hours old. The Current Obs are only supposed to be around an hour old at most.

    The forecasts at the time were coming back 2-4 hour old, but the NWS says that is about correct for those, as they are not updated as often. I just got back data for one location that is 239 hours old (loads the same old date in web browser matching the server version). Another forecast location has been giving back 503 error since late last night (both browser and server).

    For the Current Obs, instead of using (Station KMCO as example)

    https://api.weather.gov/stations/KMCO/observations/latest

    you would use

    https://w1.weather.gov/xml/current_obs/KMCO.xml

    to get the data. If you do this from a browser, you will get a style sheet version, just use view source to see the pure XML.

    There are some differences, but most of the basic information is the same. The XML data has been much more stable than the API versions.

    Hope that helps.

[reply]

      Which tags are you looking to extract from the XML? Obviously the data return by this differs from that of the API.

[reply]

In Section Seekers of Perl Wisdom