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

The Rural District Council of Amersham Interim Tree Preservation Order [No 2 of 1948]

reference
ZZZZDVESXE790
name
The Rural District Council of Amersham Interim Tree Preservation Order [No 2 of 1948]
tree-preservation-order

undefined

TPO/1948/002
tree-preservation-zone-type
geometry
MULTIPOLYGON (((-0.592521 51.662658,-0.592450 51.662584,-0.592377 51.662464,-0.592327 51.662437,-0.592184 51.662436,-0.592036 51.662456,-0.591921 51.662636,-0.591302 51.663367,-0.590695 51.664143,-0.590457 51.664391,-0.590326 51.664603,-0.590311 51.664685,-0.589735 51.665046,-0.589582 51.665126,-0.589333 51.665228,-0.589000 51.665407,-0.589099 51.665502,-0.589172 51.665547,-0.589201 51.665545,-0.589279 51.665518,-0.590361 51.665080,-0.590760 51.664911,-0.590953 51.664839,-0.591136 51.664754,-0.591226 51.664688,-0.591350 51.664573,-0.591651 51.664248,-0.591756 51.664153,-0.592011 51.664218,-0.592005 51.664171,-0.592010 51.664136,-0.592090 51.664047,-0.592212 51.663954,-0.592242 51.663919,-0.592294 51.663820,-0.592339 51.663684,-0.592344 51.663628,-0.592334 51.663595,-0.592296 51.663551,-0.592215 51.663506,-0.592211 51.663495,-0.592224 51.663468,-0.592299 51.663343,-0.592613 51.663018,-0.592707 51.662911,-0.592765 51.662781,-0.592771 51.662761,-0.592521 51.662658)))
point
POINT (-0.591314 51.663933)
notes
organisation
entry-date
2010-02-18
start-date
2010-02-18
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