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
599-tree-1
name
1274
tree-preservation-order

undefined

599-tpo-1
uprn
address-text
point
POINT (-1.046631 50.863322)
geometry
MULTIPOLYGON (((-1.046560 50.863314,-1.046563 50.863328,-1.046573 50.863341,-1.046588 50.863351,-1.046608 50.863357,-1.046630 50.863360,-1.046652 50.863358,-1.046672 50.863351,-1.046688 50.863342,-1.046698 50.863329,-1.046702 50.863315,-1.046699 50.863301,-1.046689 50.863289,-1.046673 50.863279,-1.046654 50.863272,-1.046632 50.863270,-1.046610 50.863272,-1.046590 50.863278,-1.046574 50.863288,-1.046564 50.863300,-1.046560 50.863314)))
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