Medway Council
Tree preservation zone
There is a problem
- 91 entries must have dates in YYYY-MM-DD format
entity: 19178257
- reference
- G96/1990
- name
- tree-preservation-order
- tree-preservation-zone-type
- geometry
- MULTIPOLYGON (((0.553706 51.392654,0.553717 51.392639,0.553737 51.392635,0.553759 51.392643,0.553764 51.392653,0.553744 51.392671,0.553718 51.392668,0.553706 51.392654)),((0.553567 51.392505,0.553577 51.392490,0.553592 51.392486,0.553624 51.392500,0.553621 51.392513,0.553599 51.392522,0.553575 51.392517,0.553567 51.392505)),((0.553635 51.392465,0.553617 51.392455,0.553619 51.392439,0.553640 51.392430,0.553661 51.392433,0.553673 51.392447,0.553666 51.392460,0.553684 51.392470,0.553685 51.392480,0.553671 51.392493,0.553641 51.392492,0.553628 51.392478,0.553635 51.392465)))
- point
- POINT (0.553658 51.392521)
- notes
- entry-date
- 2026-05-09
- start-date
- end-date
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
- Fix the errors indicated
- Use the check service to make sure the data meets the standard
- Publish the updated data on the endpoint URL