Tree

There is a problem

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

0444

reference: 188-tree-1
name: 0444
tree-preservation-order: undefined
188-tpo-1
uprn
address-text
point: POINT (-0.940871 50.862380)
geometry: MULTIPOLYGON (((-0.940786 50.862371,-0.940790 50.862388,-0.940801 50.862403,-0.940820 50.862415,-0.940843 50.862423,-0.940870 50.862426,-0.940896 50.862423,-0.940920 50.862416,-0.940939 50.862404,-0.940952 50.862389,-0.940956 50.862372,-0.940952 50.862356,-0.940941 50.862341,-0.940922 50.862328,-0.940898 50.862321,-0.940872 50.862318,-0.940846 50.862320,-0.940822 50.862328,-0.940803 50.862339,-0.940790 50.862354,-0.940786 50.862371)))
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