Wildlife killed by road and rail traffic within 1 km, last five years

wildlife_collisions11 fieldsNot in the demo

Source: Hjorteviltregisteret Fallvilt (Landbruksdirektoratet / Naturdata); licence not stated by the source
Geography: The address point
Reported stale after: 30 days
Access: Requires a separate agreement (Hjorteviltregisteret reuse terms (Landbruksdirektoratet; licence not stated))
Contract version: 1

Available with: a separate agreement, switched on per account · Ask about an agreement

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.

Registered fallvilt killed by motor vehicles or trains within 1 km straight-line distance of the address point over the last five years: moose, red deer, roe deer and the other species the municipalities register. A count of registered finds, not of collisions: an animal that ran off and was not searched for is not in it, and registration practice varies by kommune. Not a collision risk score.
The source states no licence. The section is available only under a separate agreement until Landbruksdirektoratet confirms reuse terms, and its collector is switched off until then.
collision_status register_not_loaded means we hold no fallvilt events and every count is null; no_collision_within_radius means the register is loaded and none was registered within 1 km. Positions are the finder's, often on the road edge.

Fields

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

Field	Type	Role
collision_status	string \| null	context
radius_m	integer \| null	context
window_from	date \| null	context
road_collisions	integer \| null	value
rail_collisions	integer \| null	value
collisions_per_year	number \| null (årstall)	value
collisions_by_species	object \| null	value
collisions_by_year	object \| null	context
nearest_collision_distance_m	integer \| null (m)	value
latest_collision_date	date \| null	context
fetched_at	timestamp \| null	context

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 --fail-with-body --silent --show-error \
  -H "X-API-Key: $APPROACH_API_KEY" \
  'https://api.approach.no/api/v1/addresses/285717643?include=wildlife_collisions'

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