Tree

There is a problem

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

1499

reference: 579-tree-1
name: 1499
tree-preservation-order: undefined
579-tpo-1
uprn
address-text
point: POINT (-0.971289 50.867092)
geometry: MULTIPOLYGON (((-0.971232 50.867086,-0.971234 50.867097,-0.971242 50.867107,-0.971255 50.867115,-0.971270 50.867120,-0.971288 50.867122,-0.971306 50.867120,-0.971321 50.867115,-0.971334 50.867108,-0.971343 50.867098,-0.971346 50.867087,-0.971343 50.867075,-0.971335 50.867065,-0.971323 50.867057,-0.971307 50.867052,-0.971290 50.867050,-0.971272 50.867052,-0.971256 50.867057,-0.971243 50.867065,-0.971235 50.867075,-0.971232 50.867086)))
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