Replies: 1 comment
-
Thank you, this discrepancy has been documented for correction. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
OK, FIRST of all, thank your for this rather awesome API to this incredible data source!
While experimenting with the API, we noticed what may be a (very) minor issue with the typing of a couple of returned values. Specifically, the gridX and gridY values returned by GETs to the /gridpoints/{wfo}/{x},{y} endpoint appear to be returned as strings, but they appear to be specified in the OpenAPI doc Schema and example as integers. (Note: The /points endpoint returns them as numbers; we didn't check other endpoints). This is certainly not impacting operationally or blocking any progress, and was only a (very) minor brief distraction while experimenting with the API.
To Repro
curl -X GET "https://api.weather.gov/gridpoints/SEW/127,78" -H "accept: application/geo+json"
Expected
Actual
Background: I'm the founder of Hillwood Park, makers of Epic Road Trip Planner. In the wake of Hurricane Helene, and with Hurricane Milton approaching the Florida cost, we manually added a set of warnings to Epic Road Trip Planner for folks potentially traveling in that region. Manually adding warnings like this doesn't scale, and this morning someone asked what it would take to integrate NWS hazard warnings (and other weather data), and we began experimenting with this API. Short answer is that while there's a lot of work to do on our end before we have that actually integrated, it's clear the API will support what we're trying to do, and I'm super-grateful for that. Folks planning road trips will be safer, more comfortable, and better informed as a result.
Beta Was this translation helpful? Give feedback.
All reactions