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

1662

reference
565-tree-1
name
1662
tree-preservation-order

undefined

565-tpo-1
uprn
address-text
point
POINT (-1.024054 50.882289)
geometry
MULTIPOLYGON (((-1.023927 50.882276,-1.023933 50.882301,-1.023950 50.882324,-1.023978 50.882342,-1.024014 50.882353,-1.024053 50.882358,-1.024093 50.882354,-1.024129 50.882343,-1.024157 50.882325,-1.024176 50.882303,-1.024183 50.882278,-1.024177 50.882253,-1.024159 50.882230,-1.024131 50.882212,-1.024096 50.882200,-1.024056 50.882196,-1.024017 50.882200,-1.023981 50.882211,-1.023952 50.882228,-1.023934 50.882251,-1.023927 50.882276)))
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