Skip to main content

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

Plymouth City Council

Tree preservation zone

There is a problem

  • tree-preservation-order column is missing values

69

reference
69
name
69
tree-preservation-order

tree-preservation-order missing

tree-preservation-zone-type
area
geometry
MULTIPOLYGON (((-4.062872 50.389276,-4.062875 50.389265,-4.062773 50.389257,-4.062681 50.389253,-4.062536 50.389252,-4.062417 50.389254,-4.062194 50.389261,-4.061624 50.389286,-4.061234 50.389318,-4.061046 50.389336,-4.061000 50.389345,-4.060966 50.389355,-4.060675 50.389422,-4.060631 50.389427,-4.060464 50.389467,-4.059948 50.389556,-4.059876 50.389567,-4.059641 50.389596,-4.059630 50.389600,-4.059619 50.389613,-4.059519 50.389619,-4.059507 50.389615,-4.059364 50.389638,-4.059298 50.389654,-4.059259 50.389667,-4.059222 50.389682,-4.059191 50.389703,-4.059108 50.389775,-4.059079 50.389805,-4.059057 50.389836,-4.059032 50.389885,-4.059009 50.389948,-4.059002 50.389983,-4.058993 50.390086,-4.059004 50.390166,-4.059012 50.390193,-4.059033 50.390243,-4.059057 50.390293,-4.059121 50.390361,-4.059224 50.390310,-4.059298 50.390279,-4.059260 50.390234,-4.059591 50.390128,-4.059761 50.390076,-4.060194 50.389950,-4.060594 50.389828,-4.060699 50.389801,-4.060939 50.389743,-4.061136 50.389699,-4.061114 50.389657,-4.061406 50.389596,-4.061507 50.389577,-4.061565 50.389563,-4.061783 50.389499,-4.062277 50.389388,-4.062543 50.389347,-4.062697 50.389318,-4.062814 50.389294,-4.062869 50.389281,-4.062872 50.389276)))
point
POINT (-4.06042 50.389691)
notes
St Marys Court Plymouth PL7 4QJ
entry-date
2024-12-13
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

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 Plymouth City 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