Tree

There is a problem

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

0955

reference: 704-tree-1
name: 0955
tree-preservation-order: undefined
704-tpo-1
uprn
address-text
point: POINT (-1.013066 50.867460)
geometry: MULTIPOLYGON (((-1.013023 50.867455,-1.013025 50.867464,-1.013031 50.867471,-1.013040 50.867477,-1.013052 50.867481,-1.013065 50.867483,-1.013079 50.867482,-1.013091 50.867478,-1.013100 50.867472,-1.013106 50.867464,-1.013109 50.867456,-1.013107 50.867448,-1.013101 50.867440,-1.013091 50.867434,-1.013080 50.867430,-1.013066 50.867429,-1.013053 50.867430,-1.013041 50.867434,-1.013032 50.867440,-1.013026 50.867447,-1.013023 50.867455)))
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