Tree

There is a problem

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

1451

reference: 431-tree-1
name: 1451
tree-preservation-order: undefined
431-tpo-1
uprn
address-text
point: POINT (-1.040680 50.897601)
geometry: MULTIPOLYGON (((-1.040652 50.897598,-1.040653 50.897604,-1.040657 50.897609,-1.040671 50.897616,-1.040680 50.897617,-1.040689 50.897616,-1.040697 50.897613,-1.040703 50.897609,-1.040709 50.897599,-1.040708 50.897593,-1.040704 50.897588,-1.040697 50.897584,-1.040681 50.897581,-1.040664 50.897584,-1.040658 50.897588,-1.040652 50.897598)))
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