Tree

There is a problem

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

1182

reference: 315-tree-1
name: 1182
tree-preservation-order: undefined
315-tpo-1
uprn
address-text
point: POINT (-1.028743 50.866308)
geometry: MULTIPOLYGON (((-1.028700 50.866304,-1.028702 50.866312,-1.028708 50.866320,-1.028717 50.866326,-1.028729 50.866330,-1.028742 50.866331,-1.028756 50.866330,-1.028768 50.866326,-1.028777 50.866320,-1.028783 50.866313,-1.028786 50.866304,-1.028784 50.866296,-1.028778 50.866288,-1.028768 50.866282,-1.028757 50.866278,-1.028744 50.866277,-1.028730 50.866278,-1.028718 50.866282,-1.028709 50.866288,-1.028703 50.866295,-1.028700 50.866304)))
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