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

2137

reference
73-tree-1
name
2137
tree-preservation-order

undefined

73-tpo-1
uprn
address-text
point
POINT (-0.975542 50.849197)
geometry
MULTIPOLYGON (((-0.975486 50.849191,-0.975488 50.849202,-0.975496 50.849213,-0.975508 50.849221,-0.975524 50.849226,-0.975542 50.849228,-0.975559 50.849226,-0.975575 50.849221,-0.975588 50.849213,-0.975596 50.849203,-0.975599 50.849192,-0.975597 50.849181,-0.975589 50.849171,-0.975576 50.849163,-0.975561 50.849158,-0.975543 50.849156,-0.975526 50.849157,-0.975510 50.849162,-0.975497 50.849170,-0.975489 50.849180,-0.975486 50.849191)))
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