Latest hourly observation at the nearest reporting station
Latest hourly observation from the nearest reporting station: temperature, precipitation, wind, humidity and observation time, with the station's distance. Station readings, not measurements at the address.
Status right now
Measured 10 Nov 2026. This is about the section as a whole, not one address: an address outside coverage still gets “not covered”, never “no”.
Available with: trial key (open fields) · bundle or agreed plan, subject to field policy and source grants · Pricing
Source terms and reuse
These are declarations from the catalogue contract, not a new rights approval. Customer access, source agreements and privacy need separate assessment. A licence label does not establish coverage or reviewed content.
- Declared licence or terms
- Creative Commons Attribution 4.0
- Declared redistribution
- Allowed with attribution
- Catalogue basis
- Stated in catalogue evidence
Attribution and note
Shown from the contract in its original language.
© MET Norway Frost, CC BY 4.0
What this does not say
Quoted verbatim from the section’s warnings field, exactly as the API returns it. They are not translated: a translation would show something other than what your response actually contains.
- Nearest station with recent observations; may fall back to a stale reporting station. Station distance is straight-line EPSG:25833 metres, not a measurement at the address. Temperature: Celsius; precipitation: millimetres over the preceding hour; wind: m/s; humidity: percent. When the nearest station carries no anemometer, wind_speed comes from the nearest station that measured wind within the last three hours, named in wind_station_name at wind_station_straight_line_distance_m. Per-measurement quality codes and sensor metadata are retained. Quality 5/6/7 and invalid values are excluded. CC BY 4.0, MET Norway.
Provider-contract fields
4 of 15 fields are value fields — the ones that decide whether a record actually says anything. The rest are context: identifiers, codes and timestamps. Fields marked “open” also occur in the demo projection, which may have different field definitions. Other fields require the appropriate field policy and source access, not just a key.
| Field | Type | Role | Demo |
|---|---|---|---|
| station_id | string | null | context | open |
| station_name | string | null | context | open |
| station_latitude | number | null | context | open |
| station_longitude | number | null | context | open |
| station_straight_line_distance_m | number | null (m) | context | open |
| observation_time | string | null | context | open |
| temperature | number | null (degC) | value | open |
| precipitation | number | null (mm) | value | open |
| wind_speed | number | null (m/s) | value | open |
| wind_station_name | string | null | context | open |
| wind_station_straight_line_distance_m | number | null (m) | context | open |
| wind_observation_time | string | null | context | open |
| humidity | number | null (%) | value | open |
| measurement_metadata | object | null | context | open |
| fetched_at | string | null | context | open |
Fetch this section
Send the key in the X-API-Key header. The section can be fetched with the rest of the address, or on its own with pagination.
curl --disable --fail-with-body --silent --show-error --connect-timeout 10 --max-time 30 \
-H "X-API-Key: ${APPROACH_API_KEY:?APPROACH_API_KEY is not set}" \
'https://api.approach.no/api/v1/addresses/285717643?include=weather'
# paginated, one section at a time
curl --disable --fail-with-body --silent --show-error --connect-timeout 10 --max-time 30 \
-H "X-API-Key: ${APPROACH_API_KEY:?APPROACH_API_KEY is not set}" \
'https://api.approach.no/api/v1/addresses/285717643/sections/weather?limit=25'Try it now
This is a real call against the public demo, from here. What appears below is what the API returned — not a sample.