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 (30 FREDERICK ROAD, EDGBASTON) TPO 2004
- reference
- 1017
- name
- THE BIRMINGHAM (30 FREDERICK ROAD, EDGBASTON) TPO 2004
- tree-preservation-order
- TPO 1017
- tree-preservation-zone-type
- area
- geometry
- MULTIPOLYGON (((-1.919878 52.467534,-1.919015 52.467331,-1.918706 52.467974,-1.918740 52.468011,-1.918579 52.468281,-1.918496 52.468439,-1.918503 52.468457,-1.918482 52.468500,-1.918459 52.468507,-1.918391 52.468635,-1.918387 52.468647,-1.918421 52.468659,-1.918386 52.468718,-1.919247 52.468918,-1.919304 52.468813,-1.919216 52.468790,-1.919344 52.468573,-1.919257 52.468553,-1.919596 52.467936,-1.919659 52.467950,-1.919878 52.467534)))
- point
- POINT (-1.919101 52.468109)
- 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