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

1402

reference
386-tree-1
name
1402
tree-preservation-order

undefined

386-tpo-1
uprn
address-text
point
POINT (-1.028142 50.882442)
geometry
MULTIPOLYGON (((-1.028057 50.882433,-1.028061 50.882449,-1.028073 50.882464,-1.028092 50.882476,-1.028115 50.882484,-1.028142 50.882487,-1.028168 50.882485,-1.028192 50.882477,-1.028211 50.882465,-1.028223 50.882451,-1.028228 50.882434,-1.028224 50.882417,-1.028212 50.882402,-1.028194 50.882390,-1.028170 50.882382,-1.028144 50.882379,-1.028117 50.882382,-1.028093 50.882389,-1.028074 50.882401,-1.028062 50.882416,-1.028057 50.882433)))
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