Tree

There is a problem

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

0874

reference: 264-tree-1
name: 0874
tree-preservation-order: undefined
264-tpo-1
uprn
address-text
point: POINT (-0.936865 50.859382)
geometry: MULTIPOLYGON (((-0.936808 50.859376,-0.936811 50.859387,-0.936819 50.859397,-0.936831 50.859405,-0.936847 50.859410,-0.936864 50.859412,-0.936882 50.859411,-0.936898 50.859406,-0.936911 50.859398,-0.936919 50.859388,-0.936922 50.859377,-0.936920 50.859366,-0.936912 50.859355,-0.936899 50.859347,-0.936884 50.859342,-0.936866 50.859340,-0.936849 50.859342,-0.936833 50.859347,-0.936820 50.859355,-0.936811 50.859365,-0.936808 50.859376)))
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