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

0929

reference
555-tree-1
name
0929
tree-preservation-order

undefined

555-tpo-1
uprn
address-text
point
POINT (-1.029502 50.882054)
geometry
MULTIPOLYGON (((-1.029445 50.882048,-1.029447 50.882059,-1.029455 50.882069,-1.029468 50.882077,-1.029484 50.882082,-1.029501 50.882084,-1.029519 50.882083,-1.029535 50.882078,-1.029547 50.882070,-1.029556 50.882060,-1.029559 50.882049,-1.029556 50.882038,-1.029548 50.882028,-1.029536 50.882020,-1.029520 50.882014,-1.029503 50.882012,-1.029485 50.882014,-1.029469 50.882019,-1.029456 50.882027,-1.029448 50.882037,-1.029445 50.882048)))
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