Tree

There is a problem

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

entity: 7002038483

reference: TPO7443
name
tree-preservation-order: undefined
Barrow Road Barton upon Humber
uprn
address-text
point: POINT (-0.431901 53.682116)
geometry: MULTIPOLYGON (((-0.431886 53.682116,-0.431888 53.682120,-0.431893 53.682124,-0.431901 53.682125,-0.431908 53.682124,-0.431914 53.682121,-0.431916 53.682116,-0.431914 53.682112,-0.431909 53.682108,-0.431901 53.682107,-0.431894 53.682108,-0.431888 53.682111,-0.431886 53.682116)))
notes
felled-date
entry-date: 2022-11-16
start-date: 2022-11-16
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 North Lincolnshire 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