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

1102

reference
762-tree-1
name
1102
tree-preservation-order

undefined

762-tpo-1
uprn
address-text
point
POINT (-1.010634 50.886860)
geometry
MULTIPOLYGON (((-1.010563 50.886852,-1.010566 50.886866,-1.010576 50.886879,-1.010591 50.886889,-1.010611 50.886895,-1.010633 50.886898,-1.010655 50.886896,-1.010675 50.886889,-1.010691 50.886880,-1.010701 50.886867,-1.010705 50.886853,-1.010702 50.886839,-1.010692 50.886827,-1.010676 50.886817,-1.010657 50.886810,-1.010635 50.886808,-1.010613 50.886810,-1.010593 50.886816,-1.010577 50.886826,-1.010567 50.886838,-1.010563 50.886852)))
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