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

1056

reference
782-tree-1
name
1056
tree-preservation-order

undefined

782-tpo-1
uprn
address-text
point
POINT (-1.035278 50.862758)
geometry
MULTIPOLYGON (((-1.035250 50.862755,-1.035251 50.862760,-1.035255 50.862765,-1.035261 50.862769,-1.035269 50.862772,-1.035278 50.862773,-1.035287 50.862772,-1.035301 50.862766,-1.035305 50.862761,-1.035307 50.862755,-1.035306 50.862749,-1.035302 50.862744,-1.035295 50.862740,-1.035279 50.862737,-1.035262 50.862740,-1.035251 50.862749,-1.035250 50.862755)))
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