Tree

There is a problem

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

1499

reference: 570-tree-1
name: 1499
tree-preservation-order: undefined
570-tpo-1
uprn
address-text
point: POINT (-0.972986 50.866470)
geometry: MULTIPOLYGON (((-0.972915 50.866462,-0.972919 50.866476,-0.972928 50.866489,-0.972944 50.866499,-0.972963 50.866506,-0.972985 50.866508,-0.973007 50.866506,-0.973027 50.866500,-0.973043 50.866490,-0.973054 50.866478,-0.973057 50.866464,-0.973054 50.866450,-0.973044 50.866437,-0.973029 50.866427,-0.973009 50.866420,-0.972987 50.866418,-0.972965 50.866420,-0.972945 50.866426,-0.972929 50.866436,-0.972919 50.866449,-0.972915 50.866462)))
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