Skip to content

← All sections

Building cases and approved or started buildings within 250 m and 500 m of the address

Building cases and buildings within 250 and 500 metres of the address. Municipal case counts cover the archives Datakilde has ingested. The cadastral register provides separate counts for buildings with a recorded framework permit or start permit.

building_cases_nearby17 fieldsNot in the demo
Source
Bergen kommune innsyn plan og byggesak (open API, public records under offentleglova); Kartverket Matrikkelen bygningspunkt (CC BY 4.0)
Geography
Around the address
Reported stale after
30 days
Access
Requires an API key granted this section
Contract version
1
In packages
noise_and_nearby_projects

Read about this data source →

Status right now

State
Within budget
Combined section status is within the age and schedule budget. Check the separate data timestamp for data freshness.
Last loaded
7 Nov 2026
Data freshness evidence
Within budget
Newest stored data record 7 Nov 2026
Newest record
7 Nov 2026
Municipalities we hold data for
4601
From 2025-09-18 to 2026-11-06 · 9695
Coverage measurement: 22 Nov 2026, 11:40 · recently checked
Other municipalities have no rows in this snapshot; this does not mean “no cases”.
Municipalities with data
1

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: 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
Attribution and note

Shown from the contract in its original language.

The source publishes no licence.

API warnings

The API returns these notes in warnings.

  • Two halves. Building cases come only from kommuner whose case portal is ingested and may be passed on (GET /coverage, source building_cases_nearby): on 30 Sep 2026 Bergen alone, newest cases first, registered from Sep 2025. case_coverage says which applies: covered; not_covered (no case archive for the kommune; the case figures are null, not zero); or restricted (Oslo: the direct PBE saksinnsyn scrape has no licence and robots.txt disallows crawling, so this nearby section reports no PBE case figures). This does not block the separate building_applications section, which reads Oslo eInnsyn journal records on the exact cadastral unit. An empty list in a covered kommune still does not prove no case exists nearby.
  • approved/started buildings are national: Matrikkelen bygningspunkt buildings with status RA (rammetillatelse gitt) or IG (igangsettingstillatelse gitt) within the ring, null where the layer holds nothing for the kommune (buildings_covered). A status stays until completion is registered, so an old RA/IG can be a project that stalled or a completion never recorded. These are buildings, not cases, and Bergen's case archive records no rammetillatelse by that name; do not add the two halves together.
  • No applicant, tiltakshaver, ansvarlig søker or other person is served, and no case title or description: case_type (the procedural step) and measure_type (what is built or changed) are a fixed vocabulary read from the title and can be wrong or other. Cases are placed on the property by gnr/bnr against the address register; property_address is the register's address, not the case's. Bergen's portal publishes no open licence: these are public records, served as case metadata with a link to the municipal case page, whose documents can name the parties. Not in the anonymous demo or trial.

Provider-contract fields

12 of 17 fields are value fields — the ones that decide whether a record actually says anything. The rest are context: identifiers, codes and timestamps.

FieldTypeRole
municipality_codestring | nullcontext
case_coveragestring | nullvalue
cases_within_250minteger | nullvalue
open_within_250minteger | nullvalue
cases_within_500minteger | nullvalue
open_within_500minteger | nullvalue
cases_on_propertyinteger | nullvalue
latest_case_datestring | nullvalue
casesarray<object> | nullvalue
cases_listedinteger | nullcontext
buildings_coveredboolean | nullcontext
approved_started_buildings_within_250minteger | nullvalue
approved_started_buildings_within_500minteger | nullvalue
rammetillatelse_buildings_within_500minteger | nullvalue
igangsetting_buildings_within_500minteger | nullvalue
buildings_updated_atstring | nullcontext
updated_atstring | nullcontext

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=building_cases_nearby'

# 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/building_cases_nearby?limit=25'

Why it cannot be tried here

This section is not part of the public demo projection. That is a licensing and privacy decision, not a sign the data is missing: it is served to customers granted the section.