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

1587

reference
219-tree-1
name
1587
tree-preservation-order

undefined

219-tpo-1
uprn
address-text
point
POINT (-1.041141 50.897546)
geometry
MULTIPOLYGON (((-1.041070 50.897538,-1.041073 50.897552,-1.041083 50.897565,-1.041098 50.897575,-1.041118 50.897581,-1.041140 50.897584,-1.041162 50.897582,-1.041182 50.897575,-1.041198 50.897566,-1.041208 50.897553,-1.041212 50.897539,-1.041209 50.897525,-1.041199 50.897513,-1.041184 50.897503,-1.041164 50.897496,-1.041142 50.897494,-1.041120 50.897496,-1.041100 50.897502,-1.041084 50.897512,-1.041074 50.897524,-1.041070 50.897538)))
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