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

1692

reference
270-tree-1
name
1692
tree-preservation-order

undefined

270-tpo-1
uprn
address-text
point
POINT (-0.978347 50.857012)
geometry
MULTIPOLYGON (((-0.978262 50.857003,-0.978266 50.857020,-0.978278 50.857035,-0.978296 50.857047,-0.978320 50.857055,-0.978346 50.857058,-0.978372 50.857055,-0.978396 50.857048,-0.978415 50.857036,-0.978428 50.857021,-0.978432 50.857005,-0.978429 50.856988,-0.978417 50.856973,-0.978398 50.856961,-0.978375 50.856953,-0.978348 50.856950,-0.978322 50.856952,-0.978298 50.856960,-0.978279 50.856972,-0.978267 50.856986,-0.978262 50.857003)))
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