Skip to main content

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

Calderdale Metropolitan Borough Council

Tree preservation zone

There is a problem

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

Land Adjoining Spa House Farm, Horley Green Lane, Shibden

reference
94/00822/C
name
Land Adjoining Spa House Farm, Horley Green Lane, Shibden
tree-preservation-order

undefined

94/00822/C
tree-preservation-zone-type
woodland
geometry
MULTIPOLYGON (((-1.847018 53.737672,-1.847608 53.737625,-1.847747 53.737785,-1.847870 53.737973,-1.847992 53.738333,-1.848131 53.738491,-1.849214 53.738271,-1.849071 53.738051,-1.849052 53.737991,-1.849002 53.737899,-1.848823 53.737888,-1.848608 53.737862,-1.848181 53.737756,-1.848107 53.737770,-1.848070 53.737768,-1.848013 53.737708,-1.847953 53.737610,-1.848015 53.737580,-1.848144 53.737547,-1.848397 53.737453,-1.848514 53.737421,-1.848657 53.737406,-1.848746 53.737444,-1.848838 53.737463,-1.848996 53.737475,-1.849092 53.737462,-1.849113 53.737451,-1.849206 53.737321,-1.849173 53.737218,-1.848688 53.737218,-1.848548 53.737205,-1.848476 53.737188,-1.848416 53.737187,-1.848351 53.737203,-1.848268 53.737258,-1.848076 53.737325,-1.847822 53.737302,-1.847644 53.737306,-1.847555 53.737295,-1.847491 53.737284,-1.847419 53.737253,-1.847302 53.737179,-1.847066 53.736982,-1.846953 53.736874,-1.846900 53.736754,-1.846898 53.736721,-1.846916 53.736633,-1.847001 53.736511,-1.847022 53.736391,-1.847025 53.736318,-1.847012 53.736224,-1.846991 53.736169,-1.846980 53.736069,-1.846984 53.735979,-1.847017 53.735899,-1.847087 53.735891,-1.847199 53.735893,-1.847528 53.735920,-1.847819 53.735971,-1.847969 53.736020,-1.848307 53.736093,-1.848537 53.736120,-1.848713 53.736120,-1.848910 53.736139,-1.849198 53.736188,-1.849381 53.736230,-1.849513 53.736243,-1.849849 53.736256,-1.850015 53.736252,-1.850118 53.736211,-1.850151 53.736189,-1.850263 53.736155,-1.850327 53.736145,-1.850503 53.736146,-1.850550 53.736138,-1.850570 53.736121,-1.850572 53.736094,-1.850562 53.736069,-1.850540 53.736055,-1.850391 53.736056,-1.850056 53.736014,-1.849929 53.736052,-1.849812 53.736099,-1.849703 53.736124,-1.849660 53.736126,-1.849186 53.736083,-1.848866 53.736026,-1.848588 53.735966,-1.848328 53.735956,-1.848042 53.735923,-1.847969 53.735902,-1.847886 53.735839,-1.847823 53.735817,-1.847704 53.735792,-1.847201 53.735750,-1.847007 53.735725,-1.847071 53.735602,-1.846765 53.735608,-1.846747 53.735662,-1.846683 53.735770,-1.846564 53.735769,-1.846614 53.735677,-1.846204 53.735604,-1.846227 53.735550,-1.846289 53.735312,-1.846384 53.735325,-1.846740 53.735410,-1.846775 53.735370,-1.846862 53.735408,-1.847033 53.735297,-1.847623 53.735509,-1.847661 53.735339,-1.847619 53.735053,-1.847618 53.734982,-1.847202 53.734999,-1.847063 53.734992,-1.846392 53.735091,-1.846195 53.735100,-1.846093 53.735161,-1.846108 53.735185,-1.846108 53.735236,-1.846011 53.735348,-1.845976 53.735412,-1.845929 53.735458,-1.845901 53.735511,-1.845883 53.735560,-1.845896 53.735694,-1.845909 53.735763,-1.845926 53.735763,-1.845929 53.735756,-1.846122 53.735783,-1.846393 53.735854,-1.846632 53.735871,-1.846510 53.736070,-1.846454 53.736250,-1.846424 53.736407,-1.846401 53.736626,-1.846411 53.736722,-1.846443 53.736785,-1.846524 53.736878,-1.846811 53.737131,-1.846983 53.737310,-1.847071 53.737387,-1.847219 53.737459,-1.847290 53.737484,-1.847459 53.737525,-1.847491 53.737561,-1.847378 53.737598,-1.846992 53.737648,-1.847018 53.737672)))
point
POINT (-1.847643 53.736659)
notes
Ash, beech, hawthorn, holly, oak, sycamore
entry-date
1994-03-23
start-date
1994-03-23
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 Calderdale Metropolitan Borough 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