Tree

There is a problem

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

1131

reference: 745-tree-1
name: 1131
tree-preservation-order: undefined
745-tpo-1
uprn
address-text
point: POINT (-1.041238 50.865553)
geometry: MULTIPOLYGON (((-1.041210 50.865550,-1.041211 50.865555,-1.041215 50.865560,-1.041221 50.865564,-1.041229 50.865567,-1.041238 50.865568,-1.041246 50.865567,-1.041261 50.865561,-1.041265 50.865556,-1.041266 50.865550,-1.041265 50.865544,-1.041261 50.865539,-1.041255 50.865535,-1.041238 50.865532,-1.041222 50.865535,-1.041215 50.865539,-1.041211 50.865544,-1.041210 50.865550)))
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