Tree

There is a problem

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

1102

reference: 764-tree-1
name: 1102
tree-preservation-order: undefined
764-tpo-1
uprn
address-text
point: POINT (-1.010756 50.886650)
geometry: MULTIPOLYGON (((-1.010699 50.886644,-1.010702 50.886655,-1.010710 50.886665,-1.010722 50.886673,-1.010738 50.886678,-1.010756 50.886680,-1.010773 50.886679,-1.010789 50.886674,-1.010802 50.886666,-1.010810 50.886656,-1.010813 50.886645,-1.010811 50.886634,-1.010803 50.886623,-1.010790 50.886615,-1.010775 50.886610,-1.010757 50.886608,-1.010739 50.886610,-1.010724 50.886615,-1.010711 50.886623,-1.010702 50.886633,-1.010699 50.886644)))
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