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

2011

reference
52-tree-1
name
2011
tree-preservation-order

undefined

52-tpo-1
uprn
address-text
point
POINT (-1.021460 50.896967)
geometry
MULTIPOLYGON (((-1.021403 50.896961,-1.021406 50.896972,-1.021413 50.896982,-1.021426 50.896990,-1.021442 50.896995,-1.021459 50.896997,-1.021477 50.896995,-1.021493 50.896991,-1.021505 50.896983,-1.021514 50.896973,-1.021517 50.896962,-1.021514 50.896950,-1.021506 50.896940,-1.021494 50.896932,-1.021478 50.896927,-1.021461 50.896925,-1.021443 50.896927,-1.021427 50.896932,-1.021414 50.896940,-1.021406 50.896950,-1.021403 50.896961)))
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