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

1224

reference
742-tree-1
name
1224
tree-preservation-order

undefined

742-tpo-1
uprn
address-text
point
POINT (-1.007349 50.886041)
geometry
MULTIPOLYGON (((-1.007250 50.886030,-1.007254 50.886050,-1.007268 50.886067,-1.007290 50.886082,-1.007318 50.886091,-1.007348 50.886094,-1.007379 50.886091,-1.007407 50.886083,-1.007429 50.886069,-1.007444 50.886051,-1.007449 50.886032,-1.007445 50.886013,-1.007431 50.885995,-1.007409 50.885981,-1.007382 50.885972,-1.007351 50.885968,-1.007320 50.885971,-1.007292 50.885980,-1.007270 50.885993,-1.007255 50.886011,-1.007250 50.886030)))
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