Skip to main content

This is a new service – your feedback will help us to improve it.

Buckinghamshire Council

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

Bucks. County Council (Eton Rural District) Tree Preservation Order No.11 - 1952; dated 17/11/52; ma

reference
ZZZZZWESRW769
name
Bucks. County Council (Eton Rural District) Tree Preservation Order No.11 - 1952; dated 17/11/52; ma
tree-preservation-order

undefined

TPO/BCC/1952/11
tree-preservation-zone-type
geometry
MULTIPOLYGON (((-0.692376 51.535442,-0.692054 51.535990,-0.691937 51.536210,-0.691887 51.536403,-0.691867 51.536529,-0.691813 51.536969,-0.691834 51.536969,-0.691813 51.537089,-0.691769 51.537280,-0.691678 51.537586,-0.691582 51.537812,-0.691460 51.538016,-0.691216 51.538312,-0.693010 51.538298,-0.693148 51.538278,-0.693244 51.538251,-0.693272 51.538291,-0.693551 51.538280,-0.693589 51.538274,-0.693608 51.538263,-0.693766 51.538131,-0.693866 51.538100,-0.693947 51.538087,-0.694183 51.538080,-0.694356 51.538092,-0.694775 51.538023,-0.695262 51.535940,-0.695425 51.535104,-0.695926 51.534041,-0.696226 51.533007,-0.695970 51.531964,-0.696261 51.530967,-0.695771 51.531028,-0.695498 51.530947,-0.694038 51.531112,-0.692874 51.531312,-0.693325 51.532866,-0.693343 51.533232,-0.693337 51.533582,-0.693310 51.533760,-0.693218 51.534032,-0.692815 51.534751,-0.692618 51.535042,-0.692548 51.535104,-0.692526 51.535142,-0.692517 51.535199,-0.692376 51.535442)))
point
POINT (-0.694055 51.534728)
notes
organisation
entry-date
2017-07-04
start-date
2017-07-04
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 Buckinghamshire 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