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

reference
T7-103\TPO0103_W1
name
tree-preservation-order

undefined

T7-103\TPO0103
tree-preservation-zone-type
woodland
geometry
MULTIPOLYGON (((-2.442359 52.898423,-2.442242 52.898379,-2.442156 52.898349,-2.442096 52.898324,-2.441992 52.898248,-2.441976 52.898234,-2.441930 52.898209,-2.441744 52.898161,-2.441724 52.898154,-2.441580 52.898085,-2.441509 52.898053,-2.441463 52.898035,-2.441419 52.898021,-2.441391 52.898010,-2.441342 52.897987,-2.441299 52.897970,-2.441251 52.897987,-2.441212 52.898006,-2.441145 52.898033,-2.441078 52.898063,-2.441031 52.898079,-2.440981 52.898092,-2.440931 52.898108,-2.440901 52.898115,-2.440841 52.898123,-2.440774 52.898148,-2.440748 52.898155,-2.440667 52.898173,-2.440526 52.898200,-2.440464 52.898219,-2.440444 52.898226,-2.440371 52.898260,-2.440333 52.898284,-2.440319 52.898296,-2.440314 52.898304,-2.440314 52.898314,-2.440487 52.898373,-2.440621 52.898421,-2.441042 52.898578,-2.441110 52.898606,-2.441125 52.898614,-2.441157 52.898639,-2.441160 52.898648,-2.441161 52.898659,-2.441159 52.898736,-2.441165 52.898753,-2.441172 52.898761,-2.441189 52.898772,-2.441253 52.898793,-2.441367 52.898821,-2.441457 52.898838,-2.441668 52.898873,-2.441690 52.898853,-2.441723 52.898828,-2.441786 52.898795,-2.441859 52.898751,-2.441956 52.898705,-2.442040 52.898659,-2.442185 52.898552,-2.442238 52.898511,-2.442359 52.898423)))
point
POINT (-2.441396 52.89841)
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