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

1662

reference
466-tree-1
name
1662
tree-preservation-order

undefined

466-tpo-1
uprn
address-text
point
POINT (-1.023889 50.882813)
geometry
MULTIPOLYGON (((-1.023747 50.882798,-1.023753 50.882825,-1.023773 50.882851,-1.023804 50.882871,-1.023843 50.882884,-1.023887 50.882889,-1.023931 50.882885,-1.023971 50.882872,-1.024003 50.882853,-1.024023 50.882828,-1.024031 50.882800,-1.024025 50.882772,-1.024005 50.882747,-1.023974 50.882727,-1.023935 50.882714,-1.023891 50.882709,-1.023847 50.882713,-1.023807 50.882725,-1.023775 50.882745,-1.023754 50.882770,-1.023747 50.882798)))
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