Skip to content

← All sections

Superficial deposits under the address point

NGU maps surface deposits at varied scales; deeper materials may differ. Up to 50 source_observations expose collection, feature/version, dates and scale with a truncation flag. The local collection is not ingested. Regional results are context only, not planning evidence. No match means unknown, not absence.

ground_conditions9 fields6 of these fields open in the demo
Source
NGU løsmasser (superficial deposits)
Geography
The address point
Reported stale after
1 year
Access
Requires an API key granted this section
Contract version
1
In packages
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
1 Nov 2026
Data freshness evidence
Not measured yet
Unverified: only collection time is known.
Newest record
not measured
Municipalities with data
0

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.

  • Point-in-polygon against NGU's løsmasse mapping, which does not cover the whole country: 38.6% of a sampled 2 673 addresses fall inside a mapped polygon. mapped=false therefore means NGU has not mapped this point, NOT that there are no deposits there, and it never establishes what the ground is. mapped=null means the layer holds no rows at all and the question was not asked. Neither may be read as a finding about the ground. NGU's thickness attribute is not served: the collector leaves thickness_class null in all 196 194 rows, and a field that is structurally always empty would read as "unknown for this address" when it is in fact never collected.
  • soil_type is NGU's mapped soil class for the polygon containing the point (e.g. marine deposits, bedrock, till). infiltration_potential is a mapped attribute of that polygon, not a measurement at this address. mapped_polygon_area_m2 is a coarseness indicator, not positional accuracy. source_observations preserves each intersecting polygon's publisher dataset UUID, collection, feature/version, source dates and suitable map scale; map_level is derived only for the three known NGU dataset UUIDs and is unknown for any other or historical null identity. At most 50 matching polygons are returned, ordered from finer to coarser mapped scale, and source_observations_truncated signals when the full count exceeds that cap. The collector currently combines NGU's detailed and regional collections, omits the separate local collection, and this API does not assess which polygon is legally or technically applicable to a proposed footprint. NGU states its regional maps are not suitable for land-planning or ground-condition assessments intended to meet Planning and Building Act requirements; treat regional matches as context only. This address-point summary is not a parcel or proposed-footprint assessment, a geotechnical assessment, or a basis for a building decision.

Provider-contract fields

3 of 9 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
mappedboolean | nullvalueopen
soil_typestring | nullvalueopen
soil_type_codestring | nullcontextopen
soil_descriptionstring | nullcontextopen
infiltration_potentialstring | nullvalueopen
mapped_polygon_area_m2number | null (m2)contextopen
source_observations_totalinteger | nullcontext—
source_observations_truncatedboolean | nullcontext—
source_observationsarray<object> | nullcontext—

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_conditions'

# 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_conditions?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.