Replies: 3 comments
-
I think you are missing the difference in time zone offset. The raw data is in UTC (+00:00). The forecasts are in local time (EDT -04:00 in this case).
So if you are, as I suspect, looking at this period in the hourly forecast data:
Then in the grid you should be looking for data corresponding to time I think you will find these data align properly. temperature: skyCover: |
Beta Was this translation helpful? Give feedback.
-
@StephenClouse Ouch, good eye. That's embarrassing. Thanks for the help! |
Beta Was this translation helpful? Give feedback.
-
@jeffclark Don't worry, you're not the first :) |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I'm looking for forecast data by the hour, but am getting conflicting information between the raw data at
gridpoints/CWA/gridX,gridY/
and the hourly forecast generated atgridpoints/CWA/gridX,gridY/forecast/hourly
Examples from 12:00:00 2-July
The
temperature
at: https://api.weather.gov/gridpoints/BOX/81,72Returns:
{ "validTime": "2020-07-02T12:00:00+00:00/PT1H", "value": 18.333333333333332 }
(Converting to F is 65)
For the same time period, the
temperature
at: https://api.weather.gov/gridpoints/BOX/81,72/forecast/hourlyReturns:
74
(Sitting outside, it's definitely closer to 74 than 65!)
The skycover data at https://api.weather.gov/gridpoints/BOX/81,72
Returns:
{ "validTime": "2020-07-02T12:00:00+00:00/PT1H", "value": 74}
Which I believe means that there is 74% cloud coverage.
For the same time period, the
shortForecast
at: https://api.weather.gov/gridpoints/BOX/81,72/forecast/hourlyReturns:
Sunny
(Sitting outside, it's certainly sunny and not 74% cloud cover! A single small cloud in the sky!)
Am I misinterpreting the "raw" data incorrectly? Should I expect these two data points align with each other?
Beta Was this translation helpful? Give feedback.
All reactions