Skip to content

← All sections

Potentially accessible shore zone (100 m belt)

SSB's statistical potentially accessible shoreline, excluding developed/cultivated land and transport areas. A match is not the complete 100 m belt, access rights or a legal prohibition. No match does not rule out shoreline restrictions; verify current plans, boundaries and exceptions with the municipality.

shore_zone6 fields6 of these fields open in the demo
Source
SSB Strandsone
Geography
Around the address
Reported stale after
47 days
Access
Requires an API key granted this section
Contract version
1
In packages
legal, outdoor_recreation, 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
28 Sept 2026
Data freshness evidence
Stale
Newest stored data record 28 Sept 2026
Newest record
28 Sept 2026
Municipalities with data
226

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
Creative Commons Attribution 4.0
Declared redistribution
Allowed with attribution
Catalogue basis
Publisher terms
Read the publisher terms →
Attribution and note

Shown from the contract in its original language.

© SSB Strandsone, CC BY 4.0

API warnings

The API returns these notes in warnings.

  • SSB's statistical potentially accessible shoreline layer excludes building-near land, cultivated land, roads and railways. contains_address means membership in the imported statistical polygon, not the complete statutory 100 m belt, a public access right or a legal building prohibition. An absent match does not place the property outside the 100 m belt. Verify the shoreline, current plan/building boundaries and any exceptions with the municipality; this layer cannot determine legal applicability.
  • 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 6 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
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=shore_zone'

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