Ensemble Weather Forecast With Multi-Model SpreadService
wx-ensemble
Returns a descriptive multi-model temperature band for a coordinate, built from independent national forecasting centres. Six models arrive in one Open-Meteo call: ICON (Deutscher Wetterdienst), GFS (NOAA), IFS (ECMWF), GEM (Environment and Climate Change Canada), ARPEGE (Meteo-France) and JMA (Japan Meteorological Agency), cross-checked against the Norwegian Meteorological Institute and, inside the US, the NOAA National Weather Service. Request is a JSON object with latitude, longitude and an optional hour horizon of 1 to 24. Response is a JSON object with one entry per hour. Each entry names every member value and its source, then reports min, max, median, mean, sample standard deviation, interquartile range, observed spread, an agreement ratio, and a confidence label explicitly marked as derived from the spread rather than a probability. Missing upstream values are reported as missing and excluded from the statistics; nothing is interpolated, back-filled or coerced to zero. When fewer than two models report a point the service refuses to publish a band and returns INSUFFICIENT_EVIDENCE with a stated reason, because one model cannot express uncertainty. When no model reports at all it returns UNAVAILABLE instead. Refusal states carry no band statistics: min, max, median, mean, spread, stddev, iqr and agreement are all null there. Aggregation is deterministic given the upstream values, and the response records its own method so nothing is taken on trust.
Service Metadata Cardsource: on-chain metadata (LCD)
{10 items
"schema":"pocket-service-card/v1"
"description":"Returns a descriptive multi-model temperature band for a coordinate, built from independent national forecasting centres. Six models arrive in one Open-Meteo ca..."
"rpc_types":[1 item
0:{4 items
"type":"REST"
"intent":"expected"
"backend_hint":"rest, plain HTTP JSON"
"notes":"Every response is a JSON object. All inputs arrive in the body. No caller authentication."
"backend":"A small Node.js HTTP service with no dependencies beyond the standard library. It fans out to public weather endpoints, normalises their timestamps to a common ..."
"notes":"Outbound calls go to api.open-meteo.com, api.met.no and api.weather.gov over HTTPS. All free, no API key; the latter two need a descriptive User-Agent. Keep out..."