Modelled noise exposure by source (screening calculation)

noise_model43 fieldsNot in the demo

Source: Approach noise screening model (CNOSSOS-EU road and rail emission, ISO 9613-2 propagation, line of sight over Kartverket DSM) on NVDB, Entur, Avinor and BRREG data
Geography: The address point
Reported stale after: 120 days
Access: Requires an API key granted this section
Contract version: 1
In packages: environment_nuisance, models

Available with: bought bundle or agreed plan (all fields) · Pricing

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.

A screening calculation at a point 4 m above ground, not a measurement, a façade level or a legal noise zone (T-1442); the official mapped bands are shown beside it for comparison. Road and rail levels are summed energetically per source; businesses and residential density are indicators that raise the index by at most 10 points and carry no dB. Rail vehicle mix is assumed; airports are indicators until a calibrated fit exists.
best_estimate_lden_db and exposure_index use the mixture of the physics and an ML model trained on the official noise maps when the release has one (best_estimate says which); the ML part reproduces those maps, which are calculations, and lden_db and sources stay the physics alone.
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.

Fields

4 of 43 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
feature_id	string \| null	context
label	string \| null	context
municipality_code	string \| null	context
updated_at	string \| null	context
exposure_index	integer \| null	value
lden_db	number \| null	value
lnight_db	number \| null	value
lday_db	number \| null	context
levening_db	number \| null	context
road_lden_db	number \| null	context
rail_lden_db	number \| null	context
air_lden_db	number \| null	context
exposure_index_base	integer \| null	context
exposure_index_uplift	integer \| null	context
status	string \| null	context
abstain_reason	string \| null	context
tier	string \| null	context
below_screening_range	boolean \| null	context
receiver_height_m	number \| null (m)	context
mapped_band_road	string \| null	context
mapped_band_rail	string \| null	context
mapped_band_airport	string \| null	context
mapped_lnight_band_road	string \| null	context
mapped_agglomeration	boolean \| null	context
agreement_with_mapped	string \| null	context
sources	array<object> \| null	context
indicators	array<object> \| null	context
index_adjustments	array<object> \| null	context
coverage	object \| null	context
model_warnings	array<string> \| null	context
best_estimate_lden_db	number \| null	value
best_estimate	string \| null	context
exposure_index_physics	integer \| null	context
ensemble	object \| null	context
establishment_context	object \| null	context
tram_schedule_context	object \| null	context
calibration	object \| null	context
release_id	string \| null	context
method	string \| null	context
model_version	string \| null	context
params_digest	string \| null	context
inputs_digest	string \| null	context
computed_at	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 --fail-with-body --silent --show-error \
  -H "X-API-Key: $APPROACH_API_KEY" \
  'https://api.approach.no/api/v1/addresses/285717643?include=noise_model'

# paginated, one section at a time
curl --fail-with-body --silent --show-error \
  -H "X-API-Key: $APPROACH_API_KEY" \
  'https://api.approach.no/api/v1/addresses/285717643/sections/noise_model?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.