Skip to content

← All sections

Cultural heritage localities near the address

Cultural-heritage localities from Riksantikvaren's Askeladden near the address, with category, protection type and law, monument count and distance. Says whether the address point lies inside a locality.

heritage_sites12 fields12 of these fields open in the demo
Source
Riksantikvaren Askeladden via Geonorge
Geography
Around the address
Reported stale after
47 days
Access
Requires an API key granted this section
Contract version
1
In packages
planning_restrictions, plot_and_zoning

Read about this data source →

Status right now

State
Stale
The clock used for combined section status is older than its limit. Data freshness is shown separately.
Last loaded
14 Sept 2026
Data freshness evidence
Stale
Newest stored data record 14 Sept 2026
Newest record
14 Sept 2026
Municipalities with data
358

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.

  • Askeladden localities carry legal protection (kulturminneloven) when vernestatus says so; contains_address true means the address point lies inside a locality polygon and any ground work may require permission.
  • Straight-line EPSG:25833 distances from the address point to the feature; not travel distance. Source features are imported as published, with their own accuracy and update cadence; updated_at is our import time.

Provider-contract fields

2 of 12 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.

FieldTypeRoleDemo
feature_idstring | nullcontextopen
labelstring | nullcontextopen
municipality_codestring | nullcontextopen
updated_atstring | nullcontextopen
locality_categorystring | nullcontextopen
locality_kindstring | nullcontextopen
protection_typestring | nullcontextopen
protection_lawstring | nullcontextopen
monument_countinteger | nullcontextopen
factsheet_urlstring | nullcontextopen
straight_line_distance_minteger | null (m)valueopen
contains_addressboolean | nullvalueopen

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

# 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/heritage_sites?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.