Tree

There is a problem

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

1812

reference: 252-tree-1
name: 1812
tree-preservation-order: undefined
252-tpo-1
uprn
address-text
point: POINT (-0.995421 50.851887)
geometry: MULTIPOLYGON (((-0.995350 50.851880,-0.995353 50.851894,-0.995363 50.851906,-0.995379 50.851916,-0.995398 50.851923,-0.995420 50.851925,-0.995442 50.851923,-0.995462 50.851917,-0.995478 50.851907,-0.995488 50.851895,-0.995492 50.851881,-0.995489 50.851867,-0.995479 50.851855,-0.995464 50.851844,-0.995444 50.851838,-0.995422 50.851836,-0.995400 50.851838,-0.995380 50.851844,-0.995364 50.851854,-0.995354 50.851866,-0.995350 50.851880)))
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