Tree

There is a problem

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

1442

reference: 438-tree-1
name: 1442
tree-preservation-order: undefined
438-tpo-1
uprn
address-text
point: POINT (-1.040615 50.897621)
geometry: MULTIPOLYGON (((-1.040587 50.897618,-1.040588 50.897624,-1.040592 50.897629,-1.040598 50.897633,-1.040615 50.897636,-1.040624 50.897636,-1.040632 50.897633,-1.040638 50.897629,-1.040644 50.897619,-1.040639 50.897608,-1.040624 50.897601,-1.040616 50.897600,-1.040607 50.897601,-1.040599 50.897604,-1.040588 50.897613,-1.040587 50.897618)))
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