Tree

There is a problem

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

1222

reference: 548-tree-1
name: 1222
tree-preservation-order: undefined
548-tpo-1
uprn
address-text
point: POINT (-1.014446 50.882499)
geometry: MULTIPOLYGON (((-1.014417 50.882496,-1.014418 50.882502,-1.014422 50.882507,-1.014429 50.882511,-1.014445 50.882514,-1.014454 50.882514,-1.014462 50.882511,-1.014468 50.882507,-1.014474 50.882497,-1.014473 50.882491,-1.014469 50.882486,-1.014455 50.882479,-1.014446 50.882478,-1.014437 50.882479,-1.014429 50.882482,-1.014423 50.882486,-1.014417 50.882496)))
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