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
I wanted to report a minor bug I'm experiencing in the GPS lookup.
When I make a GPS lookup -> GridID, GridX, GridY lookup, I'm occassionally getting an erroneous GridID, GridX, GridY tuple. It appears that the GridY coordinate is off by 1 to the north occassionally.
As an example, for the point:
Lat : 36.6133024
Lon : -120.3817894
For my test case, I manually archived some coordinates of GridID, GridX, GridY. They should correspond to the corners of a Weather.gov API 2.5 km square grid.
These points are averaged to get the center point. I passed this center point is passed back to the Weather.gov API which should return the same GridID, GridX, GridY tuple. I've also included the query URL as "Query URL" in the dropped pin.
However, when going to the forecast page of the returned tuple, the GPS coordinates of the returned tuple are off by 1 to the north, specifically for GridY.
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.
-
I wanted to report a minor bug I'm experiencing in the GPS lookup.
When I make a GPS lookup -> GridID, GridX, GridY lookup, I'm occassionally getting an erroneous GridID, GridX, GridY tuple. It appears that the GridY coordinate is off by 1 to the north occassionally.
As an example, for the point:
Lat : 36.6133024
Lon : -120.3817894
This should be in HNX 29, 27
However, the query: https://api.weather.gov/points/36.6133024,-120.3817894
Returns:
"geometry": {
"type": "Point",
"coordinates": [
-120.3818,
36.613300000000002
]
},
"properties": {
"@id": "https://api.weather.gov/points/36.6133,-120.3818",
"@type": "wx:Point",
"cwa": "HNX",
"forecastOffice": "https://api.weather.gov/offices/HNX",
"gridId": "HNX",
"gridX": 29,
"gridY": 98,
When I followup on HNX 29 98:
https://api.weather.gov/gridpoints/HNX/29,98/forecast
"coordinates": [
[
[
-120.403274,
36.644170299999999
],
[
-120.3980844,
36.622203399999997
],
[
-120.3706792,
36.626370399999999
],
[
-120.3758634,
36.6483378
],
[
-120.403274,
36.644170299999999
]
]
All of the latitude points are > the provided 36.613300000000002 and puts the returned gridpoint north of the intended target.
I've documented the faults I'm experiencing on this Google Map:
https://www.google.com/maps/d/edit?mid=1O2FrOaxCCh6G_PLTcTNWG5ZOMsiI_r1f&usp=sharing
For my test case, I manually archived some coordinates of GridID, GridX, GridY. They should correspond to the corners of a Weather.gov API 2.5 km square grid.
These points are averaged to get the center point. I passed this center point is passed back to the Weather.gov API which should return the same GridID, GridX, GridY tuple. I've also included the query URL as "Query URL" in the dropped pin.
However, when going to the forecast page of the returned tuple, the GPS coordinates of the returned tuple are off by 1 to the north, specifically for GridY.
Beta Was this translation helpful? Give feedback.
All reactions