Tree

There is a problem

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

0625

reference: 902-tree-1
name: 0625
tree-preservation-order: undefined
902-tpo-1
uprn
address-text
point: POINT (-0.966847 50.861437)
geometry: MULTIPOLYGON (((-0.966762 50.861428,-0.966766 50.861445,-0.966777 50.861460,-0.966796 50.861472,-0.966820 50.861480,-0.966846 50.861483,-0.966872 50.861480,-0.966896 50.861473,-0.966915 50.861461,-0.966928 50.861446,-0.966932 50.861429,-0.966929 50.861413,-0.966917 50.861398,-0.966898 50.861385,-0.966875 50.861378,-0.966848 50.861375,-0.966822 50.861377,-0.966798 50.861385,-0.966779 50.861396,-0.966766 50.861411,-0.966762 50.861428)))
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