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

1042

reference
768-tree-1
name
1042
tree-preservation-order

undefined

768-tpo-1
uprn
address-text
point
POINT (-1.043909 50.866199)
geometry
MULTIPOLYGON (((-1.043866 50.866194,-1.043868 50.866202,-1.043874 50.866210,-1.043884 50.866216,-1.043895 50.866220,-1.043909 50.866221,-1.043922 50.866220,-1.043934 50.866216,-1.043943 50.866211,-1.043949 50.866203,-1.043952 50.866195,-1.043950 50.866186,-1.043944 50.866179,-1.043935 50.866173,-1.043923 50.866169,-1.043910 50.866167,-1.043885 50.866172,-1.043875 50.866178,-1.043869 50.866186,-1.043866 50.866194)))
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