Tree

There is a problem

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

1794

reference: 268-tree-1
name: 1794
tree-preservation-order: undefined
268-tpo-1
uprn
address-text
point: POINT (-0.936921 50.864087)
geometry: MULTIPOLYGON (((-0.936893 50.864084,-0.936894 50.864090,-0.936898 50.864095,-0.936904 50.864099,-0.936921 50.864102,-0.936929 50.864102,-0.936944 50.864095,-0.936948 50.864090,-0.936949 50.864085,-0.936948 50.864079,-0.936944 50.864074,-0.936930 50.864067,-0.936921 50.864066,-0.936913 50.864067,-0.936898 50.864074,-0.936894 50.864079,-0.936893 50.864084)))
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