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

1274

reference
648-tree-1
name
1274
tree-preservation-order

undefined

648-tpo-1
uprn
address-text
point
POINT (-1.046915 50.863485)
geometry
MULTIPOLYGON (((-1.046873 50.863480,-1.046875 50.863489,-1.046880 50.863496,-1.046890 50.863502,-1.046902 50.863506,-1.046915 50.863508,-1.046928 50.863507,-1.046940 50.863503,-1.046949 50.863497,-1.046956 50.863489,-1.046958 50.863481,-1.046956 50.863473,-1.046950 50.863465,-1.046941 50.863459,-1.046929 50.863455,-1.046916 50.863454,-1.046903 50.863455,-1.046891 50.863459,-1.046881 50.863465,-1.046875 50.863472,-1.046873 50.863480)))
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