Tree

There is a problem

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

1502

reference: 730-tree-1
name: 1502
tree-preservation-order: undefined
730-tpo-1
uprn
address-text
point: POINT (-0.988339 50.859675)
geometry: MULTIPOLYGON (((-0.988268 50.859667,-0.988271 50.859681,-0.988281 50.859694,-0.988297 50.859704,-0.988316 50.859710,-0.988338 50.859713,-0.988360 50.859711,-0.988380 50.859704,-0.988396 50.859695,-0.988407 50.859682,-0.988410 50.859668,-0.988407 50.859654,-0.988397 50.859642,-0.988382 50.859632,-0.988362 50.859625,-0.988340 50.859623,-0.988318 50.859625,-0.988298 50.859631,-0.988282 50.859641,-0.988272 50.859653,-0.988268 50.859667)))
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