Nearest protected nature areas

protected_nature_areas18 fields17 of these fields open in the demo

Source: Miljødirektoratet Naturbase
Geography: Around the address
Reported stale after: 180 days
Access: Requires an API key granted this section
Contract version: 2
In packages: outdoor_recreation

What this does not say

Quoted verbatim from the section’s warnings field, exactly as the API returns it. They are not translated: a translation would show something other than what your response actually contains.

Distance is measured to the area's outline and contains_address says whether the address falls inside it. The outline is generalised at source (geometry_tolerance_deg, in degrees — roughly a kilometre at Norwegian latitudes), so within that distance of a boundary neither the distance nor contains_address decides anything: this is an address-resolution answer, not a legal boundary determination. lat/lon are a point inside the area for labelling, never a distance origin.
Only areas within 20 km are returned. An empty section means no protected area within that radius, not that the address is unrestricted.
Routes follow the car profile, from the address to the feature; ranking remains straight-line. Static modelled travel time excludes live traffic and emergency response. Road snapping is limited to 250 m at each end. Ferries may be included without timetable/wait guarantees. Graph source date is unverified unless supplied. © OpenStreetMap contributors, ODbL: https://www.openstreetmap.org/copyright
walk_route and cycle_route follow OSRM's foot and bicycle profiles on the same OpenStreetMap data: paths and stairs allowed on foot, road rules for bicycles; modelled times at profile default speeds, not measured.

Fields

5 of 18 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” return values to anonymous callers; the rest require a key.

Field	Type	Role	Demo
area_id	string \| null	context	open
name	string \| null	value	open
official_name	string \| null	context	open
protection_type	string \| null	value	open
protection_plan	string \| null	context	open
iucn_category	string \| null	context	open
factsheet_url	string \| null	context	open
protection_date	string \| null	context	open
area_km2	number \| null (km2)	value	open
geometry_tolerance_deg	number \| null (grader)	context	—
lat	number \| null	context	open
lon	number \| null	context	open
straight_line_distance_m	integer \| null (m)	value	open
contains_address	boolean \| null	value	open
fetched_at	string \| null	context	open
route	object	context	open
walk_route	object	context	open
cycle_route	object	context	open

Fetch this section

curl -H "X-API-Key: $APPROACH_API_KEY" \
  "https://api.approach.no/api/v1/addresses/285717643?include=protected_nature_areas"

# paginated, one section at a time
curl -H "X-API-Key: $APPROACH_API_KEY" \
  "https://api.approach.no/api/v1/addresses/285717643/sections/protected_nature_areas?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.