Birmingham City Council
Tree preservation zone
There is a problem
- 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order dataset
THE BIRMINGHAM (61 ST. MARY'S ROW AND LAND ADJOINING 61 & 63 ST. MARY'S ROW, MOSELEY) TPO 2004
- reference
- 1011
- name
- THE BIRMINGHAM (61 ST. MARY'S ROW AND LAND ADJOINING 61 & 63 ST. MARY'S ROW, MOSELEY) TPO 2004
- tree-preservation-order
- TPO 1011
- tree-preservation-zone-type
- area
- geometry
- MULTIPOLYGON (((-1.885050 52.446119,-1.885211 52.446485,-1.885110 52.446612,-1.885521 52.446651,-1.885712 52.446365,-1.885959 52.446034,-1.885773 52.446020,-1.885545 52.446029,-1.885268 52.446074,-1.885241 52.446087,-1.885228 52.446113,-1.885192 52.446120,-1.885133 52.446097,-1.885050 52.446119)))
- point
- POINT (-1.885462 52.446298)
- notes
- The shaded area represents those properties which fall within the outline of a Tree Preservation Order. To precisely identify trees protected by the Order, you can request a copy of the tree preservation order at the following link.
- organisation
- entry-date
- 2025-11-30
- start-date
- end-date
How to fix this issue
Your dataset is missing the tree-preservation-order column.
The Tree preservation zone guidance explains how to fix the issue:
tree-preservation-order
The reference for the tree preservation order that covers this zone.
How to improve Birmingham City Council’s data
- Fix the errors indicated
- Use the check service to make sure the data meets the standard
- Publish the updated data on the endpoint URL