Possibility of marine clay at the address

marine_clay_possibility8 fields8 of these fields open in the demo

Source: NGU Mulighet for marin leire
Geography: The address point
Reported stale after: 120 days
Access: Requires an API key granted this section
Contract version: 1
In packages: hazard_screen

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.

A screening layer derived from the marine limit and løsmasse maps: it says whether marine clay CAN occur, not that quick clay is present. Not a ground investigation.
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

2 of 8 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	value	open
municipality_code	string \| null	context	open
updated_at	string \| null	context	open
possibility_class	string \| null	context	open
deposit_type	string \| null	context	open
straight_line_distance_m	integer \| null (m)	context	open
contains_address	boolean \| null	value	open

Fetch this section

curl -H "X-API-Key: $APPROACH_API_KEY" \
  "https://api.approach.no/api/v1/addresses/285717643?include=marine_clay_possibility"

# paginated, one section at a time
curl -H "X-API-Key: $APPROACH_API_KEY" \
  "https://api.approach.no/api/v1/addresses/285717643/sections/marine_clay_possibility?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.