Skip to content

← All sections

NVDB phase-A road-network lines within 5 km

Individual NVDB phase-A road-network segments clipped to a 5 km radius around the authorized project address, with GeoJSON linework for map display. The source classification does not independently verify active work at a particular site; this is not a project boundary or a complete record of works.

road_construction_geometry18 fieldsNot in the demo
Source
Statens vegvesen NVDB (NLOD 2.0)
Geography
Around the address
Reported stale after
14 days
Access
Requires an approved pilot customer and named section access
Contract version
1

Status right now

State
Current
The source has loaded within its age limit.
Last loaded
2 Nov 2026
Newest record
not measured
Municipalities we hold data for
1103, 1106, 1108, 1119, 1120, 1127, 1130, 1144, 1145, 1146, 1804, 1833, 1841, 1845, 1851, 1870, 3107, 3122, 3201, 3205, 3209, 3405, 3407, 3437, 3440, 3901, 3903, 3905, 4001, 4012, 4036, 4203, 4204, 4205, 4215, 4217, 4225, 4601, 4618, 4626, 4627, 4628, 4636, 4639, 5001, 5022, 5027, 5031, 5035, 5037, 5055, 5501, 5503, 5510, 5512, 5546, 5601, 5605, 5628
From 2026-11-02 to 2026-11-02 · 2830
Every other municipality answers “not covered”, never “no cases”.
Municipalities with data
59

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
Read the publisher terms →
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 (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.

  • This is NVDB phase-A road-network linework clipped to a 5 km radius around the saved address point. Phase A is the source classification; these lines do not independently verify active work at a site and are not a planning application, project boundary or complete works extent. NVDB has no project identifier, contractor, start date or completion date here. A record represents one road-network segment.
  • GeoJSON geometry is EPSG:4326 and clipped to the 5 km radius. Long lines are simplified only as needed to fit a 1000-vertex per-feature limit; geometry_simplification_m reports 0, 5 or 25 metres. Do not use this display geometry for surveying, engineering clearance or proof that all works are included. A response is limited to 8 features per page; follow next_cursor for more.
  • First-party project-context data only; this linework is not available through customer address API keys.

Provider-contract fields

9 of 18 fields are value fields — the ones that decide whether a record actually says anything. The rest are context: identifiers, codes and timestamps.

FieldTypeRole
segment_keystring | nullcontext
road_referencestring | nullvalue
namestring | nullcontext
phasestring | nullvalue
road_categorystring | nullvalue
road_numberinteger | nullcontext
municipality_codestring | nullcontext
topology_levelstring | nullcontext
length_mnumber | nullvalue
distance_minteger | null (m)value
nvdb_valid_fromdate | nullcontext
measured_datedate | nullcontext
geometryobject | nullvalue
geometry_statusstring | nullvalue
geometry_simplification_minteger | nullvalue
geometry_crsstring | nullvalue
source_urlstring | nullcontext
updated_attimestamp | 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=road_construction_geometry'

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