Ground-integrity screening score

ground_integrity17 fields14 of these fields open in the demo

Source: Approach ground model over NGU/NVE layers
Geography: The address point
Reported stale after: 60 days
Access: Requires an API key granted this section
Contract version: 1
In packages: hazard_screen, models

Available with: trial key (open fields) · 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.

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.
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.

Fields

1 of 17 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” return values to anonymous callers; the rest require 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
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 --fail-with-body --silent --show-error \
  -H "X-API-Key: $APPROACH_API_KEY" \
  'https://api.approach.no/api/v1/addresses/285717643?include=ground_integrity'

# 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/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.