Medway Council

Tree preservation zone

There is a problem

• 69 entries must have dates in YYYY-MM-DD format

entity: 19128365

• reference: G160-1996
• geometry: MULTIPOLYGON (((0.609878 51.339723,0.609823 51.339677,0.610070 51.339555,0.610144 51.339509,0.610414 51.339412,0.610584 51.339334,0.610787 51.339284,0.611243 51.339104,0.611365 51.339398,0.611594 51.339529,0.611842 51.339640,0.611939 51.339672,0.612198 51.339854,0.612654 51.340225,0.612851 51.340350,0.612588 51.340524,0.613191 51.340849,0.613691 51.341080,0.613740 51.341161,0.613716 51.341434,0.614004 51.341805,0.612258 51.341614,0.612084 51.341465,0.611690 51.341202,0.611592 51.341114,0.611332 51.340828,0.610811 51.340437,0.610714 51.340292,0.610598 51.340250,0.610497 51.340193,0.609878 51.339723)))
• point: POINT (0.611908 51.340509)
• entry-date: 2025-11-29
• start-date:

  start-date must be a real date

  1996-11-15

How to fix this issue

Your dataset is missing the start-date column.

The Tree preservation zone guidance explains how to fix the issue:

start-date

The date that the tree preservation order came into force, written in YYYY-MM-DD format.

Example: 1984-03-28

How to improve Medway 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