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

1662

reference
469-tree-1
name
1662
tree-preservation-order

undefined

469-tpo-1
uprn
address-text
point
POINT (-1.023663 50.882687)
geometry
MULTIPOLYGON (((-1.023578 50.882678,-1.023582 50.882695,-1.023594 50.882710,-1.023612 50.882722,-1.023636 50.882730,-1.023662 50.882733,-1.023689 50.882731,-1.023712 50.882723,-1.023732 50.882711,-1.023744 50.882696,-1.023749 50.882680,-1.023745 50.882663,-1.023733 50.882648,-1.023714 50.882636,-1.023691 50.882628,-1.023664 50.882625,-1.023638 50.882628,-1.023614 50.882635,-1.023595 50.882647,-1.023582 50.882662,-1.023578 50.882678)))
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