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

1216

reference
634-tree-1
name
1216
tree-preservation-order

undefined

634-tpo-1
uprn
address-text
point
POINT (-1.011925 50.866740)
geometry
MULTIPOLYGON (((-1.011854 50.866733,-1.011857 50.866747,-1.011867 50.866759,-1.011883 50.866769,-1.011902 50.866776,-1.011924 50.866778,-1.011946 50.866776,-1.011966 50.866770,-1.011982 50.866760,-1.011992 50.866748,-1.011996 50.866734,-1.011993 50.866720,-1.011983 50.866707,-1.011968 50.866697,-1.011948 50.866691,-1.011926 50.866688,-1.011904 50.866690,-1.011884 50.866697,-1.011868 50.866707,-1.011858 50.866719,-1.011854 50.866733)))
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