Tree

There is a problem

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

1033

reference: 178-tree-1
name: 1033
tree-preservation-order: undefined
178-tpo-1
uprn
address-text
point: POINT (-0.938117 50.859147)
geometry: MULTIPOLYGON (((-0.938061 50.859141,-0.938063 50.859152,-0.938071 50.859162,-0.938083 50.859170,-0.938099 50.859175,-0.938117 50.859177,-0.938134 50.859176,-0.938150 50.859171,-0.938163 50.859163,-0.938171 50.859153,-0.938174 50.859142,-0.938172 50.859131,-0.938164 50.859120,-0.938151 50.859112,-0.938136 50.859107,-0.938118 50.859105,-0.938101 50.859107,-0.938085 50.859112,-0.938072 50.859120,-0.938064 50.859130,-0.938061 50.859141)))
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