Skip to main content

This is a new service – your feedback will help us to improve it.

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 (HAYFIELD ROAD AND WAKE GREEN ROAD, WAKE GREEN) TPO 1969

reference
75
name
THE BIRMINGHAM (HAYFIELD ROAD AND WAKE GREEN ROAD, WAKE GREEN) TPO 1969
tree-preservation-order

undefined

TPO 75
tree-preservation-zone-type
area
geometry
MULTIPOLYGON (((-1.869664 52.442820,-1.869687 52.442665,-1.869779 52.442544,-1.869820 52.442451,-1.869995 52.441884,-1.870524 52.441904,-1.870536 52.441733,-1.870734 52.441740,-1.870872 52.441138,-1.870236 52.441129,-1.869998 52.441110,-1.869769 52.441075,-1.869743 52.441077,-1.869706 52.441099,-1.869622 52.441085,-1.869623 52.441072,-1.869609 52.441066,-1.869560 52.441060,-1.869460 52.441459,-1.869482 52.441470,-1.869476 52.441512,-1.869458 52.441512,-1.869462 52.441564,-1.869444 52.441696,-1.869470 52.441697,-1.869443 52.441812,-1.869454 52.441839,-1.869450 52.441858,-1.869528 52.441863,-1.869487 52.441941,-1.869477 52.441939,-1.869236 52.442387,-1.869067 52.442529,-1.869087 52.442556,-1.869089 52.442572,-1.869049 52.442636,-1.869061 52.442652,-1.869170 52.442688,-1.869664 52.442820)))
point
POINT (-1.869923 52.441776)
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

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL