Urban Morphological Zones 2000 (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 2000 (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

Bosnia and Herzegovina, Montenegro, North Macedonia, EEA33 (2013-2020), Albania, San Marino, Serbia

Datasource

Official portal for European data link

Quality scoring

Dataset description

An urban morphological zone (UMZ) is defined as a "set of urban areas laying less than 200 m apart". This layer contains UMZ delineations for Europe, based on Corine Land Cover database. During 2012, the UMZ methodology was updated in order to correct errors derived for the water course as join elements between urban areas. Previous version applied over CLC v15 (and previous version) joined many small urban areas due to the water presence. This fact was erroneous from the landscape and urban perspective as most of those areas remain as urban-rural typologies. Moreover, water courses cannot be considered as roads from the urban morphological view (either from the commuting point of understanding). This new version, known as v16, corrected this effect in the majority of cases.

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