Tree

There is a problem

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

1216

reference: 110-tree-1
name: 1216
tree-preservation-order: undefined
110-tpo-1
uprn
address-text
point: POINT (-1.011717 50.865418)
geometry: MULTIPOLYGON (((-1.011660 50.865412,-1.011663 50.865424,-1.011671 50.865434,-1.011683 50.865442,-1.011699 50.865447,-1.011716 50.865449,-1.011734 50.865447,-1.011750 50.865442,-1.011763 50.865434,-1.011771 50.865424,-1.011774 50.865413,-1.011771 50.865402,-1.011764 50.865392,-1.011751 50.865384,-1.011735 50.865379,-1.011718 50.865377,-1.011700 50.865379,-1.011684 50.865384,-1.011672 50.865391,-1.011663 50.865401,-1.011660 50.865412)))
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