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

0955

reference
325-tree-1
name
0955
tree-preservation-order

undefined

325-tpo-1
uprn
address-text
point
POINT (-1.018405 50.866628)
geometry
MULTIPOLYGON (((-1.018362 50.866623,-1.018364 50.866632,-1.018370 50.866639,-1.018379 50.866645,-1.018391 50.866649,-1.018404 50.866650,-1.018417 50.866649,-1.018429 50.866646,-1.018439 50.866640,-1.018445 50.866632,-1.018447 50.866624,-1.018445 50.866616,-1.018439 50.866608,-1.018430 50.866602,-1.018418 50.866598,-1.018405 50.866597,-1.018392 50.866598,-1.018380 50.866601,-1.018370 50.866607,-1.018364 50.866615,-1.018362 50.866623)))
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