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 (UMBERSLADE ROAD/ RIBBLESDALE ROAD, STIRCHLEY) TPO 1994
- reference
- 648
- name
- THE BIRMINGHAM (UMBERSLADE ROAD/ RIBBLESDALE ROAD, STIRCHLEY) TPO 1994
- tree-preservation-order
- TPO 648
- tree-preservation-zone-type
- area
- geometry
- MULTIPOLYGON (((-1.926679 52.432520,-1.926418 52.432338,-1.926153 52.432149,-1.925866 52.431948,-1.925611 52.431767,-1.925445 52.431647,-1.925208 52.431480,-1.924868 52.431241,-1.924315 52.430855,-1.924293 52.430841,-1.924059 52.430982,-1.923994 52.431018,-1.923877 52.431072,-1.923544 52.431205,-1.923430 52.431254,-1.923184 52.431366,-1.923170 52.431374,-1.923161 52.431387,-1.923161 52.431399,-1.923169 52.431411,-1.923248 52.431469,-1.923453 52.431609,-1.923738 52.431811,-1.923962 52.431966,-1.924406 52.432279,-1.924586 52.432184,-1.924589 52.432181,-1.924615 52.432173,-1.924672 52.432169,-1.924692 52.432171,-1.924705 52.432174,-1.924723 52.432184,-1.924845 52.432241,-1.924939 52.432282,-1.925313 52.432084,-1.925660 52.432211,-1.925795 52.432280,-1.925964 52.432369,-1.926322 52.432564,-1.926422 52.432632,-1.926449 52.432652,-1.926475 52.432639,-1.926617 52.432558,-1.926679 52.432520)))
- point
- POINT (-1.92469 52.43171)
- 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.
- entry-date
- 2026-06-25
- start-date
- end-date
How to fix this issue
Your data is missing a tree-preservation-order.
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