Environment

Resolve lat/lon to NWS gridpoint and associated URLs

Step 1 of the NWS forecast flow. Convert a lat/lon into the NWS gridpoint tuple (wfo, grid_x, grid_y) together with the URLs for the 7-day forecast, the hourly forecast, the raw forecast grid, the observation station list, and the forecast / county / fire weather zones. Sugra's own /forecast and /forecast/hourly endpoints chain this lookup internally; /point is exposed so clients that want to compose requests against the raw upstream URLs can do so without re-implementing the resolution. US only: lat/lon outside US territory returns 503. Cached 24 hours (a point-to-gridpoint assignment is stable for any given coordinate). Attribution: NOAA National Weather Service (api.weather.gov).

get/api/v1/weather/nws/point

Query parameters

latnumber required

Latitude in decimal degrees, -90 to 90. US territory only.

lonnumber required

Longitude in decimal degrees, -180 to 180. US territory only.

Response

Gridpoint resolution plus upstream URL catalog.

Example response

{
  "meta": {
    "endpoint": "/api/v1/fred/us/cpi",
    "data_time": "2026-04-16T14:30:00Z",
    "response_time": "2026-04-16T14:30:12Z",
    "provider": "Sugra API v1.0.1",
    "data_age_days": 8.532,
    "source": "sugra_crypto",
    "attribution": "Short interest and Reg SHO daily short volume data is owned by and sourced from FINRA (Financial Industry Regulatory Authority).",
    "fallback_chain": [
      "sugra_crypto",
      "sugra_finance"
    ],
    "period": "2026-Q1",
    "notes": "the UKMTO report behind these counts is dated 2026-08-21 and is 11 days old"
  }
}

Changes

Changed in 2 of the 22 revisions of this API.15

Sep 1, 2026328d061c12ca3See the full diff
- ○
  added the optional property meta/data_age_days to the response with the 200 status
  response-optional-property-added
- ○
  added the optional property meta/notes to the response with the 200 status
  response-optional-property-added
- ○
  added the optional property meta/period to the response with the 200 status
  response-optional-property-added
Aug 8, 20264c4530760ba112See the full diff
- ○
  added the optional property code to the response with the 401 status
  response-optional-property-added
- ○
  added the optional property code to the response with the 429 status
  response-optional-property-added
- ○
  added the optional property code to the response with the 503 status
  response-optional-property-added
- ○
  added the optional property hint to the response with the 401 status
  response-optional-property-added
- ○
  added the optional property hint to the response with the 429 status
  response-optional-property-added
- ○
  added the optional property hint to the response with the 503 status
  response-optional-property-added
- ○
  added the optional property plan to the response with the 401 status
  response-optional-property-added
- ○
  added the optional property plan to the response with the 429 status
  response-optional-property-added
- ○
  added the optional property plan to the response with the 503 status
  response-optional-property-added
- ○
  added the optional property reason to the response with the 401 status
  response-optional-property-added
- ○
  added the optional property reason to the response with the 429 status
  response-optional-property-added
- ○
  added the optional property reason to the response with the 503 status
  response-optional-property-added

Full history