Trees worthy of conservation

Open data API in a single place

Provided by Københavns Kommune

Get early access to Trees worthy of conservation API!

Let us know and we will figure it out for you.

Dataset information

Country of origin
Updated
Created
Available languages
English
Keywords
Lokalplaner, belplantning, trægrupper, træer, bevaringsværdig, lokalplan, træ
Quality scoring

Dataset description

In the City of Copenhagen, the criteria for a tree to be designated as conservation worthy are that it is at least 20 years old and can live at least 25 years more at the time of designation. Size, character, location and state of health are also included in the assessment. A designated conservation-worthy tree may only be felled and pruned with permission from the TMF. Trees worthy of conservation are recorded when drawing up local plans. The trees worthy of conservation have been digitised in autumn 2018 based on all local plans from 2006 to 2018. The map attachments of the local plans combined with aerial photographs from spring 2018 have been used to identify the existing trees worthy of conservation. Digitalisation is indicative and should be aligned with the current local plan. In the data set, both a point layer and a polygon layer have the following main categories: * Conservation-worthy wood * Conservation-worthy wood on terms * Second character planting
European data infrastructure with broad catalog discovery, free evaluation access and production-grade API options.
190K+
indexed dataset pages
32
countries and EU institutions
2019
API-first since
Free API quota
for evaluation and prototypes
SLA
history and push on production APIs
FAQ

Questions before production use

Practical answers on evaluation, licensing, freshness, versioning and support.

api.store is built and operated by Apitalks s.r.o. Company details and a direct contact path are linked in the footer for vendor checks and procurement review.
Yes. Selected APIs include a free API quota, so your team can validate coverage, freshness, response shape and workflow fit before asking for a production plan.
Often yes, but usage rights depend on the source license and dataset. We surface source, license and update metadata where available, and can help review terms before a production integration.
Maintained APIs include update metadata where available. For production integrations, we can add history, monitoring and push updates so changes are easier to detect and act on.
Production APIs can add SLA, stable identifiers, versioning support, history, push updates and direct support around the data your product or AI workflow depends on.

Didn't find the API you need?

Let us know and we will figure it out for you.

European data discovery with free evaluation access and production-grade API options.

Copyright © 2026. Made by Apitalks