Where does the boundary run?
The property's registered boundary as GeoJSON in WGS84, ready to draw straight into a map without a separate conversion from UTM first.
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
- One GET call
- GeoJSON
- WGS84
- Updated continuously
ℹ️ The endpoint responds once Placepoint API has launched. The contract below is final; the Tenant API already responds.
From matrikkelnummer to plot boundary
The call tells you exactly where a property runs on the ground, as geometry and not just as text. Developers building their own map interfaces need the boundary as a polygon to draw, estate agents making map extracts for a sales prospectus avoid drawing the boundary by hand, and municipalities comparing their own planning data against Placepoint's copy need the same geometry in both places.
The answer is one simple GeoJSON object: type is always Feature, geometry is a Polygon in WGS84, and properties is empty for a property boundary. A building's footprint fills the same field with height and number of floors instead, see Building footprints.
The geometry comes from the same matrikkel and FKB basis that the map interface draws from itself, so a property looks identical in your own application as it does in Placepoint Fusion.
GeoJSON in WGS84, ready to draw
No separate conversion from UTM. The geometry goes straight into a map layer, in the same coordinate system most map libraries and mobile devices already work in.The same basis as the map interface
The boundary comes from the same matrikkel and FKB basis that the map interface draws, so the property looks identical in both places.One geometry per property
A property with several parcels returns one combined geometry, not one per parcel, so you do not have to merge them yourself.
Fields that actually tell you something
One GET call with the matrikkelnummer gives you the boundary. The fields below are the three that make up the whole GeoJSON answer.
/properties/{country}/{cadastreId}/boundarycurl -X GET "https://data.placepoint.no/properties/NO/0301-207-76-0-0/boundary" \
-H "Authorization: Bearer $TOKEN"
svar · 200
{
"type": "Feature",
"geometry": {
"type": "Polygon",
"coordinates": [
[
[
10.7561,
59.9074
],
[
10.7565,
59.9074
],
[
10.7565,
59.9077
],
[
10.7561,
59.9077
],
[
10.7561,
59.9074
]
]
]
},
"properties": {}
}
The boundary can be drawn directly in a map library such as MapLibre GL JS:
const res = await fetch(`${base}/properties/NO/${cadastreId}/boundary`, {
headers: { Authorization: `Bearer ${token}` },
});
const boundary = await res.json();
map.addSource("tomtegrense", { type: "geojson", data: boundary });
map.addLayer({
id: "tomtegrense-linje",
type: "line",
source: "tomtegrense",
paint: { "line-color": "#1d4ed8", "line-width": 2 },
});
Three steps to your first answer
Log in with GitHub
One click, under a minute, no payment card. The key comes back to this page.Call the endpoint
The curl above fills itself in with your key when you are logged in. The call only needs the country code and the matrikkelnummer.Apply the answer
Put the GeoJSON object straight into your map library as a source, as the snippet above shows for MapLibre GL JS.
Data and sources
The boundaries come from the matrikkel at Kartverket, updated continuously through Geonorge.