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

1425

reference
938-tree-1
name
1425
tree-preservation-order

undefined

938-tpo-1
uprn
address-text
point
POINT (-1.028346 50.876958)
geometry
MULTIPOLYGON (((-1.028289 50.876952,-1.028292 50.876963,-1.028300 50.876973,-1.028312 50.876981,-1.028328 50.876986,-1.028345 50.876988,-1.028363 50.876986,-1.028379 50.876981,-1.028392 50.876974,-1.028400 50.876964,-1.028403 50.876953,-1.028400 50.876941,-1.028393 50.876931,-1.028380 50.876923,-1.028364 50.876918,-1.028347 50.876916,-1.028329 50.876918,-1.028313 50.876923,-1.028301 50.876931,-1.028292 50.876941,-1.028289 50.876952)))
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