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

reference: 2013/009.G1
name: Bristol Street
tree-preservation-order: undefined
2013/009
tree-preservation-zone-type: group
geometry: MULTIPOLYGON (((-1.639713 54.968534,-1.639668 54.968449,-1.639658 54.968434,-1.639649 54.968426,-1.639630 54.968420,-1.639618 54.968420,-1.639554 54.968427,-1.639522 54.968433,-1.639515 54.968438,-1.639511 54.968444,-1.639510 54.968451,-1.639533 54.968511,-1.639538 54.968539,-1.639541 54.968567,-1.639540 54.968590,-1.639534 54.968599,-1.639524 54.968607,-1.639509 54.968613,-1.639494 54.968617,-1.639477 54.968619,-1.639457 54.968619,-1.639414 54.968614,-1.639377 54.968612,-1.639366 54.968615,-1.639358 54.968618,-1.639351 54.968626,-1.639345 54.968638,-1.639346 54.968656,-1.639355 54.968674,-1.639361 54.968681,-1.639381 54.968694,-1.639402 54.968702,-1.639415 54.968705,-1.639444 54.968707,-1.639470 54.968706,-1.639768 54.968680,-1.639780 54.968674,-1.639782 54.968671,-1.639782 54.968666,-1.639752 54.968605,-1.639713 54.968534)))
point: POINT (-1.639586 54.968591)
notes: These data are update live via a feed to NCC's Tree Managament System, EzyTreev
entry-date: 2022-07-01
start-date: 2013-06-14
end-date

Your data is missing a tree-preservation-order.

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

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