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
74-tree-1
name
2137
tree-preservation-order

undefined

74-tpo-1
uprn
address-text
point
POINT (-0.975653 50.849214)
geometry
MULTIPOLYGON (((-0.975596 50.849208,-0.975599 50.849219,-0.975607 50.849229,-0.975619 50.849237,-0.975635 50.849243,-0.975652 50.849244,-0.975670 50.849243,-0.975686 50.849238,-0.975699 50.849230,-0.975707 50.849220,-0.975710 50.849209,-0.975708 50.849198,-0.975700 50.849188,-0.975687 50.849180,-0.975672 50.849174,-0.975654 50.849173,-0.975636 50.849174,-0.975620 50.849179,-0.975608 50.849187,-0.975599 50.849197,-0.975596 50.849208)))
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