Tree

There is a problem

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

1499

reference: 716-tree-1
name: 1499
tree-preservation-order: undefined
716-tpo-1
uprn
address-text
point: POINT (-0.971249 50.866063)
geometry: MULTIPOLYGON (((-0.971207 50.866058,-0.971209 50.866066,-0.971215 50.866074,-0.971224 50.866080,-0.971236 50.866084,-0.971249 50.866085,-0.971262 50.866084,-0.971284 50.866075,-0.971290 50.866067,-0.971292 50.866059,-0.971290 50.866050,-0.971284 50.866043,-0.971275 50.866037,-0.971263 50.866033,-0.971250 50.866031,-0.971225 50.866036,-0.971215 50.866042,-0.971209 50.866050,-0.971207 50.866058)))
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