Pull an hourly wind-speed and gust forecast for a crane lift site to check against the load chart's wind limits
domain: api.weather.gov · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Call GET https://api.weather.gov/points/{lat},{lon} (no API key required, but a descriptive User-Agent header is required by NWS policy) to resolve the lift site to its forecast office and gridpoint.
Follow the forecastGridData URL returned in that response for the resolved gridpoint.
Request the gridpoint data (/gridpoints/{office}/{gridX},{gridY}) and read the windSpeed, windGust, and windDirection time series, each carrying a unit-of-measure code and ISO 8601 valid-time intervals.
Convert the reported units (typically km/h) to mph if comparing against a US crane manufacturer's load-chart wind limit.
Re-query close to lift time, since gridpoint forecasts are updated multiple times per day and consecutive equal values are merged in the response to save bandwidth.
Known gotchas
Manufacturer wind limits are usually specified at hook height, not the standard forecast reference height — treat the NWS figure as a planning input, not a substitute for an on-site anemometer reading at lift time.
api.weather.gov only covers US territories; coordinates outside NWS coverage return an error rather than degraded or estimated data.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?