Bristol City Council
Tree preservation zone
There is a problem
- 365 entries with tree-preservation-order field must match the reference field in the tree preservation order dataset
Stoke Lodge Playing Field Shirehampton Road Bristol
- reference
- LSN8QRDN0UN00
- name
- Stoke Lodge Playing Field Shirehampton Road Bristol
- tree-preservation-order
- 1192
- tree-preservation-zone-type
- group
- geometry
- MULTIPOLYGON (((-2.636918 51.487808,-2.636952 51.487811,-2.637034 51.487791,-2.637004 51.487759,-2.636919 51.487725,-2.636931 51.487705,-2.636907 51.487681,-2.636863 51.487659,-2.636807 51.487644,-2.636773 51.487646,-2.636768 51.487628,-2.636686 51.487607,-2.636683 51.487581,-2.636656 51.487560,-2.636627 51.487555,-2.636596 51.487561,-2.636572 51.487552,-2.636581 51.487522,-2.636549 51.487490,-2.636496 51.487477,-2.636409 51.487491,-2.636368 51.487461,-2.636341 51.487449,-2.636319 51.487449,-2.636319 51.487433,-2.636290 51.487406,-2.636253 51.487388,-2.636241 51.487392,-2.636237 51.487416,-2.636222 51.487417,-2.636146 51.487351,-2.636122 51.487345,-2.636014 51.487356,-2.636029 51.487427,-2.636073 51.487466,-2.636126 51.487465,-2.636175 51.487489,-2.636267 51.487501,-2.636289 51.487534,-2.636311 51.487531,-2.636342 51.487556,-2.636403 51.487580,-2.636403 51.487595,-2.636457 51.487614,-2.636500 51.487609,-2.636503 51.487629,-2.636595 51.487680,-2.636595 51.487692,-2.636620 51.487707,-2.636668 51.487708,-2.636666 51.487734,-2.636695 51.487753,-2.636785 51.487783,-2.636821 51.487781,-2.636918 51.487808)))
- point
- POINT (-2.636524 51.487583)
- notes
- English oak, small-leaved lime, cherry, common beech along nothern boundary of western playing field
- organisation
- entry-date
- 2011-10-06
- start-date
- 2011-10-06
- end-date
How to fix this issue
Your dataset is missing the tree-preservation-order column.
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.
How to improve Bristol City 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