Skip to content

← All sections

Railway noise zones

Railway noise zones (T-1442 red and yellow zone) near the address from Bane NOR's network, with distance. calculated_year is the model's forecast year, not a measurement year.

rail_noise_zones10 fields10 of these fields open in the demo
Source
Bane NOR Støysoner jernbane
Geography
Around the address
Reported stale after
47 days
Access
Requires an API key granted this section
Contract version
1
In packages
environment_nuisance, noise_and_nearby_projects

Read about this data source →

Status right now

State
Within budget
Combined section status is within the age and schedule budget. Check the separate data timestamp for data freshness.
Last loaded
27 Oct 2026
Data freshness evidence
Within budget
Newest stored data record 27 Oct 2026
Newest record
27 Oct 2026
Municipalities with data
107

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.

  • T-1442 planning zones for Bane NOR's network; noise_levels' rail source_type (round 3, 2017) carries the EU END dB bands for major and agglomeration rail and can hold a result where this layer does not.
  • 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.

FieldTypeRoleDemo
feature_idstring | nullcontextopen
labelstring | nullcontextopen
municipality_codestring | nullcontextopen
updated_atstring | nullcontextopen
noise_zone_categorystring | nullcontextopen
noise_sourcestring | nullcontextopen
methodstring | nullcontextopen
calculated_yearinteger | null (årstall)contextopen
straight_line_distance_minteger | null (m)valueopen
contains_addressboolean | nullvalueopen

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=rail_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/rail_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.