Tree

There is a problem

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

1442

reference: 440-tree-1
name: 1442
tree-preservation-order: undefined
440-tpo-1
uprn
address-text
point: POINT (-1.040449 50.897867)
geometry: MULTIPOLYGON (((-1.040420 50.897864,-1.040426 50.897874,-1.040432 50.897878,-1.040440 50.897881,-1.040449 50.897882,-1.040465 50.897879,-1.040472 50.897875,-1.040476 50.897870,-1.040477 50.897864,-1.040476 50.897859,-1.040466 50.897849,-1.040449 50.897846,-1.040432 50.897849,-1.040426 50.897853,-1.040422 50.897858,-1.040420 50.897864)))
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