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

1662

reference
566-tree-1
name
1662
tree-preservation-order

undefined

566-tpo-1
uprn
address-text
point
POINT (-1.024024 50.882270)
geometry
MULTIPOLYGON (((-1.023939 50.882261,-1.023943 50.882277,-1.023955 50.882292,-1.023973 50.882305,-1.023997 50.882312,-1.024023 50.882315,-1.024050 50.882313,-1.024074 50.882305,-1.024093 50.882294,-1.024105 50.882279,-1.024110 50.882262,-1.024106 50.882245,-1.024094 50.882230,-1.024076 50.882218,-1.024052 50.882210,-1.024026 50.882207,-1.023999 50.882210,-1.023975 50.882217,-1.023956 50.882229,-1.023944 50.882244,-1.023939 50.882261)))
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