Tree

There is a problem

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

0155

reference: 720-tree-1
name: 0155
tree-preservation-order: undefined
720-tpo-1
uprn
address-text
point: POINT (-0.989703 50.867827)
geometry: MULTIPOLYGON (((-0.989661 50.867823,-0.989663 50.867831,-0.989668 50.867838,-0.989678 50.867845,-0.989703 50.867850,-0.989716 50.867849,-0.989728 50.867845,-0.989737 50.867839,-0.989744 50.867832,-0.989746 50.867823,-0.989744 50.867815,-0.989738 50.867807,-0.989729 50.867801,-0.989717 50.867797,-0.989704 50.867796,-0.989691 50.867797,-0.989679 50.867801,-0.989669 50.867807,-0.989663 50.867814,-0.989661 50.867823)))
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