Skip to main content

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

Wirral Borough Council

Tree preservation zone

There is a problem

  • You have 6 tree preservation zones outside of your boundary

Entity: 19167026

dataset
tree-preservation-zone
end-date
entity
19167026
entry-date
1953-09-03
geojson
geometry
MULTIPOLYGON (((-2.978650 53.301582,-2.978311 53.300653,-2.978177 53.300694,-2.978114 53.300711,-2.978070 53.300718,-2.978017 53.300738,-2.977940 53.300762,-2.977597 53.300865,-2.977361 53.300938,-2.977018 53.301039,-2.976682 53.301143,-2.976470 53.301205,-2.976272 53.301269,-2.976174 53.301295,-2.976123 53.301312,-2.976076 53.301325,-2.975959 53.301362,-2.975765 53.301417,-2.975573 53.301476,-2.975078 53.301621,-2.974676 53.301736,-2.974352 53.301832,-2.974540 53.302041,-2.974671 53.302179,-2.974826 53.302353,-2.975063 53.302291,-2.975103 53.302353,-2.975135 53.302381,-2.975164 53.302426,-2.975215 53.302481,-2.975225 53.302497,-2.975246 53.302542,-2.975274 53.302588,-2.975270 53.302607,-2.975242 53.302621,-2.975199 53.302637,-2.975184 53.302640,-2.975118 53.302644,-2.975083 53.302638,-2.975127 53.302663,-2.975271 53.302631,-2.975397 53.302599,-2.975449 53.302581,-2.975526 53.302561,-2.975603 53.302534,-2.975670 53.302520,-2.975930 53.302434,-2.976001 53.302415,-2.976088 53.302385,-2.976174 53.302359,-2.976360 53.302297,-2.976491 53.302258,-2.976565 53.302232,-2.976640 53.302210,-2.976876 53.302136,-2.977195 53.302031,-2.977683 53.301887,-2.977834 53.301834,-2.978320 53.301676,-2.978535 53.301612,-2.978650 53.301582)))
name
Bebington Borough Council BB0011
organisation-entity
384
point
POINT (-2.976621 53.301668)
prefix
tree-preservation-zone
quality
authoritative
reference
BB0011W027
start-date
1953-09-03
typology
geography
notes
New Chester Road, Eastham. Hooton Road,Rivacre Road, Hooton
tree-preservation-zone-type
woodland
tree-preservation-order
BB0011

How to improve Wirral Borough 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