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

0955

reference
331-tree-1
name
0955
tree-preservation-order

undefined

331-tpo-1
uprn
address-text
point
POINT (-1.016858 50.866809)
geometry
MULTIPOLYGON (((-1.016787 50.866801,-1.016790 50.866815,-1.016800 50.866828,-1.016816 50.866838,-1.016835 50.866844,-1.016857 50.866847,-1.016879 50.866845,-1.016899 50.866838,-1.016915 50.866829,-1.016926 50.866816,-1.016929 50.866802,-1.016926 50.866788,-1.016916 50.866776,-1.016901 50.866766,-1.016881 50.866759,-1.016859 50.866757,-1.016837 50.866759,-1.016817 50.866765,-1.016801 50.866775,-1.016791 50.866787,-1.016787 50.866801)))
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