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

1565

reference
334-tree-1
name
1565
tree-preservation-order

undefined

334-tpo-1
uprn
address-text
point
POINT (-1.028080 50.863866)
geometry
MULTIPOLYGON (((-1.028037 50.863861,-1.028039 50.863869,-1.028045 50.863877,-1.028054 50.863883,-1.028066 50.863887,-1.028079 50.863888,-1.028092 50.863887,-1.028114 50.863878,-1.028120 50.863870,-1.028122 50.863862,-1.028120 50.863853,-1.028114 50.863846,-1.028105 50.863840,-1.028093 50.863836,-1.028080 50.863834,-1.028055 50.863839,-1.028046 50.863845,-1.028039 50.863853,-1.028037 50.863861)))
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