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

1582

reference
338-tree-1
name
1582
tree-preservation-order

undefined

338-tpo-1
uprn
address-text
point
POINT (-1.044753 50.894322)
geometry
MULTIPOLYGON (((-1.044667 50.894313,-1.044671 50.894329,-1.044683 50.894345,-1.044702 50.894357,-1.044725 50.894364,-1.044752 50.894367,-1.044778 50.894365,-1.044802 50.894357,-1.044821 50.894346,-1.044833 50.894331,-1.044838 50.894314,-1.044834 50.894297,-1.044822 50.894282,-1.044804 50.894270,-1.044780 50.894262,-1.044754 50.894259,-1.044727 50.894262,-1.044703 50.894269,-1.044684 50.894281,-1.044672 50.894296,-1.044667 50.894313)))
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