Skip to main content

Carry weather meaning with the value

Weather is a family of observations, forecasts, guidance, sampled fields and selected views. A common wrapper must preserve the product distinctions that explain what a value means.

Choose the object by use case​

Use caseObject familyPreserve
Show what a station observedMETAR / observationStation, observation time, raw/source provenance and units
Show a forecast intervalTAF / forecast periodIssue time, validity, change group and probability
Compare hourly statistical guidanceMOS LAMP / NBM / autoModel run, station, valid hour, per-field source and source status
Build a combined airport viewWeather FusionProduct identities, selection policy, freshness and partial state
Evaluate a trajectoryGridded weather captureVerified bytes, axes, run/valid times, coverage and interpolation policy
Inspect a vertical columnSoundingLevel coordinate, pressure/height datum, units and valid time
Render a hazardTemporal hazard geometryGeometry, vertical extent, validity interval, issue and supersession

Time is part of the contract​

Observed at identifies a measurement. Issued at identifies a forecast publication. Model run identifies an analysis cycle. Valid from/until identifies applicability. Ingested at identifies the service's receipt. Selected at identifies a consumer decision. These times must not collapse into one field. Define interval boundaries and freshness policy before comparing values from different products.

MOS selection and provenance​

The current auto product selects LAMP first and falls back to NBM per field. A row can therefore contain values from more than one source. Retain product labels, run and ingestion times, source status and raw guidance needed to explain the selection.

StateReader behavior
Missing fieldDisplay absence; do not substitute zero
Unknown ceilingPreserve unknown; do not label unlimited
Unlimited ceilingPreserve the explicit unlimited meaning
Stale or future guidanceRetain status and apply the documented selection policy
ProbabilityPreserve probability and its event/interval; do not treat it as an observed condition

The Java blender, Swift MosGuidance, web reader and MCP adapter exist today. Their presence is not proof of a single versioned cross-client wire contract. The next weather phase audits field parity and runs the same positive and negative fixtures through the real readers.

Weather Fusion ownership​

The weather service's aggregate DTO and the native Weather Fusion selection/cache layer are related but distinct. The repository's separately named server/fusion owns dataset-version catalogs; it is not the Weather Fusion model owner. The public catalog records that distinction. Existing service and app Swift DTO copies need explicit ownership and conformance decisions.

A fused response can be partial even when transport succeeds. Keep each product's freshness and availability; avoid claiming complete weather from the aggregate object's existence.

Weather captured for planning​

A planning job binds captured resources and effective weather time before dispatch. Prepared source handles are local to a process; portable coverage and source digests travel with the retained job. Missing coverage cannot silently become zero wind. An explicit estimate has its own method and disclosure. See the planning recipe for a synthetic grid and an unavailable-weather case.