Tree

There is a problem

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

1471

reference: 383-tree-1
name: 1471
tree-preservation-order: undefined
383-tpo-1
uprn
address-text
point: POINT (-1.026698 50.884445)
geometry: MULTIPOLYGON (((-1.026612 50.884436,-1.026616 50.884453,-1.026628 50.884468,-1.026647 50.884480,-1.026670 50.884488,-1.026697 50.884491,-1.026723 50.884488,-1.026747 50.884481,-1.026766 50.884469,-1.026779 50.884454,-1.026783 50.884438,-1.026779 50.884421,-1.026767 50.884406,-1.026749 50.884394,-1.026725 50.884386,-1.026699 50.884383,-1.026672 50.884385,-1.026649 50.884393,-1.026629 50.884405,-1.026617 50.884420,-1.026612 50.884436)))
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