Skip to content

← All sections

Possibility of marine clay at the address

Whether marine clay can occur at the address, from NGU's screening layer derived from the marine limit and superficial deposits. It does not show that quick clay is present and is not a ground investigation.

marine_clay_possibility8 fields8 of these fields open in the demo
Source
NGU Mulighet for marin leire
Geography
The address point
Reported stale after
47 days
Access
Requires an API key granted this section
Contract version
1
In packages
hazard_screen, plot_and_zoning

Read about this data source →

Status right now

State
Within budget
Combined section status is within the age and schedule budget. Check the separate data timestamp for data freshness.
Last loaded
18 Nov 2026
Data freshness evidence
Within budget
Newest stored data record 18 Nov 2026
Newest record
18 Nov 2026
Municipalities with data
219

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

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

API warnings

The API returns these notes in warnings.

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

Provider-contract 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” 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.

FieldTypeRoleDemo
feature_idstring | nullcontextopen
labelstring | nullvalueopen
municipality_codestring | nullcontextopen
updated_atstring | nullcontextopen
possibility_classstring | nullcontextopen
deposit_typestring | nullcontextopen
straight_line_distance_minteger | null (m)contextopen
contains_addressboolean | nullvalueopen

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=marine_clay_possibility'

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