Tree

There is a problem

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

1082

reference: 860-tree-1
name: 1082
tree-preservation-order: undefined
860-tpo-1
uprn
address-text
point: POINT (-0.962950 50.865884)
geometry: MULTIPOLYGON (((-0.962879 50.865877,-0.962882 50.865891,-0.962892 50.865903,-0.962907 50.865913,-0.962927 50.865920,-0.962949 50.865922,-0.962971 50.865920,-0.962991 50.865914,-0.963007 50.865904,-0.963017 50.865892,-0.963021 50.865878,-0.963018 50.865864,-0.963008 50.865852,-0.962992 50.865841,-0.962973 50.865835,-0.962951 50.865832,-0.962929 50.865834,-0.962909 50.865841,-0.962893 50.865851,-0.962882 50.865863,-0.962879 50.865877)))
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