Tree

There is a problem

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

1577

reference: 351-tree-1
name: 1577
tree-preservation-order: undefined
351-tpo-1
uprn
address-text
point: POINT (-1.046458 50.893212)
geometry: MULTIPOLYGON (((-1.046359 50.893202,-1.046363 50.893221,-1.046377 50.893239,-1.046399 50.893253,-1.046426 50.893262,-1.046457 50.893266,-1.046488 50.893263,-1.046516 50.893254,-1.046538 50.893240,-1.046552 50.893223,-1.046558 50.893204,-1.046553 50.893184,-1.046539 50.893166,-1.046518 50.893152,-1.046490 50.893143,-1.046459 50.893140,-1.046429 50.893143,-1.046401 50.893151,-1.046378 50.893165,-1.046364 50.893183,-1.046359 50.893202)))
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