Tree preservation zone

There is a problem

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

entity: 19206706

reference: 2001
name
tree-preservation-order: undefined
Former Glenlion 1-10 Lion Park Avenue Chessington
tree-preservation-zone-type: T
geometry: MULTIPOLYGON (((-0.286670 51.368850,-0.286664 51.368851,-0.286659 51.368855,-0.286659 51.368859,-0.286662 51.368862,-0.286667 51.368864,-0.286673 51.368864,-0.286680 51.368860,-0.286680 51.368855,-0.286677 51.368852,-0.286670 51.368850)))
point: POINT (-0.28667 51.368857)
notes
entry-date: 2018-12-10
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree preservation zone guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that covers this zone.

This diagram shows the relationship between the tree preservation order dataset and the tree preservation zone dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree preservation zone dataset.

How to improve Royal Borough of Kingston upon Thames’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