Tree

There is a problem

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

1502

reference: 727-tree-1
name: 1502
tree-preservation-order: undefined
727-tpo-1
uprn
address-text
point: POINT (-0.988202 50.859830)
geometry: MULTIPOLYGON (((-0.988145 50.859824,-0.988147 50.859835,-0.988155 50.859845,-0.988168 50.859853,-0.988183 50.859858,-0.988201 50.859860,-0.988218 50.859859,-0.988234 50.859854,-0.988247 50.859846,-0.988255 50.859836,-0.988258 50.859825,-0.988256 50.859814,-0.988248 50.859804,-0.988236 50.859796,-0.988220 50.859790,-0.988202 50.859788,-0.988185 50.859790,-0.988169 50.859795,-0.988156 50.859803,-0.988148 50.859813,-0.988145 50.859824)))
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