Tree

There is a problem

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

1222

reference: 547-tree-1
name: 1222
tree-preservation-order: undefined
547-tpo-1
uprn
address-text
point: POINT (-1.014379 50.882491)
geometry: MULTIPOLYGON (((-1.014351 50.882488,-1.014352 50.882494,-1.014356 50.882499,-1.014370 50.882506,-1.014379 50.882507,-1.014387 50.882506,-1.014402 50.882499,-1.014406 50.882494,-1.014407 50.882489,-1.014406 50.882483,-1.014402 50.882478,-1.014396 50.882474,-1.014379 50.882471,-1.014363 50.882474,-1.014356 50.882478,-1.014352 50.882483,-1.014351 50.882488)))
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