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

1952

reference
33-tree-1
name
1952
tree-preservation-order

undefined

33-tpo-1
uprn
address-text
point
POINT (-0.951155 50.850464)
geometry
MULTIPOLYGON (((-0.951098 50.850458,-0.951101 50.850469,-0.951108 50.850480,-0.951121 50.850488,-0.951137 50.850493,-0.951154 50.850495,-0.951172 50.850493,-0.951188 50.850488,-0.951200 50.850480,-0.951209 50.850470,-0.951212 50.850459,-0.951209 50.850448,-0.951201 50.850438,-0.951189 50.850430,-0.951173 50.850425,-0.951156 50.850423,-0.951138 50.850425,-0.951122 50.850429,-0.951109 50.850437,-0.951101 50.850447,-0.951098 50.850458)))
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