Current zoning plans ArnhemBestemmingsplannen vigerend Arnhem
Bestemmingsplannen vigerend ArnhemCurrent zoning plans Arnhem
Dataset providing the current (vigerend) zoning plans (bestemmingsplannen) of the Dutch municipality of Arnhem. Since 2001 Arnhem has produced its spatial plans digitally at source, meaning any paper version is derived from the digital original. Since 1 January 2010, digital publication of spatial plans has been a legal requirement in the Netherlands, and these plans are made available through the national spatial plans register. The dataset covers the municipality's land-use designations and planning rules for specific areas, and is published via the national open data portal data.overheid.nl.Vanaf 2001 maakt de gemeente Arnhem (vrijwel) al haar ruimtelijke plannen digitaal bij de bron. Dat wil zeggen dat de papieren versie een afgeleide is van de digitale bron. Vanaf 1 januari 2010 is het digitaal publiceren van ruimtelijke plannen zelfs wettelijk verplicht. In de landelijke voorzien...
Trust score
How is this computed?Weighted across five axes. Tap a ring for what it measures.
Data schema (8 fields)
Click a field to see example values.
| Field | Type | Description |
|---|---|---|
| OBJECTID | oid | Internal unique record identifier.Internal unique record identifier. |
| NAAM | string | Name of the zoning plan (bestemmingsplan).Name of the zoning plan (bestemmingsplan). |
| ID_PLN_WROId pln wro | smallinteger | Numeric identifier of the plan in the WRO system.Numeric identifier of the plan in the WRO system. |
| URL | string | Link to the plan's page on the Arnhem spatial plans website.Link to the plan's page on the Arnhem spatial plans website. |
| SHAPE | geometry | Geometric shape representing the plan's spatial boundary.Geometric shape representing the plan's spatial boundary. |
| SHAPE.STArea() | double | Area of the plan's geometry, in square units.Area of the plan's geometry, in square units. |
| SHAPE.STLength() | double | Perimeter length of the plan's geometry, in units.Perimeter length of the plan's geometry, in units. |
| CADTEXT | string | Cadastral or label text associated with the plan.Cadastral or label text associated with the plan. |
Schema captured from arcgis 17 hours ago.
Query the data
Pick columns and a sort, then fetch a live preview straight from the source. Choose an API-filterable column (marked ▾) under “Where” to pick from its list of values.
Sample data (3 records)
| OBJECTID | NAAM | ID_PLN_WRO | URL | SHAPE.STArea() | SHAPE.STLength() |
|---|---|---|---|---|---|
| 1 | Hoogkamp-Sterrenberg-Gulden Bodem | 640 | https://open.arnhem.nl/ruimtelijkeplannen/plannen/BP00/NL.IMRO.02020000640-/ | 333.974585 | 676.4315888143757 |
| 2 | Bedrijventerrein Westervoortsedijk | 649 | https://open.arnhem.nl/ruimtelijkeplannen/plannen/BP00/NL.IMRO.02020000649-/ | 198942.220333075 | 6077.33424752363 |
| 3 | Geitenkamp | 614 | https://open.arnhem.nl/ruimtelijkeplannen/plannen/BP00/NL.IMRO.02020000614-/ | 5232.474191 | 345.51854874404705 |
Live sample captured at profiling time — values may have changed upstream.
Verification Status
Using the API
Query examples
curl -s 'https://geo.arnhem.nl/arcgis/rest/services/OpenData/BP_geldend/MapServer?f=json' -H 'Accept: application/json'Service definition: the list of layers.
Dataset
Volume & freshness
License
No license declared upstream.
Distributions (1)
Plangebied 00 vigerend (GeoJSON)
https://geo.arnhem.nl/arcgis/rest/services/OpenData/BP_geldend/MapServer/0/query?where=1%3D1&outFields=*&f=geojsonSource: arcgis
Machine-readable & source
Embed this badge in a README or wiki — it always shows the latest verification state and quality tier.