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: 19205955

reference
T6-11\TPO011A_A2
name
tree-preservation-order

undefined

T6-11\TPO011A
tree-preservation-zone-type
area
geometry
MULTIPOLYGON (((-2.221858 53.036540,-2.221874 53.036568,-2.221943 53.036622,-2.222026 53.036637,-2.222037 53.036635,-2.222074 53.036634,-2.222091 53.036630,-2.222124 53.036628,-2.222151 53.036622,-2.222182 53.036619,-2.222192 53.036616,-2.222249 53.036587,-2.222305 53.036553,-2.222334 53.036532,-2.222356 53.036512,-2.222362 53.036504,-2.222381 53.036471,-2.222432 53.036353,-2.222441 53.036327,-2.222457 53.036289,-2.222476 53.036229,-2.222480 53.036203,-2.222480 53.036190,-2.222376 53.035923,-2.222373 53.035920,-2.222365 53.035917,-2.222356 53.035916,-2.222347 53.035913,-2.222343 53.035910,-2.222330 53.035884,-2.222308 53.035886,-2.222280 53.035897,-2.222245 53.035922,-2.222237 53.035936,-2.222117 53.036092,-2.222047 53.036177,-2.222039 53.036184,-2.222010 53.036218,-2.221867 53.036371,-2.221834 53.036400,-2.221823 53.036441,-2.221858 53.036540),(-2.222284 53.036276,-2.222313 53.036281,-2.222318 53.036285,-2.222318 53.036362,-2.222303 53.036362,-2.222303 53.036437,-2.222100 53.036438,-2.222100 53.036459,-2.222050 53.036459,-2.222050 53.036437,-2.222030 53.036408,-2.222011 53.036337,-2.222011 53.036304,-2.222016 53.036293,-2.222023 53.036284,-2.222037 53.036277,-2.222284 53.036276)))
point
POINT (-2.222185 53.036304)
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