Tree

There is a problem

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

1622

reference: 968-tree-1
name: 1622
tree-preservation-order: undefined
968-tpo-1
uprn
address-text
point: POINT (-0.994412 50.857493)
geometry: MULTIPOLYGON (((-0.994369 50.857489,-0.994371 50.857497,-0.994377 50.857505,-0.994386 50.857511,-0.994398 50.857515,-0.994411 50.857516,-0.994425 50.857515,-0.994437 50.857511,-0.994446 50.857505,-0.994452 50.857498,-0.994455 50.857489,-0.994453 50.857481,-0.994447 50.857474,-0.994437 50.857467,-0.994413 50.857462,-0.994399 50.857463,-0.994387 50.857467,-0.994378 50.857473,-0.994372 50.857480,-0.994369 50.857489)))
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