I can't get a full 24 hour period for historical METAR data.

  • 2
  • Question
  • Updated 2 years ago
I can't figure out why when i search historical data, it is not pulling a full 24 hour period. I am looking specifically for METAR data and when I call:
api.wunderground.com/api/mykey/history_20131119/q/KNYL.xml
it returns data from 0757Z to 2357Z. I tried getting the rest from the day before since it seems to pull the history using local time, but the day before ends at 2357Z. How can I get the data from 0057Z to 0657Z?
Photo of rasteele

rasteele

  • 1 Post
  • 0 Reply Likes
  • confused

Posted 5 years ago

  • 2
Photo of danbridgeman

danbridgeman

  • 6 Posts
  • 0 Reply Likes
This just started happening to me a few days ago. What it looks like to me is that it is starting every day at midnight in the local timezone, and then ending the day at midnight in GMT. The hours that get lost seem to be completely inaccessible.

I've tried locations in multiple timezones, and I've gotten the data back in both JSON and XML formats, and the results are always the same. It worked fine up until a few days ago.
Photo of Brendan Hayes

Brendan Hayes, Official Rep

  • 962 Posts
  • 122 Reply Likes
These should be better now. There was a location bug causing some time problems that was fixed. Let me know if there's any other issues.
Photo of jpgrover

jpgrover

  • 1 Post
  • 0 Reply Likes
I'm having similar issues getting exactly 24 hours of METAR data for several cities.  Some cities have data for less than 24 hours and some cities have more than 1 METAR reading per hour.  For example, look at these cities on Feb 14th, 2016...

http://api.wunderground.com/api/mykey/history_20160214/q/AZ/Chandler.json (only 16 hours)
http://api.wunderground.com/api/mykey/history_20160214/q/WA/Seattle.json (only 1 hour)
http://api.wunderground.com/api/mykey/history_20160214/q/MEXICO/Tijuana.json (30 observations)
http://api.wunderground.com/api/mykey/history_20160214/q/NV/Henderson.json (71 observations)