Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1372

reference: 974-tree-1
name: 1372
tree-preservation-order: undefined
974-tpo-1
uprn
address-text
point: POINT (-1.004605 50.853244)
geometry: MULTIPOLYGON (((-1.004548 50.853238,-1.004551 50.853249,-1.004558 50.853259,-1.004571 50.853267,-1.004587 50.853272,-1.004604 50.853274,-1.004622 50.853273,-1.004638 50.853268,-1.004650 50.853260,-1.004659 50.853250,-1.004662 50.853239,-1.004659 50.853228,-1.004651 50.853218,-1.004639 50.853210,-1.004623 50.853204,-1.004606 50.853202,-1.004588 50.853204,-1.004572 50.853209,-1.004559 50.853217,-1.004551 50.853227,-1.004548 50.853238)))
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

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL