Medway Council
Tree preservation zone
There is a problem
- 93 entries must have dates in YYYY-MM-DD format
entity: 19128569
- reference
- M3-1998
- name
- tree-preservation-order
- tree-preservation-zone-type
- geometry
- MULTIPOLYGON (((0.539638 51.331628,0.539568 51.331726,0.539342 51.332016,0.539084 51.332329,0.538998 51.332436,0.538986 51.332449,0.538979 51.332454,0.538948 51.332469,0.538926 51.332476,0.538892 51.332483,0.538863 51.332484,0.538838 51.332479,0.538812 51.332471,0.538782 51.332458,0.538770 51.332446,0.538751 51.332420,0.538738 51.332396,0.538723 51.332361,0.538720 51.332349,0.538686 51.332269,0.538681 51.332253,0.538671 51.332207,0.538669 51.332095,0.538654 51.331967,0.538654 51.331952,0.538650 51.331917,0.538647 51.331907,0.538648 51.331897,0.538658 51.331873,0.538673 51.331847,0.538755 51.331682,0.538779 51.331644,0.538803 51.331616,0.538888 51.331506,0.538940 51.331456,0.539012 51.331379,0.539060 51.331325,0.539096 51.331290,0.539163 51.331231,0.539346 51.331264,0.539840 51.331335,0.539763 51.331451,0.539683 51.331567,0.539638 51.331628)))
- point
- POINT (0.539138 51.331791)
- notes
- entry-date
- 2026-08-11
- start-date
- end-date
How to fix this issue
Your data is missing a start-date.
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
- Fix the errors indicated
- Use the check service to make sure the data meets the standard
- Publish the updated data on the endpoint URL