Nearest geotechnical boreholes (NADAG)
Up to ten nearest geotechnical boreholes from NGU's NADAG database, with depth to bedrock, depth quality, number of investigations and quick-clay assessment. Depth is the source value, not a measurement at this plot.
Status right now
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.
- NADAG logical boreholes can group several physical investigations. Retain source_borehole_id with source_namespace and source_version; a bore number alone is not a nationally unique identity.
- depth_to_bedrock_m is the source depth value, not a measurement at this plot. Retain depth_quality_code without inferring confirmed rock; max_bored_length_m is a separate quantity. No foundation-safety conclusion or interpolation is provided.
- elevation_m uses the separately supplied elevation_datum_code; no vertical-datum conversion is performed. Accuracy fields are source centimetres, not guaranteed survey accuracy. Null or Ukjent remains unknown.
- quick_clay_assessment_code is the source category, including not-assessed and uncertain states; it is not a safe/unsafe boolean for this property.
- Collection URLs link to source relationships, not report PDFs or proof that any report is available. No linked content is fetched or redistributed; cite the report/data owner when subsequently using it.
- At most ten cached boreholes are ranked by straight-line UTM33 distance within a plus/minus 500 m coordinate window. This is not complete parcel investigation coverage. NADAG content depends on submissions, may contain uncorrected errors and may omit surveys. Source observation/update dates are distinct from our cache refresh.
- 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.
- Routes follow the car profile, from the address to the feature; ranking remains straight-line. Static modelled travel time excludes live traffic and emergency response. Road snapping is limited to 250 m at each end. Ferries may be included without timetable/wait guarantees. Graph source date is unverified unless supplied. © OpenStreetMap contributors, ODbL: https://www.openstreetmap.org/copyright
- walk_route and cycle_route follow OSRM's foot and bicycle profiles on the same OpenStreetMap data: paths and stairs allowed on foot, road rules for bicycles; modelled times at profile default speeds, not measured.
Provider-contract fields
2 of 29 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.
| 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 |
| depth_to_bedrock_m | number | null | context | open |
| depth_quality_code | string | null | context | — |
| investigation_count | integer | null | context | open |
| captured_at | string | null | context | open |
| source_borehole_id | string | null | context | — |
| source_namespace | string | null | context | — |
| source_version | string | null | context | — |
| elevation_m | number | null (m) | context | — |
| elevation_datum_code | string | null | context | — |
| horizontal_accuracy_cm | integer | null (cm) | context | — |
| vertical_accuracy_cm | integer | null (cm) | context | — |
| max_bored_length_m | number | null (m) | context | — |
| quick_clay_assessment_code | string | null | context | — |
| originating_investigation_id | string | null | context | — |
| source_origin | string | null | context | — |
| source_updated_at | string | null | context | — |
| document_collection_url | string | null | context | — |
| investigation_collection_url | string | null | context | — |
| interpretation_collection_url | string | null | context | — |
| straight_line_distance_m | integer | null (m) | value | open |
| lon | number | null | context | open |
| lat | number | null | context | open |
| route | object | context | open |
| walk_route | object | context | open |
| cycle_route | object | 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 --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=geotechnical_boreholes'
# 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/geotechnical_boreholes?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.