Zoning-plan features at the address point
Legacy section: land-use purposes (arealformål) and utilisation features from loaded municipal plan registers whose geometry covers the address point. Kept for existing integrations; the planning section replaces it.
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: 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).
- Arealformål and utnyttelse features whose geometry covers the address point, from the municipal plan registers we have loaded (currently Oslo PBE); no feature means not loaded for this municipality, not unregulated. See zoning_plan for the plan itself.
Provider-contract fields
3 of 10 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 |
|---|---|---|---|
| id | integer | null | context | open |
| plan_id | string | null | context | open |
| feature_type | string | null | value | open |
| subtype | string | null | value | open |
| purpose | string | null | value | open |
| plan_name | string | null | context | open |
| confidence | number | null | context | open |
| source_system | string | null | context | open |
| municipality_code | string | null | context | open |
| created_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_features'
# 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_features?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.