Tree

There is a problem

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

1558

reference: 254-tree-1
name: 1558
tree-preservation-order: undefined
254-tpo-1
uprn
address-text
point: POINT (-0.988115 50.874581)
geometry: MULTIPOLYGON (((-0.988073 50.874577,-0.988075 50.874585,-0.988081 50.874593,-0.988090 50.874599,-0.988102 50.874603,-0.988115 50.874604,-0.988128 50.874603,-0.988140 50.874599,-0.988150 50.874593,-0.988156 50.874586,-0.988158 50.874577,-0.988156 50.874569,-0.988150 50.874562,-0.988141 50.874555,-0.988116 50.874550,-0.988103 50.874551,-0.988091 50.874555,-0.988081 50.874561,-0.988075 50.874568,-0.988073 50.874577)))
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