How much can you build, and how much is used?

The zoning plans that cover a property, and how much of the permitted utilization has already been built, in two calls. Status separates an adopted plan from a proposal under consideration.

Logg inn med GitHubSlik ser det ut ↓Teknisk referanse →

Nøkkelen virker i dag på Leietaker-API og dagens Data API; Placepoint API godtar samme nøkkel når det lanseres.

Prøv med et ekte bygg: Oslo S, Jernbanetorget 1

• Trial key with GitHub in under a minute
• Two GET calls
• Plan and utilization
• Kartverket data
• Updated periodically

ℹ️ The endpoint responds once Placepoint API has launched. The contract below is final; the Tenant API already responds.

From property to plan and utilization

The calls answer two questions at once: which zoning plans apply to the property, and how much of the permitted utilization has already been built. Developers use it to screen sites quickly by remaining potential before ordering a full zoning analysis, estate agents to document building limits in a sales prospectus, and municipalities to check their own plan data against Placepoint's copy.

The plan list shows status, purpose and adoption date per plan, with the municipality number and links to the plan documents where they exist. A property can sit under several plan levels at the same time: an older zoning plan and a newer municipal master plan can apply in parallel until one is revoked, and a plan under consideration can sit alongside the adopted plan that still applies until a decision is made. The status field separates these, so you avoid reading a proposed plan as if it were already binding.

The utilization shows the permitted utilization rate as a percentage of built-up area and square metres of usable floor area, what has actually been built, and how much is left. The basis field says which plan the figures come from, so a difference between permitted and built area can be traced back to the right document rather than taken for granted. That makes the calculation verifiable in the same way as a manual review of plan maps and provisions, only without the review itself.

The plan documents are available as PDFs through signed download links, valid for 15 minutes from the moment the call returns them: zoning provisions, plan descriptions and other attachments registered on the plan.

• Two questions, one response

  Which zoning plans apply, and how much of the permitted utilization has already been built, without ordering a full zoning analysis.

• Status separates proposals from adopted plans

  The status field separates an adopted plan from one under consideration, so you avoid reading a proposal as if it were already binding.

• Plan documents as signed links

  Zoning provisions and plan descriptions come as PDFs through signed download links, valid for 15 minutes from the moment the call returns them.

Fields that actually tell you something

The zoning plans that cover the property.

GET/properties/{country}/{cadastreId}/zoning-plans

curl -X GET "https://data.placepoint.no/properties/NO/0301-207-76-0-0/zoning-plans" \
  -H "Authorization: Bearer $TOKEN"

svar · 200

{
  "items": [
    {
      "planId": "S-5028",
      "name": "Bjorvika, felt B13",
      "status": "ADOPTED",
      "purpose": "Bolig og forretning",
      "adoptedDate": "2011-06-15",
      "municipality": {
        "code": "0301",
        "name": "Oslo"
      },
      "documents": [
        {
          "id": "doc_9931a",
          "kind": "ZONING_PLAN",
          "title": "Reguleringsbestemmelser S-5028",
          "publishedDate": "2011-06-20",
          "downloadUrl": "https://data.placepoint.no/files/doc_9931a?sig=ab12cd34ef56&exp=1893456000",
          "mediaType": "application/pdf"
        }
      ]
    }
  ]
}

Scope: properties.readTeknisk referanse og Try-it

Vis alle felt (29)

Felt	Type	Beskrivelse
items[].planId	string	Plan identifier in the planregister.
items[].name	string	Plan name.
items[].status	string	Plan status.
items[].purpose	string	Permitted purpose, e.g. Bolig og forretning.
items[].adoptedDate	string	When the plan was adopted.
items[].planType	string	Which level of plan this is. AREA_DEVELOPMENT_PLAN is a VPOR and PLANNING_PROGRAM a planprogram; both bind development without being reguleringsplaner. The set grows as municipalities digitize more plan kinds; treat an unknown value as OTHER.
items[].verticalLevel	string	Vertical level the plan applies to, e.g. På grunnen.
items[].utilizationValue	number	Utilization figure the plan sets for the area.
items[].inEffectDate	string	When the plan came into effect.
items[].considerationZones[].code	string	Zone code in the planregister.
items[].considerationZones[].name	string	Zone name.
items[].considerationZones[].description	string	What the zone restricts.
items[].proposedBy	string	Who proposed the plan, e.g. Privat or Kommunen.
items[].finalizedDate	string	When the plan was finalized (vedtatt sluttbehandlet), where that differs from adoptedDate.
items[].minUtilizationValue	number	Minimum utilization the plan requires, where it sets one. utilizationValue carries the maximum.
items[].landUseStatus	string	Registered arealbruksstatus for the plan area.
items[].ownershipForm	string	Registered eierform for the plan area.
items[].firstDigitizedDate	string	When the plan was first digitized into the planregister.
items[].planUrl	string	The plan in the municipality's own planregister.
items[].municipality.code	string	Kommunenummer (Norway) or kommunkod (Sweden).
items[].municipality.name	string	Name.
items[].municipality.countyName	string	Fylke (Norway) or län (Sweden) the municipality belongs to.
items[].municipality.cityDistrictName	string	Bydel, where the municipality is divided into them.
items[].documents[].id	string	Document identifier.
items[].documents[].kind	string	Document category. The set grows as new archives are connected; treat an unknown value as OTHER.
items[].documents[].title	string	Document title.
items[].documents[].publishedDate	string	When the document was published.
items[].documents[].downloadUrl	string	Signed download URL, valid for 15 minutes.
items[].documents[].mediaType	string	IANA media type, e.g. application/pdf.

Permitted and built utilization rate.

GET/properties/{country}/{cadastreId}/utilization

curl -X GET "https://data.placepoint.no/properties/NO/0301-207-76-0-0/utilization" \
  -H "Authorization: Bearer $TOKEN"

svar · 200

{
  "allowedBya": 60,
  "allowedBraM2": 9200,
  "builtBraM2": 8400,
  "remainingBraM2": 800,
  "basis": "Regulert i S-5028, felt B13"
}

Scope: properties.readTeknisk referanse og Try-it

Vis alle felt (8)

Felt	Type	Beskrivelse
allowedBya	number	Allowed built-over percentage of plot area (bebygd areal).
builtBya	number	Built-over percentage of plot area today, computed from the registered buildings.
allowedBraM2	number	Allowed gross floor area in square meters.
builtBraM2	number	Built gross floor area in square meters.
remainingBraM2	number	Remaining allowed gross floor area in square meters.
utilizationType	string	Which figure the plan sets, since a plan states one of them rather than all: percentage of built-over area, percentage of gross floor area, or gross floor area per square meter of plot.
minUtilizationValue	number	Minimum utilization the plan requires, where it sets one.
basis	string	What the figures rest on, e.g. the applicable zoning plan.

Three steps to your first response

1. Log in with GitHub

   One click, under a minute, no payment card. The key comes back to this page.

2. Call the endpoint

   Replace $TOKEN in the curl above with your key; both calls only need the country code and the matrikkelnummer.

3. Use the response

   Use the plan list to document building limits in a sales prospectus, and the utilization figures to screen sites by remaining potential.

Data and sources

The zoning plans come from Kartverket's nationwide copy of the municipalities' zoning plans, updated periodically through Geonorge. The utilization figures are calculated by Placepoint from the plan's provisions and the matrikkel building data, and are updated when either of the two changes.

See also

• Map layer: Zoning
• Technical reference
• Placepoint API

Questions and answers

How fresh is the data?

The zoning plans are updated periodically through Geonorge. The utilization figures are recalculated when the plan's provisions or the matrikkel building data change.

What does the basis field mean?

basis shows which plan the utilization figures come from, so a difference between permitted and built area can be traced to the right document.

Can a property sit under several plans at the same time?

Yes. An older zoning plan and a newer municipal master plan can apply in parallel until one is revoked, and status separates a proposal from an adopted plan.

Does it work in Sweden?

Not yet. The zoning plans come from Kartverket's nationwide copy of Norwegian municipalities' plans; Swedish detaljplaner are not included in this call today.

Screen sites by remaining potential

Two calls give you the current zoning plans and how much of the permitted utilization has already been built. Log in with GitHub for a trial key.

Logg inn med GitHub