Nearest change-radar signals

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

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.

Derived composite; each signal links back to a public case or plan. Direction is a heuristic (positive/negative/mixed) and not a valuation.
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.

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.

Field	Type	Role
feature_id	string \| null	context
label	string \| null	value
category	string \| null	context
municipality_code	string \| null	context
updated_at	string \| null	context
case_type	string \| null	context
status	string \| null	context
registered	string \| null	context
direction	string \| null	context
source	string \| null	context
precision	string \| null	context
measure_type	string \| null	context
case_number	string \| null	context
straight_line_distance_m	integer \| null (m)	value
lon	number \| null	context
lat	number \| null	context
route	object	context
walk_route	object	context
cycle_route	object	context

Fetch this section

curl -H "X-API-Key: $APPROACH_API_KEY" \
  "https://api.approach.no/api/v1/addresses/285717643?include=change_signals"

# paginated, one section at a time
curl -H "X-API-Key: $APPROACH_API_KEY" \
  "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.