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

undefined

72-tpo-1
uprn
address-text
point
POINT (-0.975466 50.849180)
geometry
MULTIPOLYGON (((-0.975409 50.849174,-0.975412 50.849185,-0.975420 50.849195,-0.975432 50.849203,-0.975448 50.849209,-0.975465 50.849210,-0.975483 50.849209,-0.975499 50.849204,-0.975512 50.849196,-0.975520 50.849186,-0.975523 50.849175,-0.975520 50.849164,-0.975512 50.849154,-0.975500 50.849146,-0.975484 50.849140,-0.975467 50.849139,-0.975449 50.849140,-0.975433 50.849145,-0.975421 50.849153,-0.975412 50.849163,-0.975409 50.849174)))
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