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

Harlings Shaw Copse Harlings Shaw Bletchingley

reference
132/TAN W1
name
Harlings Shaw Copse Harlings Shaw Bletchingley
tree-preservation-order

undefined

132/TAN
tree-preservation-zone-type
woodland
geometry
MULTIPOLYGON (((-0.083106 51.238812,-0.083129 51.238790,-0.083163 51.238593,-0.083118 51.238132,-0.082986 51.237646,-0.082913 51.237435,-0.082687 51.237252,-0.082310 51.237115,-0.082325 51.237151,-0.082117 51.237704,-0.082244 51.237886,-0.082237 51.238030,-0.082253 51.238030,-0.082249 51.238124,-0.082285 51.238471,-0.082263 51.238996,-0.082273 51.239114,-0.082242 51.239158,-0.082225 51.239354,-0.082140 51.239522,-0.082098 51.239652,-0.081913 51.239672,-0.081699 51.239644,-0.081543 51.239675,-0.081571 51.239656,-0.081352 51.239662,-0.081296 51.239677,-0.081215 51.239628,-0.081158 51.239539,-0.081144 51.239455,-0.081098 51.239371,-0.081117 51.239311,-0.081002 51.239262,-0.080903 51.239260,-0.080684 51.239292,-0.080486 51.239305,-0.080647 51.239437,-0.080727 51.239522,-0.080855 51.239594,-0.080965 51.239645,-0.081099 51.239741,-0.081119 51.239786,-0.081159 51.239938,-0.081205 51.240020,-0.081218 51.240090,-0.081198 51.240209,-0.081310 51.240294,-0.081494 51.240261,-0.081783 51.240236,-0.081928 51.240173,-0.082164 51.240007,-0.082462 51.239704,-0.082792 51.239326,-0.083106 51.238812)))
point
POINT (-0.082283 51.238815)
notes
organisation
entry-date
1984-06-20
start-date
1984-06-20
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