Bristol City Council

Tree

There is a problem

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

Magpie Bottom Hanham BS15 8HD

• reference: ICGOVSDNBB000
• name: Magpie Bottom Hanham BS15 8HD
• tree-preservation-order:

  undefined

  TP090
• address-text: Address: Magpie Bottom Hanham BS15 8HD
• point: POINT (-2.520733 51.451594)
• geometry: MULTIPOLYGON (((-2.520704 51.451533,-2.520654 51.451549,-2.520616 51.451591,-2.520615 51.451611,-2.520634 51.451638,-2.520656 51.451652,-2.520710 51.451662,-2.520788 51.451646,-2.520835 51.451625,-2.520851 51.451587,-2.520835 51.451553,-2.520816 51.451536,-2.520790 51.451530,-2.520704 51.451533)))
• notes: INDIAN CEDAR - Cedrus deodara
• entry-date: 2011-10-14
• start-date: 2005-02-25

How to fix this issue

Your dataset is missing the tree-preservation-order column.

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

How to improve Bristol City Council’s data

1. Fix the errors indicated
2. Use the check service to make sure the data meets the standard
3. Publish the updated data on the endpoint URL