Ground-integrity screening score
Penalty-based ground screening score from public NGU and NVE map layers, with soil type, flood, quick-clay, storm-surge, marine-clay and borehole flags. A score of 100 means no penalty was found, not that the ground was investigated.
Status right now
Measured 22 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
Model and method
How sound is the ground under the address?
This is model metadata from the contract. Results are estimates, not observed source facts. Declared maturity and reference comparison do not establish that the current model release is approved or available to the customer.
- Result type
- Calculation
- Method
- Index
- Declared maturity
- Marked stable in the catalogue
- Reference comparison
- No qualified comparison declared
- Contract version
- 1
- Model artifact and runtime version
- Not established by this catalogue description
Inputs, headline fields and comparison basis
Declared inputs
- løsmasser
- marine clay
- quick-clay and flood zones
- NADAG boreholes
- landslide events
Headline output fields
score
Declared comparison basis
none: a screening score
Input names are not a complete training dataset or revision-pinned lineage. Read the caveats and response metadata for what a particular result is based on.
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
- unverified
- Declared redistribution
- Not established
- Catalogue basis
- Unverified
Attribution and note
Shown from the contract in its original language.
Computed by Approach; the terms of its inputs named in source apply and have not been reviewed together.
API warnings
The API returns these notes in warnings.
- Penalty-based screening from public map layers; 100 means no penalty found in the layers listed in coverage, not that the ground has been investigated.
- From method penalties-v3: where NVE's quick-clay or flood zones do not cover the kommune, the national awareness (aktsomhet) maps listed in aktsomhet_coverage answer instead — quick_clay_aktsomhet, flood_aktsomhet and landslide_aktsomhet are in_area or outside_area, null where the map is not loaded. An awareness area is a screening map of where the hazard must be assessed, not a hazard zone; rows computed before v3 carry no aktsomhet fields.
- A snapshot from the scoring run (updated_at), not a live answer. Its flood and quick clay flags follow hazard_zones' rule — true in a zone, false only in a kommune whose zones we hold, null otherwise — and the score is null when either is unknown. Between runs hazard_zones, which is answered live, is the canonical hazard answer. Rows before method penalties-v2 predate that rule and the quick clay release areas.
- landslide_zones_within_500m counts recorded landslide and avalanche events (NVE skredhendelser) within 500 m, not mapped hazard zones.
- Straight-line EPSG:25833 distances from the address point to the feature; not travel distance. Source features are imported as published, with their own accuracy and update cadence; updated_at is our import time.
Provider-contract fields
1 of 21 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 |
|---|---|---|---|
| feature_id | string | null | context | open |
| label | string | null | context | open |
| municipality_code | string | null | context | open |
| updated_at | string | null | context | open |
| score | integer | null (poeng) | value | open |
| method | string | null | context | open |
| soil_type | string | null | context | open |
| in_flood_zone | boolean | null | context | open |
| in_quick_clay_zone | boolean | null | context | — |
| quick_clay_level | string | null | context | open |
| quick_clay_zone_type | string | null | context | — |
| in_storm_surge_200yr_zone | boolean | null | context | — |
| marine_clay_possibility | boolean | null | context | open |
| boreholes_within_250m | integer | null | context | open |
| landslide_zones_within_500m | integer | null | context | open |
| rock_weakness_zone | string | null | context | open |
| quick_clay_aktsomhet | string | null | context | — |
| flood_aktsomhet | string | null | context | — |
| landslide_aktsomhet | string | null | context | — |
| aktsomhet_coverage | array<string> | null | context | — |
| coverage | array<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=ground_integrity'
# 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/ground_integrity?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.