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

1151

reference
129-tree-1
name
1151
tree-preservation-order

undefined

129-tpo-1
uprn
address-text
point
POINT (-1.032899 50.866696)
geometry
MULTIPOLYGON (((-1.032772 50.866682,-1.032777 50.866707,-1.032795 50.866730,-1.032823 50.866748,-1.032858 50.866760,-1.032898 50.866764,-1.032937 50.866761,-1.032973 50.866749,-1.033002 50.866732,-1.033021 50.866709,-1.033027 50.866684,-1.033022 50.866659,-1.033004 50.866637,-1.032976 50.866619,-1.032941 50.866607,-1.032901 50.866602,-1.032862 50.866606,-1.032826 50.866617,-1.032797 50.866635,-1.032778 50.866657,-1.032772 50.866682)))
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