Skip to main content

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

Tandridge District Council

Tree preservation zone

There is a problem

  • tree-preservation-order column must match the reference field in the tree preservation order dataset

Land adjacent to Caterham Bypass and r/o 17 - 41 Crescent Road Caterham

reference
188/TAN A2
name
Land adjacent to Caterham Bypass and r/o 17 - 41 Crescent Road Caterham
tree-preservation-order

undefined

188/TAN
tree-preservation-zone-type
area
geometry
MULTIPOLYGON (((-0.070991 51.281081,-0.070995 51.281202,-0.071050 51.281611,-0.071219 51.281945,-0.071447 51.282357,-0.071632 51.282717,-0.071718 51.282839,-0.071857 51.283192,-0.071962 51.283526,-0.072003 51.283842,-0.071997 51.284199,-0.071939 51.284523,-0.071768 51.284890,-0.071680 51.285061,-0.071495 51.285345,-0.071275 51.285603,-0.071582 51.285652,-0.071703 51.285591,-0.071942 51.285301,-0.072128 51.284986,-0.072281 51.284599,-0.072356 51.284326,-0.072376 51.284052,-0.072370 51.283772,-0.072297 51.283343,-0.072291 51.283260,-0.071771 51.282225,-0.071567 51.281884,-0.071487 51.281609,-0.071745 51.281546,-0.071963 51.281772,-0.072228 51.281955,-0.072502 51.282158,-0.072767 51.282368,-0.072824 51.282433,-0.073072 51.282651,-0.073238 51.282814,-0.073495 51.282977,-0.073994 51.283209,-0.074605 51.283410,-0.075088 51.283584,-0.075268 51.283468,-0.074662 51.283260,-0.074030 51.283031,-0.073734 51.282905,-0.073129 51.282385,-0.071905 51.281414,-0.071659 51.281206,-0.071277 51.281194,-0.071096 51.281197,-0.071004 51.280998,-0.070991 51.281081)))
point
POINT (-0.072242 51.283046)
notes
organisation
entry-date
1987-10-15
start-date
1987-10-15
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 Tandridge District 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