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

1710

reference
836-tree-1
name
1710
tree-preservation-order

undefined

836-tpo-1
uprn
address-text
point
POINT (-1.044059 50.855497)
geometry
MULTIPOLYGON (((-1.043988 50.855489,-1.043991 50.855503,-1.044001 50.855516,-1.044017 50.855526,-1.044036 50.855532,-1.044058 50.855535,-1.044080 50.855533,-1.044100 50.855527,-1.044116 50.855517,-1.044126 50.855504,-1.044130 50.855490,-1.044127 50.855477,-1.044117 50.855464,-1.044102 50.855454,-1.044082 50.855447,-1.044060 50.855445,-1.044038 50.855447,-1.044018 50.855453,-1.044002 50.855463,-1.043992 50.855475,-1.043988 50.855489)))
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