NVDB road-project areas with source-owned polygons within 5 km
NVDB type-30 Veganlegg with source-owned area geometry within 5 km. Only project polygons explicitly owned by the source are shown; road-network location alone is not converted to a project boundary. Own geometry is optional in NVDB, so an empty result does not establish that no project exists.
Status right now
Measured 3 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: approved pilot customer and named section access
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
- Norsk lisens for offentlige data 2.0
- Declared redistribution
- Allowed with attribution
- Catalogue basis
- Stated in catalogue evidence
Attribution and note
Shown from the contract in its original language.
Inneholder data under norsk lisens for offentlige data (NLOD) tilgjengeliggjort av Statens vegvesen NVDB type 30 (NLOD 2.0)
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.
- Only NVDB type-30 Veganlegg with an explicit source-owned polygon are returned. NVDB's product specification makes own geometry optional; projects located only on the road network are not returned here. This is the observed feed, not a complete inventory of Norwegian public or private projects. A missing result does not prove no project exists.
- Source-owned polygon geometry is clipped to 5 km around the saved address point and transformed to EPSG:4326. Long features are simplified only as needed to fit a 1000-vertex limit; geometry_status and geometry_simplification_m describe this display geometry. This is not a cadastral boundary, construction limit, or engineering survey.
- First-party project-context data only. Customer API keys are denied; the section also requires an explicit per-product licensed-section allowlist entry.
Provider-contract fields
8 of 15 fields are value fields — the ones that decide whether a record actually says anything. The rest are context: identifiers, codes and timestamps.
| Field | Type | Role |
|---|---|---|
| project_id | integer | null | context |
| project_reference | string | null | value |
| project_type | string | null | value |
| project_name | string | null | value |
| lifecycle_status | string | null | value |
| start_date | string | null | value |
| finish_date | string | null | value |
| distance_m | integer | null (m) | value |
| geometry | object | null | value |
| geometry_status | string | null | context |
| geometry_simplification_m | integer | null | context |
| geometry_crs | string | null | context |
| source_modified_at | string | null | context |
| fetched_at | string | null | context |
| source_url | string | null | context |
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=road_project_areas'
# 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/road_project_areas?limit=25'Why it cannot be tried here
This section is not part of the public demo projection. That is a licensing and privacy decision, not a sign the data is missing: it is served to customers granted the section.