Tree

There is a problem

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

2033

reference: 145-tree-1
name: 2033
tree-preservation-order: undefined
145-tpo-1
uprn
address-text
point: POINT (-0.968430 50.851877)
geometry: MULTIPOLYGON (((-0.968373 50.851871,-0.968375 50.851882,-0.968383 50.851892,-0.968396 50.851900,-0.968411 50.851905,-0.968429 50.851907,-0.968447 50.851905,-0.968462 50.851900,-0.968475 50.851893,-0.968484 50.851883,-0.968487 50.851872,-0.968484 50.851860,-0.968476 50.851850,-0.968464 50.851842,-0.968448 50.851837,-0.968431 50.851835,-0.968413 50.851837,-0.968397 50.851842,-0.968384 50.851850,-0.968376 50.851860,-0.968373 50.851871)))
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