Zoning-plan features at the address point

zoning_plan_features10 fields10 of these fields open in the demo

Source: Municipal plan register (WFS)
Geography: The address point
Reported stale after: 120 days
Access: Requires an API key granted this section
Contract version: 1
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.

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.

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” return values to anonymous callers; the rest require 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

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

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