Land Uptake per Person (inhabitants and jobs) (LUP) 2009 (LEAC Grid), Nov. 2016

Open data API in a single place

Provided by The European environmental Agency (EEA)

Get early access to Land Uptake per Person (inhabitants and jobs) (LUP) 2009 (LEAC Grid), Nov. 2016 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

2016.12.16

Available languages

English

Keywords

Buildings, Population distribution — demography

Datasource

Official portal for European data link

Quality scoring

Dataset description

The new urban sprawl metric, named "Weighted Urban Proliferation“ (WUP) is based on the following definition of urban sprawl: the more area is built over in a given landscape (amount of built-up area) and the more dispersed this built-up area is in the landscape (spatial configuration), and the higher the uptake of built-up area per inhabitant or job (lower utilisation intensity in the built-up area), the higher the degree of urban sprawl. Weighted Urban Proliferation (WUP) metric has three components: the percentage of built-up areas (PBA), the dispersion of the built-up areas (DIS), and land uptake per person (LUP). Land uptake per person (inhabitants and jobs) (LUP) describes the use of urban built-up area by people working and living in that area.

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