nws-weather

NWS Weather

Fetch the National Weather Service forecast for an intended US location through the selected NWS connector. The default at-point runner accepts numeric latitude and longitude, reads the provider's point-to-grid mapping and then fetches that grid's forecast. No API key, office-code lookup or hand-built grid request is needed for this route.

Use this for read-only forecast evidence. Global place-name discovery and Open-Meteo data belong to open-meteo-weather; resolve the intended place first when coordinates are unknown. Do not guess a city or assume that a US place shares a grid with a nearby point. Notification, scheduling and operational actions need their own skill and authority.

How it works

1. Supply the intended latitude and longitude. The NWS request uses four decimal places, matching the existing points contract.
2. points.read returns the provider's gridId, gridX and gridY. A bounded domain function admits those exact fields and keeps the point, timezone, forecast URL and native readback binding in location. It never derives a grid from geography or follows an arbitrary returned URL.
3. Only a usable mapping proceeds through the existing forecast.read operation. Its original provider packet retains forecast periods, units, generated/update times and native evidence.
4. Return the observed data. The calling agent interprets the forecast and its coverage; this reader does not invent planning advice or publication.

The NWS API documentation explains point-to-grid discovery. Mappings can change, so reuse a saved grid only while its freshness is appropriate to the caller's job. The default reads the current mapping; it does not maintain a cache or background loop.

Reuse in graphs

forecast still accepts office, grid_x and grid_y as strings and reads that exact grid once. It never calls points or geocodes again. locate still accepts string lat and lon for a points-only read. Preserve the native provider packet and readback when handing either result downstream.