METAR.ws: Station Observations and Weather-Model Streaming API

What is METAR.ws?

Keep observation time separate from the time the service received a report. Decoded temperature, wind, visibility and flight category accompany the raw text; station coordinates and elevation help align the observation site with a model grid. Grid-point distance and source age add freshness context.

Model highs and lows are forecasts, not measured settlement results. Model output can be detected, partial or day-complete, and source publication and model-run timing bound availability. Match the contract's station, time zone, units and rounding convention before comparing a forecast extreme with the eventual observation.

Feed coverage and updates

• Decoded observations

  Receive temperature, wind, visibility and flight category together with the raw report.

• Separate timestamps

  Distinguish observation time from platform receipt time.

• Station metadata

  Use coordinates and elevation when aligning stations and model grids.

• Model signals

  Receive derived highs and lows as model runs become available.

• Model lifecycle events

  Handle detected, partial and day-complete output as distinct states.

• Freshness context

  Inspect grid-point distance and source age.

• Historical API

  Retrieve past METAR/SPECI data within the selected plan's limits.

• WebSocket subscriptions

  Select stations and event types over an authenticated connection.

Monitoring and data workflows

Pricing and total cost

Feed access and configuration

1. Check coverage for the required station and model.
2. Create an API key.
3. Connect to the documented WebSocket endpoint.
4. Subscribe to the station identifiers and event types you need.
5. Retain raw reports, units and both timestamps.
6. Handle partial model runs and reconnections explicitly.

Useful links

Frequently asked questions about METAR.ws