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

1216

reference
627-tree-1
name
1216
tree-preservation-order

undefined

627-tpo-1
uprn
address-text
point
POINT (-1.011826 50.866673)
geometry
MULTIPOLYGON (((-1.011755 50.866665,-1.011759 50.866679,-1.011768 50.866692,-1.011784 50.866702,-1.011804 50.866708,-1.011825 50.866711,-1.011847 50.866709,-1.011867 50.866702,-1.011883 50.866693,-1.011894 50.866680,-1.011897 50.866666,-1.011894 50.866652,-1.011884 50.866640,-1.011869 50.866630,-1.011849 50.866623,-1.011827 50.866621,-1.011805 50.866623,-1.011785 50.866629,-1.011769 50.866639,-1.011759 50.866651,-1.011755 50.866665)))
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