You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently I use a latitude/longitude to query the /points/{lat,lon} endpoint, then use the observationStations parameter to get a list of the observing stations for that grid.
How are the stations returned in the gridpoints station request sorted? Are they closest to the grid point?
Is there a better way to get the closest station to a latitude and longitude via the API? The /points/{point}/stations is deprecated, so what I do now is:
Call /points/{point}]
Then use the url in observationStations parameter to get a list of stations.
Take the first station in the list, then call a /stations/{stationId} endpoint to get the data I am interested in.
It would really be nice to reduce the number of queries to get to that point.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Currently I use a latitude/longitude to query the /points/{lat,lon} endpoint, then use the observationStations parameter to get a list of the observing stations for that grid.
How are the stations returned in the gridpoints station request sorted? Are they closest to the grid point?
Is there a better way to get the closest station to a latitude and longitude via the API? The /points/{point}/stations is deprecated, so what I do now is:
It would really be nice to reduce the number of queries to get to that point.
Beta Was this translation helpful? Give feedback.
All reactions