Tree

There is a problem

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

1499

reference: 712-tree-1
name: 1499
tree-preservation-order: undefined
712-tpo-1
uprn
address-text
point: POINT (-0.971344 50.866626)
geometry: MULTIPOLYGON (((-0.971273 50.866618,-0.971277 50.866632,-0.971286 50.866645,-0.971302 50.866655,-0.971322 50.866662,-0.971343 50.866664,-0.971365 50.866662,-0.971385 50.866656,-0.971401 50.866646,-0.971412 50.866633,-0.971416 50.866620,-0.971412 50.866606,-0.971403 50.866593,-0.971387 50.866583,-0.971367 50.866576,-0.971345 50.866574,-0.971323 50.866576,-0.971304 50.866582,-0.971288 50.866592,-0.971277 50.866604,-0.971273 50.866618)))
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