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

0496

reference
139-tree-1
name
0496
tree-preservation-order

undefined

139-tpo-1
uprn
address-text
point
POINT (-1.003691 50.853146)
geometry
MULTIPOLYGON (((-1.003649 50.853141,-1.003651 50.853150,-1.003656 50.853157,-1.003666 50.853163,-1.003678 50.853167,-1.003691 50.853169,-1.003716 50.853164,-1.003725 50.853158,-1.003732 50.853150,-1.003734 50.853142,-1.003732 50.853134,-1.003726 50.853126,-1.003717 50.853120,-1.003705 50.853116,-1.003692 50.853115,-1.003679 50.853116,-1.003657 50.853125,-1.003651 50.853133,-1.003649 50.853141)))
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