Red-listed and high-risk alien species observed within 250 m, last 20 years
species_observations12 fieldsNot in the demo
Available with: bought bundle or agreed plan (all fields) · Pricing
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.
- Observations reported to Artskart of species on the Norwegian Red List (CR critically endangered, EN endangered, VU vulnerable, NT near threatened) and alien species assessed as very high (SE) or high (HI) ecological risk, whose published position lies within 250 m of the address point in the last 20 years. An observation is a report, not a population: a passing bird counts, and an unsurveyed garden has none. Not an environmental assessment; a planning case decides what a find means for the plot.
- Positions are never served. Artskart generalises the position of sensitive species before publishing it, and this section passes on only counts and species names, so nothing more precise than Artskart's own public map is exposed. coarse_precision_observations counts observations whose stated uncertainty exceeds 250 m: their true position may lie outside the radius, and finds just outside may belong inside.
- Attribution: data from Artsdatabanken's Artskart, CC BY 4.0, compiled from many contributing datasets. observation_status harvest_incomplete_for_kommune means the national collection has not yet reached every status for the address's kommune, so counts may be low; not_loaded means nothing is collected and every count is null.
Fields
6 of 12 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 |
|---|---|---|
| observation_status | string | null | context |
| radius_m | integer | null | context |
| window_from | date | null | context |
| redlisted_observations | integer | null | value |
| redlisted_species | integer | null | value |
| alien_high_risk_observations | integer | null | value |
| alien_high_risk_species | integer | null | value |
| by_status | object | null | value |
| species | array<object> | null | value |
| coarse_precision_observations | integer | null | context |
| latest_observed_on | 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=species_observations' # 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/species_observations?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.