Urban Morphological Zones Changes 2000-2006 (vector) - version 16, Jun. 2013

Open data API in a single place

Provided by The European environmental Agency (EEA)

Get early access to Urban Morphological Zones Changes 2000-2006 (vector) - version 16, Jun. 2013 API!

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

Dataset information

Catalog

The European environmental Agency (EEA) catalog

Country of origin

EU institutions

Updated

Created

Available languages

English

Keywords

Netherlands, Germany, Austria, Ireland, Cyprus, Liechtenstein, Serbia, Albania, Denmark, Luxembourg, Sweden, Montenegro, Finland, Belgium, Bulgaria, North Macedonia, Slovakia, Hungary, Poland, Czechia, Switzerland, Latvia, Slovenia, Croatia, Italy, Estonia, Spain, Portugal, Norway, Malta, Bosnia and Herzegovina, Türkiye, United Kingdom, Iceland, Romania, Lithuania, France

Datasource

Official portal for European data link

Quality scoring

Dataset description

Changes between UMZs in 2000 and UMZs in 2006 using CLC version 16. Most changes are Positive changes, understood as areas of urban sprawl (i.e. new UMZ areas between 2000 and 2006), while negative changes describe the reduction of a certain UMZ between 2000 and 2006 (warning: some negative changes might be due to different interpretations between 2000-2006).

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