Projected climate change for the address's county (Klima i Norge 2025)
climate_projection14 fieldsNot in the demo
Available with: bought bundle or agreed plan (all fields) · Pricing
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.
- Each row is one indicator, season, scenario and 30-year period for the whole region (county): ensemble mean with its 10th and 90th percentile. diff-* indicators are differences in the indicator's unit (diff-tas in degC, diff-pr20mm in days per year), change-* indicators are relative changes in per cent, all against 1991-2020.
- Ensemble statistics of 30-year means averaged over a whole county (Oslo and Akershus together), not a forecast for the address and not local: terrain, coast and altitude inside a county differ much more than the county mean. Changes are relative to 1991-2020. mean is the ensemble mean, q10 and q90 the 10th and 90th percentile of the ensemble. Scenarios: rcp26 (strong mitigation), rcp45 (intermediate) and ssp370 (high emissions); this edition has no RCP8.5. Periods: 2041-2070 and 2071-2100 (30-year means centred on 2056 and 2086, read from the source's time axis).
- The county statistics have no flood-discharge indicator: runoff (change-mrro), very heavy daily rain (change-pr997, the 99.7th percentile), the largest 5-day rainfall (change-prmax5day) and days above 20 mm (diff-pr20mm) are the nearest available signals, and none of them says that a river or street at this address will flood.
- Licence: MET Norway publishes these data under NLOD 2.0 and CC BY 4.0 (https://api.met.no/doc/License). Attribution: Norwegian Centre for Climate Services (KSS), MET Norway and NVE, Klima i Norge, 2025 edition.
Fields
3 of 14 fields are value fields — the ones that decide whether a record actually says anything. The rest are context: identifiers, codes and timestamps.
| Field | Type | Role |
|---|---|---|
| region_code | integer | null | context |
| region_name | string | null | context |
| scenario | string | null | context |
| indicator | string | null | context |
| season | string | null | context |
| period_start | integer | null | context |
| period_end | integer | null | context |
| mean | number | null | value |
| q10 | number | null | value |
| q90 | number | null | value |
| unit | string | null | context |
| description | string | null | context |
| baseline | string | null | context |
| updated_at | timestamp | null | context |
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 --fail-with-body --silent --show-error \ -H "X-API-Key: $APPROACH_API_KEY" \ 'https://api.approach.no/api/v1/addresses/285717643?include=climate_projection' # paginated, one section at a time curl --fail-with-body --silent --show-error \ -H "X-API-Key: $APPROACH_API_KEY" \ 'https://api.approach.no/api/v1/addresses/285717643/sections/climate_projection?limit=25'
Why it cannot be tried here
This section is not part of the public demo projection. That is a licensing and privacy decision, not a sign the data is missing: it is served to customers granted the section.