Zoning plans covering the address point
Zoning plans (reguleringsplaner) whose area covers the address point, with plan name, type, status, adoption and in-force dates and links to the provisions. Several plans at different levels can apply to the same point.
Status right now
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: approved pilot customer and named section access
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.
DiBK NAP plan register (Norge digitalt): reuse terms for customers not confirmed. Pending legal review.
API warnings
The API returns these notes in warnings.
- Point-in-polygon lookup against ingested plan geometries (currently Oslo), with a live lookup in DiBK's national plan base (NAP) at the point everywhere else. No match never means the address is unregulated: a kommune that has not published to NAP answers nothing. Verify the legally binding plan and provisions via plan_register_url/provisions_url.
- Overlapping plans, including kommunedelplaner and different vertical levels, can all apply to the same point; plan_status can be empty in the source register.
- Where no ingested polygon covers the point, the plan is read live from DiBK's national plan base (NAP) WMS at the address point and marked source_system dibk-nap-wms; NAP carries what the kommune has published to it, so a kommune outside NAP still answers no match.
Provider-contract fields
6 of 16 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.
| Field | Type | Role | Demo |
|---|---|---|---|
| plan_id | string | null | context | open |
| national_plan_id | string | null | context | open |
| municipality_code | string | null | context | open |
| plan_name | string | null | value | open |
| plan_name_short | string | null | context | open |
| plan_type | string | null | value | open |
| plan_type_name | string | null | context | open |
| plan_status | string | null | value | open |
| adopted_date | string | null | value | open |
| in_force_date | string | null | value | open |
| vertical_level | integer | null | context | open |
| provisions_code | string | null | context | — |
| provisions_url | string | null | value | open |
| plan_register_url | string | null | context | open |
| source_system | string | null | context | open |
| updated_at | string | null | context | open |
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=zoning_plan'
# 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/zoning_plan?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.