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

1810

reference
915-tree-1
name
1810
tree-preservation-order

undefined

915-tpo-1
uprn
address-text
point
POINT (-1.042753 50.866645)
geometry
MULTIPOLYGON (((-1.042654 50.866635,-1.042658 50.866654,-1.042672 50.866672,-1.042694 50.866686,-1.042721 50.866695,-1.042752 50.866698,-1.042783 50.866696,-1.042811 50.866687,-1.042833 50.866673,-1.042847 50.866656,-1.042853 50.866636,-1.042848 50.866617,-1.042835 50.866599,-1.042813 50.866585,-1.042785 50.866576,-1.042755 50.866573,-1.042724 50.866575,-1.042696 50.866584,-1.042674 50.866598,-1.042659 50.866615,-1.042654 50.866635)))
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