CORINE Land Cover and Changes (CLC and CHA, Lithuania) 1990–2012

Open data API in a single place

Provided by Viešoji įstaiga Statybos sektoriaus vystymo agentūra

Get early access to CORINE Land Cover and Changes (CLC and CHA, Lithuania) 1990–2012 API!

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

Dataset information

Catalog

Viešoji įstaiga Statybos sektoriaus vystymo agentūra catalog

Country of origin

Lithuania

Updated

2026.04.07 00:00

Created

2025.03.04

Available languages

English

Keywords

atviri duomenys, open data, pokyčiai, land cover, changes, Žemės Danga, soil, corine, clc, land use

Datasource

Official portal for European data link

Quality scoring

Dataset description

BThe Corine Land Cover (CLC) database is a pan-European vector dataset of land cover, divided into 44 classes (30 classes cover the territory of Lithuania) according to land cover type and land use. Currently, five datasets have been created (for the years 1990, 2000, 2006, 2012 and 2018) describing the land cover for the years in question and the changes in land cover since the previous database. The CHA change databases are constructed by inputting land cover changes between the two years. The minimum mapping is 25 ha for linear features and 100 m for linear features. The minimum mappable object in the change database is 5 ha for areal objects, with a minimum object width of 100 m.

European data infrastructure with broad catalog discovery, free evaluation access and production-grade API options.

190K+

indexed dataset pages

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.

api.store Built by Apitalks

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

About api.storePrivacy Terms of Service