Skip to content

← All sections

Nearest change-radar signals

Nearest registered signals of change around the address, drawn from municipal cases, plans and grid measures, each linking back to a public case or plan. The direction is a heuristic, not a valuation.

change_signals19 fieldsNot in the demo
Source
Approach endringsradar (municipal cases, plans, grid measures)
Geography
Around the address
Reported stale after
30 days
Access
Requires an API key granted this section
Contract version
2
In packages
planning_restrictions, 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
17 Nov 2026
Data freshness evidence
Within budget
Newest stored data record 17 Nov 2026
Newest record
17 Nov 2026
Municipalities with data
359

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: 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
Attribution and note

Shown from the contract in its original language.

Computed by Approach; the terms of its inputs named in source apply and have not been reviewed together.

API warnings

The API returns these notes in warnings.

  • Derived composite; each signal links back to a public case or plan. Direction is a heuristic (positive/negative/mixed) and not a valuation. Not a model: the section lists what is registered near the address and estimates nothing, so its kind is snapshot and it is not in the models catalogue (/models).
  • 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.
  • Routes follow the car profile, from the address to the feature; ranking remains straight-line. Static modelled travel time excludes live traffic and emergency response. Road snapping is limited to 250 m at each end. Ferries may be included without timetable/wait guarantees. Graph source date is unverified unless supplied. © OpenStreetMap contributors, ODbL: https://www.openstreetmap.org/copyright
  • walk_route and cycle_route follow OSRM's foot and bicycle profiles on the same OpenStreetMap data: paths and stairs allowed on foot, road rules for bicycles; modelled times at profile default speeds, not measured.

Provider-contract fields

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

FieldTypeRole
feature_idstring | nullcontext
labelstring | nullvalue
categorystring | nullcontext
municipality_codestring | nullcontext
updated_atstring | nullcontext
case_typestring | nullcontext
statusstring | nullcontext
registeredstring | nullcontext
directionstring | nullcontext
sourcestring | nullcontext
precisionstring | nullcontext
measure_typestring | nullcontext
case_numberstring | nullcontext
straight_line_distance_minteger | null (m)value
lonnumber | nullcontext
latnumber | nullcontext
routeobjectcontext
walk_routeobjectcontext
cycle_routeobjectcontext

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=change_signals'

# 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/change_signals?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.