Tree

There is a problem

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

1216

reference: 106-tree-1
name: 1216
tree-preservation-order: undefined
106-tpo-1
uprn
address-text
point: POINT (-1.012714 50.865562)
geometry: MULTIPOLYGON (((-1.012671 50.865558,-1.012673 50.865566,-1.012679 50.865574,-1.012688 50.865580,-1.012700 50.865584,-1.012713 50.865585,-1.012726 50.865584,-1.012738 50.865580,-1.012748 50.865574,-1.012754 50.865567,-1.012756 50.865558,-1.012754 50.865550,-1.012749 50.865542,-1.012739 50.865536,-1.012727 50.865532,-1.012714 50.865531,-1.012701 50.865532,-1.012689 50.865536,-1.012680 50.865542,-1.012673 50.865549,-1.012671 50.865558)))
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