Superficial deposits under the address point
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.
- 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 løsmassetype for the polygon containing the point (e.g. marine deposits, bedrock, till). infiltration_potential is a mapped attribute of that polygon, not measurements at this address. mapped_polygon_area_m2 is the size of the smallest containing polygon and is a coarseness indicator: a large polygon means the classification is regional, not site-specific. Not a geotechnical assessment; a site investigation is the only basis for building decisions.
Fields
3 of 6 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 |
|---|---|---|---|
| mapped | boolean | null | value | open |
| soil_type | string | null | value | open |
| soil_type_code | string | null | context | open |
| soil_description | string | null | context | open |
| infiltration_potential | string | null | value | open |
| mapped_polygon_area_m2 | number | null (m2) | 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_conditions' # 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_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.