Depave v1.0 — Amsterdam

Base map

Streets Satellite Crop to city boundary

opacity

Needs assessment by buurt

Heat burden Stormwater flood risk Canopy deficit Pavement burden

Composite

Combined needs score Priority tracts

Where is depaving possible?

Layer styling

By pavement category By depaving potential

Depaving potential No potential

How much can actually be depaved?

Within the depaving-potential categories, by a zoning logic per pavement type.

loading…

Ownership scope. The map shows only pavement on land gemeente Amsterdam owns AND has not leased out (erfpacht). Private land, leased land, and national land (Rijkswaterstaat highways, ProRail rail) are clipped out — depaving is a public-realm action on City land.

Why Westpoort looks empty. It's a port / industrial zone: ~83% of its pavement sits on leased or private terminals and national highways, so the public-land clip removes it. Only the small City-owned public realm remains.

Private / national roads (Rijkswaterstaat highways) and national rail (ProRail) are folded into Roads and Railway / tram and counted in their totals, even though they sit on non-City land and are not themselves depave candidates.

Data sources. Pavement from the BGT (Kadaster / PDOK) and ownership from the BRK; neighbourhood units and population from CBS. Heat and flood layers from the Klimaateffectatlas. Tree canopy from the Bomenkaart 2022, published by Atlas Natuurlijk Kapitaal (ANK), www.atlasnatuurlijkkapitaal.nl — attribution required by the publisher's licence. Basemaps © OpenStreetMap contributors, © CARTO; satellite imagery © Esri.

Summary

loading…