Tree

There is a problem

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

1537

reference: 919-tree-1
name: 1537
tree-preservation-order: undefined
919-tpo-1
uprn
address-text
point: POINT (-1.025496 50.868444)
geometry: MULTIPOLYGON (((-1.025383 50.868432,-1.025388 50.868455,-1.025403 50.868475,-1.025428 50.868491,-1.025460 50.868501,-1.025495 50.868505,-1.025530 50.868502,-1.025562 50.868492,-1.025587 50.868476,-1.025604 50.868456,-1.025610 50.868434,-1.025605 50.868412,-1.025589 50.868392,-1.025564 50.868376,-1.025533 50.868365,-1.025498 50.868361,-1.025463 50.868365,-1.025431 50.868375,-1.025405 50.868390,-1.025389 50.868410,-1.025383 50.868432)))
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