Tree

There is a problem

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

1393

reference: 616-tree-1
name: 1393
tree-preservation-order: undefined
616-tpo-1
uprn
address-text
point: POINT (-1.023508 50.881050)
geometry: MULTIPOLYGON (((-1.023394 50.881038,-1.023399 50.881060,-1.023415 50.881080,-1.023440 50.881097,-1.023471 50.881107,-1.023506 50.881111,-1.023541 50.881108,-1.023573 50.881098,-1.023599 50.881082,-1.023615 50.881062,-1.023621 50.881040,-1.023616 50.881018,-1.023601 50.880997,-1.023576 50.880981,-1.023544 50.880971,-1.023509 50.880967,-1.023474 50.880970,-1.023442 50.880980,-1.023417 50.880996,-1.023400 50.881016,-1.023394 50.881038)))
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