Tree

There is a problem

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

1499

reference: 518-tree-1
name: 1499
tree-preservation-order: undefined
518-tpo-1
uprn
address-text
point: POINT (-0.971953 50.866642)
geometry: MULTIPOLYGON (((-0.971896 50.866636,-0.971899 50.866648,-0.971907 50.866658,-0.971919 50.866666,-0.971935 50.866671,-0.971952 50.866673,-0.971970 50.866671,-0.971986 50.866666,-0.971999 50.866658,-0.972007 50.866649,-0.972010 50.866637,-0.972007 50.866626,-0.971999 50.866616,-0.971987 50.866608,-0.971971 50.866603,-0.971954 50.866601,-0.971936 50.866603,-0.971920 50.866608,-0.971907 50.866615,-0.971899 50.866625,-0.971896 50.866636)))
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