Estonian vegetation height model (CHM - Canopy Height Model)

Open data API in a single place

Provided by Maa-amet

Get early access to Estonian vegetation height model (CHM - Canopy Height Model) API!

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

Dataset information

Country of origin
Updated
Created
2015.03.27
Available languages
English
Keywords
kõrgusmudel, DEM, digital elevation model, canopy height model, CHM, reljeefimudel, taimkatte kõrgusmudel, 3D, reljeef, kõrgusandmed
Quality scoring

Dataset description

The vegetation height model (CHM - Canopy Height Model) shows the height of vegetation above the ground. The data cover the whole of Estonia (except for small areas on the south-eastern border). The model is divided into height classes where pixels with a value of less than 1 metre are transparent. The following altitude classes are: pixels with a value of 1-4 m, 4-10 m, 10-20 m, 20-30 m and more than 30 m. The calculation assumes that there are no trees more than 50 metres high in Estonia. Data resolution 4-10m (pixel size 4m is in use from 2017 until 2016 data is 10m). Heights are in 0.5m steps. The first layer of the vegetation height model covering Estonia is from 2008 to 2011, after which the layers are already separated by years and the summer and spring flight areas are separated.
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