Skip to content

← All sections

Zoning plans within 500 m and 1 km of the address

Legacy section: counts and list of zoning plans within 500 m and 1 km of the address, by status such as in progress or adopted. Kept for existing integrations; the planning section replaces it.

nearby_zoning_plans13 fields13 of these fields open in the demo
Source
Municipal plan registers ingested by Approach (currently Oslo kommune, Plan- og bygningsetaten planregister)
Geography
Around the address
Reported stale after
90 days
Access
Requires an API key granted this section
Contract version
1
In packages
noise_and_nearby_projects

Read about this data source →

Status right now

State
Stale
The clock used for combined section status is older than its limit. Data freshness is shown separately.
Last loaded
2 Nov 2026
Data freshness evidence
Not measured yet
Unverified: only collection time is known.
Newest record
not measured
Municipalities we hold data for
0301
From 1902-09-13 to 2026-10-21 · 7202
Coverage measurement: 22 Nov 2026, 11:40 · recently checked
Other municipalities have no rows in this snapshot; this does not mean “no cases”.
Municipalities with data
8

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.

  • Deprecated: use the planning section, which carries this section's records together with the other plan sections' and a coverage block saying, per part, whether the kommune is covered. Kept for existing integrations; stops answering on 15 Apr 2027 (the Sunset header carries the date).
  • Only kommuner whose plan register is ingested are answered (GET /coverage, source regulation_plans; on 30 Sep 2026 Oslo alone). Anywhere else the section answers not_found with reason not_covered: we hold no plans there, which is not the same as there being none. Plans across a kommune border are counted only where that kommune is ingested too.
  • Distance is straight-line from the address point to the plan's exact land-use polygons (distance_basis exact_plan_features), or to the plan outline where the register publishes no polygons (plan_outline); 0 means the plan covers the address. Oslo's register publishes no lifecycle status, so its plans are adopted when they carry an ikrafttredelse or vedtak date and unknown otherwise; in_progress (NAP planstatus 1 Planlegging igangsatt, 2 Planforslag) appears only where a register publishes it, and plans in hearing that the kommune has not yet registered are not seen. The list is in-progress first, then nearest, at most 100 plans; the counts cover every plan. Verify the plan and its provisions via plan_register_url / provisions_url.

Provider-contract fields

10 of 13 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
municipality_codestring | nullcontextopen
plans_within_500minteger | nullvalueopen
in_progress_within_500minteger | nullvalueopen
adopted_within_500minteger | nullvalueopen
other_within_500minteger | nullvalueopen
plans_within_1kminteger | nullvalueopen
in_progress_within_1kminteger | nullvalueopen
adopted_within_1kminteger | nullvalueopen
other_within_1kminteger | nullvalueopen
plans_covering_addressinteger | nullvalueopen
plansarray<object> | nullvalueopen
plans_listedinteger | nullcontextopen
updated_atstring | nullcontextopen

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

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