Road-traffic noise zones
Road-traffic noise zones (red and yellow zone under T-1442) near the address from Statens vegvesen's strategic noise mapping, with distance. calculated_year is the forecast year of the noise model, not a measurement year.
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
- Norsk lisens for offentlige data 2.0
- Declared redistribution
- Allowed with attribution
- Catalogue basis
- 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 Støykartlegging T-1442
API warnings
The API returns these notes in warnings.
- Strategic noise mapping (rød sone Lden ≥ 65 dB, gul sone ≥ 55 dB) of state/county roads nationwide, and of municipal roads with AADT over 1 000 in the Oslo, Bergen, Trondheim, Stavanger and Fredrikstad/Sarpsborg urban areas per the source's own scope; façade-level values are not included. Our load currently holds far fewer zones for those four cities than that scope implies (Trondheim: none), a known coverage gap under investigation, not evidence the source excludes municipal roads there. noise_levels' agglomeration_roads scope (round 4, 2022) models every road in those same urban areas and is the fuller answer for an address not matched here.
- calculated_year is the prognosis year of the noise model (T-1442 mapping is computed for a forecast year, typically 2040 for roads), not the year of a measurement or of publication.
- 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.
Provider-contract fields
2 of 10 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 | context | open |
| municipality_code | string | null | context | open |
| updated_at | string | null | context | open |
| noise_zone_category | string | null | context | open |
| noise_source | string | null | context | open |
| method | string | null | context | open |
| calculated_year | integer | null (årstall) | context | open |
| straight_line_distance_m | integer | null (m) | value | open |
| contains_address | boolean | null | value | 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=road_noise_zones'
# 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_noise_zones?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.