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

2133

reference
67-tree-1
name
2133
tree-preservation-order

undefined

67-tpo-1
uprn
address-text
point
POINT (-0.945040 50.847716)
geometry
MULTIPOLYGON (((-0.944983 50.847710,-0.944985 50.847722,-0.944993 50.847732,-0.945006 50.847740,-0.945021 50.847745,-0.945039 50.847747,-0.945056 50.847745,-0.945072 50.847740,-0.945085 50.847732,-0.945093 50.847723,-0.945096 50.847711,-0.945094 50.847700,-0.945086 50.847690,-0.945074 50.847682,-0.945058 50.847677,-0.945040 50.847675,-0.945023 50.847677,-0.945007 50.847682,-0.944994 50.847689,-0.944986 50.847699,-0.944983 50.847710)))
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