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

1357

reference
305-tree-1
name
1357
tree-preservation-order

undefined

305-tpo-1
uprn
address-text
point
POINT (-1.026903 50.893652)
geometry
MULTIPOLYGON (((-1.026832 50.893645,-1.026835 50.893659,-1.026845 50.893671,-1.026860 50.893681,-1.026880 50.893688,-1.026902 50.893690,-1.026924 50.893688,-1.026944 50.893682,-1.026960 50.893672,-1.026970 50.893660,-1.026974 50.893646,-1.026971 50.893632,-1.026961 50.893619,-1.026945 50.893609,-1.026926 50.893603,-1.026904 50.893600,-1.026882 50.893602,-1.026862 50.893609,-1.026846 50.893618,-1.026835 50.893631,-1.026832 50.893645)))
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