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

1628

reference
820-tree-1
name
1628
tree-preservation-order

undefined

820-tpo-1
uprn
address-text
point
POINT (-1.036317 50.875498)
geometry
MULTIPOLYGON (((-1.036218 50.875487,-1.036222 50.875507,-1.036236 50.875524,-1.036258 50.875538,-1.036286 50.875548,-1.036316 50.875551,-1.036347 50.875548,-1.036375 50.875539,-1.036397 50.875526,-1.036412 50.875508,-1.036417 50.875489,-1.036413 50.875469,-1.036399 50.875452,-1.036377 50.875438,-1.036349 50.875428,-1.036319 50.875425,-1.036288 50.875428,-1.036260 50.875437,-1.036238 50.875450,-1.036223 50.875468,-1.036218 50.875487)))
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