Tree

There is a problem

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

1576

reference: 355-tree-1
name: 1576
tree-preservation-order: undefined
355-tpo-1
uprn
address-text
point: POINT (-1.047372 50.892595)
geometry: MULTIPOLYGON (((-1.047273 50.892584,-1.047277 50.892603,-1.047291 50.892621,-1.047313 50.892635,-1.047340 50.892644,-1.047371 50.892648,-1.047402 50.892645,-1.047430 50.892636,-1.047452 50.892622,-1.047466 50.892605,-1.047472 50.892586,-1.047467 50.892566,-1.047453 50.892548,-1.047432 50.892534,-1.047404 50.892525,-1.047373 50.892522,-1.047343 50.892525,-1.047315 50.892533,-1.047292 50.892547,-1.047278 50.892565,-1.047273 50.892584)))
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