Tree

There is a problem

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

1809

reference: 271-tree-1
name: 1809
tree-preservation-order: undefined
271-tpo-1
uprn
address-text
point: POINT (-0.979303 50.858513)
geometry: MULTIPOLYGON (((-0.979204 50.858502,-0.979208 50.858522,-0.979222 50.858539,-0.979244 50.858554,-0.979271 50.858563,-0.979302 50.858566,-0.979333 50.858563,-0.979361 50.858555,-0.979383 50.858541,-0.979397 50.858523,-0.979403 50.858504,-0.979398 50.858485,-0.979385 50.858467,-0.979363 50.858453,-0.979335 50.858444,-0.979305 50.858440,-0.979274 50.858443,-0.979246 50.858452,-0.979224 50.858465,-0.979209 50.858483,-0.979204 50.858502)))
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