Skip to content

← All sections

Trees and vegetation near the building

Trees and woodland near the building, detected on Kartverket's 1 m height models: distance to the nearest crown, number and height of trees within 10 m and 30 m, and canopy share. Counts are crown blobs, not trunks.

vegetation13 fields13 of these fields open in the demo
Source
Kartverket høydedata DOM/DTM 1 m, detected by Approach
Geography
The address point
Reported stale after
400 days
Access
Requires an API key granted this section
Contract version
1

Read about this data source →

Status right now

State
Within budget
Combined section status is within the age and schedule budget. Check the separate data timestamp for data freshness.
Last loaded
22 Nov 2026
Data freshness evidence
Not measured yet
Unverified: only collection time is known.
Newest record
not measured

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

Model and method

How close are trees, and how much canopy is around the building?

This is model metadata from the contract. Results are estimates, not observed source facts. Declared maturity and reference comparison do not establish that the current model release is approved or available to the customer.

Result type
Calculation
Method
Geometric calculation
Declared maturity
Experimental
Reference comparison
No qualified comparison declared
Contract version
1
Model artifact and runtime version
Not established by this catalogue description
Inputs, headline fields and comparison basis

Declared inputs

  • DOM1 and DTM1 (Kartverket)

Headline output fields

nearest_tree_crown_m, trees_within_10m, trees_within_30m, tallest_tree_within_10m_m, tallest_tree_within_30m_m, canopy_share_30m, trees, building_source, building_footprint_m2, building_height_m, nearest_woodland_m

Declared comparison basis

none yet

Input names are not a complete training dataset or revision-pinned lineage. Read the caveats and response metadata for what a particular result is based on.

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
unverified
Declared redistribution
Not established
Catalogue basis
Unverified
Attribution and note

Shown from the contract in its original language.

Computed by Approach; the terms of its inputs named in source apply and have not been reviewed together.

API warnings

The API returns these notes in warnings.

  • 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.

Provider-contract 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” 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
nearest_tree_crown_mnumber | nullvalueopen
nearest_woodland_mnumber | nullvalueopen
trees_within_10minteger | nullvalueopen
trees_within_30minteger | nullvalueopen
tallest_tree_within_10m_mnumber | nullvalueopen
tallest_tree_within_30m_mnumber | nullvalueopen
canopy_share_30mnumber | null (andel)valueopen
treesobject | nullvalueopen
building_sourcestring | nullvalueopen
building_footprint_m2number | null (m2)valueopen
building_height_mnumber | null (m)valueopen
methodstring | nullcontextopen
computed_atstring | nullcontextopen

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=vegetation'

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