Tree

There is a problem

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

1499

reference: 894-tree-1
name: 1499
tree-preservation-order: undefined
894-tpo-1
uprn
address-text
point: POINT (-0.971065 50.866193)
geometry: MULTIPOLYGON (((-0.971009 50.866187,-0.971011 50.866198,-0.971019 50.866208,-0.971031 50.866216,-0.971047 50.866221,-0.971065 50.866223,-0.971082 50.866221,-0.971098 50.866217,-0.971111 50.866209,-0.971119 50.866199,-0.971122 50.866188,-0.971120 50.866176,-0.971112 50.866166,-0.971100 50.866158,-0.971084 50.866153,-0.971066 50.866151,-0.971049 50.866153,-0.971033 50.866158,-0.971020 50.866166,-0.971012 50.866176,-0.971009 50.866187)))
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