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

1182

reference
316-tree-1
name
1182
tree-preservation-order

undefined

316-tpo-1
uprn
address-text
point
POINT (-1.028937 50.866324)
geometry
MULTIPOLYGON (((-1.028894 50.866319,-1.028896 50.866328,-1.028902 50.866335,-1.028911 50.866341,-1.028923 50.866345,-1.028936 50.866346,-1.028949 50.866345,-1.028961 50.866342,-1.028971 50.866336,-1.028977 50.866328,-1.028979 50.866320,-1.028977 50.866312,-1.028971 50.866304,-1.028962 50.866298,-1.028950 50.866294,-1.028937 50.866293,-1.028924 50.866294,-1.028912 50.866297,-1.028902 50.866303,-1.028896 50.866311,-1.028894 50.866319)))
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