Tree

There is a problem

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

entity: 7002038301

reference: TPO2071
name
tree-preservation-order: undefined
Cliff Drive, Burton Stather 2000
uprn
address-text
point: POINT (-0.685602 53.653808)
geometry: MULTIPOLYGON (((-0.685587 53.653808,-0.685589 53.653812,-0.685594 53.653815,-0.685602 53.653817,-0.685610 53.653816,-0.685615 53.653812,-0.685617 53.653808,-0.685615 53.653803,-0.685610 53.653800,-0.685602 53.653799,-0.685595 53.653800,-0.685589 53.653803,-0.685587 53.653808)))
notes
felled-date
entry-date: 2000-11-21
start-date: 2000-10-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