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
East Hampshire District Council

Tree

There is a problem

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

1102

reference
766-tree-1
name
1102
tree-preservation-order

undefined

766-tpo-1
uprn
address-text
point
POINT (-1.010846 50.886484)
geometry
MULTIPOLYGON (((-1.010775 50.886477,-1.010779 50.886491,-1.010789 50.886503,-1.010804 50.886513,-1.010824 50.886520,-1.010846 50.886522,-1.010868 50.886520,-1.010888 50.886514,-1.010904 50.886504,-1.010914 50.886492,-1.010918 50.886478,-1.010914 50.886464,-1.010905 50.886451,-1.010889 50.886441,-1.010869 50.886435,-1.010848 50.886432,-1.010826 50.886434,-1.010806 50.886440,-1.010790 50.886450,-1.010779 50.886463,-1.010775 50.886477)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

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 East Hampshire District 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