Tree

There is a problem

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

1002

reference: 877-tree-1
name: 1002
tree-preservation-order: undefined
877-tpo-1
uprn
address-text
point: POINT (-1.040686 50.873467)
geometry: MULTIPOLYGON (((-1.040629 50.873461,-1.040632 50.873472,-1.040640 50.873482,-1.040652 50.873490,-1.040668 50.873495,-1.040686 50.873497,-1.040703 50.873495,-1.040719 50.873490,-1.040732 50.873483,-1.040740 50.873473,-1.040743 50.873462,-1.040741 50.873450,-1.040733 50.873440,-1.040720 50.873432,-1.040705 50.873427,-1.040687 50.873425,-1.040669 50.873427,-1.040653 50.873432,-1.040641 50.873440,-1.040632 50.873450,-1.040629 50.873461)))
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