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

1206

reference
816-tree-1
name
1206
tree-preservation-order

undefined

816-tpo-1
uprn
address-text
point
POINT (-1.008233 50.888937)
geometry
MULTIPOLYGON (((-1.008162 50.888930,-1.008165 50.888944,-1.008175 50.888956,-1.008190 50.888966,-1.008210 50.888973,-1.008232 50.888975,-1.008254 50.888973,-1.008274 50.888967,-1.008290 50.888957,-1.008300 50.888945,-1.008304 50.888931,-1.008301 50.888917,-1.008291 50.888904,-1.008275 50.888894,-1.008256 50.888888,-1.008234 50.888885,-1.008212 50.888887,-1.008192 50.888894,-1.008176 50.888903,-1.008165 50.888916,-1.008162 50.888930)))
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