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

1825

reference
399-tree-1
name
1825
tree-preservation-order

undefined

399-tpo-1
uprn
address-text
point
POINT (-1.017702 50.894523)
geometry
MULTIPOLYGON (((-1.017532 50.894505,-1.017540 50.894539,-1.017563 50.894569,-1.017601 50.894593,-1.017648 50.894609,-1.017701 50.894615,-1.017753 50.894610,-1.017801 50.894595,-1.017840 50.894571,-1.017864 50.894541,-1.017873 50.894508,-1.017866 50.894475,-1.017842 50.894444,-1.017805 50.894420,-1.017758 50.894404,-1.017705 50.894399,-1.017652 50.894404,-1.017604 50.894419,-1.017566 50.894442,-1.017541 50.894472,-1.017532 50.894505)))
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