Tree

There is a problem

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

1793

reference: 988-tree-1
name: 1793
tree-preservation-order: undefined
988-tpo-1
uprn
address-text
point: POINT (-0.974275 50.858291)
geometry: MULTIPOLYGON (((-0.974190 50.858282,-0.974194 50.858299,-0.974205 50.858314,-0.974224 50.858326,-0.974247 50.858334,-0.974274 50.858337,-0.974300 50.858334,-0.974324 50.858327,-0.974343 50.858315,-0.974356 50.858300,-0.974360 50.858284,-0.974356 50.858267,-0.974345 50.858252,-0.974326 50.858240,-0.974302 50.858232,-0.974276 50.858229,-0.974250 50.858231,-0.974226 50.858239,-0.974207 50.858251,-0.974194 50.858265,-0.974190 50.858282)))
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