Trees and vegetation near the building
Available with: trial key (open fields) · 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.
- Crowns detected on the 1 m surface model minus the terrain model (height above ground 2.5-30 m, blob-shaped, not roof-like), so a count is a count of crown blobs, not of trunks, and a hedge of small trees may read as one. A blob wider than 12 m of crown radius is a forest edge rather than a tree, and is reported as nearest_woodland_m with kind woodland in the list; Norway's broadest single crowns stay inside that. Distances run from the building's edge to the crown's edge; the building is the roof blob under the Matrikkel building point (building_source matrikkel_point), else the roof-like blob nearest the address point (nearest_roof), else a 5 m disc around the point (address_point), in which case the distances are to the point. trees lists up to 25 crowns nearest the building with east_m/north_m from the address point, height_m and crown_radius_m. canopy_share_30m is the share of ground within 30 m of the address point under a crown. No record until vegetation-enrichment has reached the address.
Fields
11 of 13 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 |
|---|---|---|---|
| nearest_tree_crown_m | number | null | value | open |
| nearest_woodland_m | number | null | value | open |
| trees_within_10m | integer | null | value | open |
| trees_within_30m | integer | null | value | open |
| tallest_tree_within_10m_m | number | null | value | open |
| tallest_tree_within_30m_m | number | null | value | open |
| canopy_share_30m | number | null (andel) | value | open |
| trees | object | null | value | open |
| building_source | string | null | value | open |
| building_footprint_m2 | number | null (m2) | value | open |
| building_height_m | number | null (m) | value | open |
| method | string | null | context | open |
| computed_at | string | null | context | open |
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=vegetation' # 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/vegetation?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.