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

1402

reference
385-tree-1
name
1402
tree-preservation-order

undefined

385-tpo-1
uprn
address-text
point
POINT (-1.028872 50.882408)
geometry
MULTIPOLYGON (((-1.028801 50.882400,-1.028804 50.882414,-1.028814 50.882427,-1.028829 50.882437,-1.028849 50.882443,-1.028871 50.882446,-1.028893 50.882444,-1.028913 50.882437,-1.028929 50.882428,-1.028939 50.882415,-1.028943 50.882401,-1.028940 50.882387,-1.028930 50.882375,-1.028914 50.882365,-1.028895 50.882358,-1.028873 50.882356,-1.028851 50.882358,-1.028831 50.882364,-1.028815 50.882374,-1.028805 50.882386,-1.028801 50.882400)))
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