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 (12 AUSTEN PLACE, EDGBASTON) TPO 2004
- reference
- 1052
- name
- THE BIRMINGHAM (12 AUSTEN PLACE, EDGBASTON) TPO 2004
- tree-preservation-order
- TPO 1052
- tree-preservation-zone-type
- area
- geometry
- MULTIPOLYGON (((-1.917601 52.467277,-1.917359 52.467189,-1.917177 52.467357,-1.917069 52.467426,-1.916946 52.467441,-1.916825 52.467466,-1.916770 52.467501,-1.916727 52.467559,-1.916718 52.467585,-1.916724 52.467615,-1.916741 52.467641,-1.916799 52.467678,-1.916889 52.467667,-1.917050 52.467679,-1.917087 52.467676,-1.917138 52.467658,-1.917154 52.467646,-1.917217 52.467557,-1.917350 52.467588,-1.917440 52.467508,-1.917601 52.467277)))
- point
- POINT (-1.91717 52.467469)
- 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