Tree

There is a problem

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

2022

reference: 143-tree-1
name: 2022
tree-preservation-order: undefined
143-tpo-1
uprn
address-text
point: POINT (-0.975866 50.823612)
geometry: MULTIPOLYGON (((-0.975809 50.823606,-0.975812 50.823617,-0.975820 50.823627,-0.975832 50.823635,-0.975848 50.823640,-0.975865 50.823642,-0.975883 50.823641,-0.975899 50.823636,-0.975911 50.823628,-0.975920 50.823618,-0.975923 50.823607,-0.975920 50.823596,-0.975912 50.823586,-0.975900 50.823577,-0.975884 50.823572,-0.975867 50.823570,-0.975849 50.823572,-0.975833 50.823577,-0.975821 50.823585,-0.975812 50.823595,-0.975809 50.823606)))
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