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

1588

reference
290-tree-1
name
1588
tree-preservation-order

undefined

290-tpo-1
uprn
address-text
point
POINT (-1.040638 50.897657)
geometry
MULTIPOLYGON (((-1.040595 50.897652,-1.040597 50.897661,-1.040603 50.897668,-1.040613 50.897674,-1.040624 50.897678,-1.040638 50.897680,-1.040651 50.897679,-1.040663 50.897675,-1.040672 50.897669,-1.040678 50.897661,-1.040681 50.897653,-1.040679 50.897645,-1.040673 50.897637,-1.040664 50.897631,-1.040652 50.897627,-1.040639 50.897626,-1.040625 50.897627,-1.040613 50.897631,-1.040604 50.897637,-1.040598 50.897644,-1.040595 50.897652)))
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