Skip to main content
Check and provide your planning data

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

Back to dataset table
North Tyneside Council

Tree

There is a problem

  • 6 entries with tree-preservation-order field must match the reference field in the tree preservation order

The Crescent, Wallsend Tree Preservation Order 2005

reference
05/00158/TPO-T1
name
The Crescent, Wallsend Tree Preservation Order 2005
tree-preservation-order

undefined

05/00158/TPO
uprn
address-text
point
POINT (-1.535981 55.000542)
geometry
MULTIPOLYGON (((-1.535987 55.000572,-1.536000 55.000571,-1.536017 55.000565,-1.536032 55.000553,-1.536035 55.000546,-1.536035 55.000538,-1.536034 55.000534,-1.536026 55.000524,-1.536007 55.000514,-1.535988 55.000511,-1.535969 55.000511,-1.535946 55.000518,-1.535931 55.000530,-1.535927 55.000541,-1.535929 55.000549,-1.535933 55.000556,-1.535945 55.000565,-1.535962 55.000571,-1.535981 55.000573,-1.535987 55.000572)))
notes
felled-date
entry-date
2009-08-03
start-date
2005-09-30
end-date
2017-07-24

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve North Tyneside 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