Skip to main content
This page collects the practical advice scattered across the rest of the reference into a single checklist.
temp_c, dewp_c, and the decimal fields on forecast events are sent as strings on purpose. Parse them with a decimal type rather than a float, so precision survives.
If you subscribe to both metar.atis.<icao> and metar.obs.<icao> for the same station, the same observation will arrive twice. Use the pair (station, report_time) as your dedup key.
Until local_day_complete is true, a forecast’s temp_max_c and temp_min_c only reflect the hours received so far. Mixing incomplete days into an accuracy comparison biases it in one direction, so filter them out first.
Subscribing to a channel that doesn’t exist yet fails with channel_format rather than closing your connection, so you can safely try a station before you know it is covered.
Channel limits are counted per account, not per connection. Opening a second connection doesn’t buy you more channels, only more delivery paths for the same budget.
Every example on this site reconnects on close with a short delay and re-subscribes afterward. Last-value replay means you’re current again immediately, so there’s no extra state to restore.

Next: FAQ

Quick answers to common integration questions.