Tree

There is a problem

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

1381

reference: 136-tree-1
name: 1381
tree-preservation-order: undefined
136-tpo-1
uprn
address-text
point: POINT (-1.032124 50.865222)
geometry: MULTIPOLYGON (((-1.032025 50.865211,-1.032029 50.865231,-1.032043 50.865248,-1.032065 50.865262,-1.032092 50.865272,-1.032123 50.865275,-1.032154 50.865272,-1.032182 50.865263,-1.032204 50.865250,-1.032218 50.865232,-1.032224 50.865213,-1.032219 50.865193,-1.032205 50.865176,-1.032184 50.865162,-1.032156 50.865152,-1.032126 50.865149,-1.032095 50.865152,-1.032067 50.865161,-1.032045 50.865174,-1.032030 50.865192,-1.032025 50.865211)))
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