Skip to main content

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

Newcastle-under-Lyme Borough Council

Tree preservation zone

There is a problem

  • tree-preservation-order column must match the reference field in the tree preservation order dataset

entity: 19205924

reference
T7-12\TPO0012_A1
name
tree-preservation-order

undefined

T7-12\TPO0012
tree-preservation-zone-type
area
geometry
MULTIPOLYGON (((-2.313167 52.949649,-2.313147 52.949609,-2.313126 52.949578,-2.313102 52.949552,-2.313057 52.949525,-2.312965 52.949491,-2.312885 52.949466,-2.312689 52.949411,-2.312444 52.949358,-2.312047 52.949293,-2.311971 52.949279,-2.311924 52.949276,-2.311854 52.949281,-2.311807 52.949288,-2.311768 52.949299,-2.311714 52.949315,-2.311589 52.949357,-2.311501 52.949405,-2.311436 52.949449,-2.311334 52.949531,-2.311333 52.949534,-2.311183 52.949667,-2.311061 52.949749,-2.310866 52.949850,-2.310852 52.949864,-2.310804 52.949888,-2.310730 52.949937,-2.310714 52.949953,-2.310703 52.949977,-2.310703 52.949992,-2.310706 52.950007,-2.310719 52.950030,-2.310732 52.950063,-2.310775 52.950113,-2.310812 52.950140,-2.310854 52.950159,-2.310904 52.950197,-2.311024 52.950255,-2.311068 52.950258,-2.311195 52.950253,-2.311348 52.950234,-2.311431 52.950217,-2.312001 52.950120,-2.312423 52.950087,-2.312747 52.950055,-2.312780 52.950050,-2.312842 52.950035,-2.312873 52.950027,-2.312939 52.950006,-2.313016 52.949976,-2.313051 52.949958,-2.313073 52.949945,-2.313104 52.949920,-2.313149 52.949868,-2.313165 52.949839,-2.313172 52.949822,-2.313182 52.949787,-2.313186 52.949751,-2.313184 52.949717,-2.313178 52.949682,-2.313167 52.949649)))
point
POINT (-2.311973 52.949782)
notes
entry-date
2026-07-28
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 Newcastle-under-Lyme 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