Skip to main content

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

South Cambridgeshire District Council

Tree preservation zone

There is a problem

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

Bourn Parish

reference
TPO 0015 (1972)/A1
name
Bourn Parish
tree-preservation-order
TPO 0015 (1972)
tree-preservation-zone-type
area
geometry
MULTIPOLYGON (((-0.064373 52.189590,-0.064459 52.189534,-0.064782 52.189768,-0.064896 52.189842,-0.065015 52.189938,-0.067476 52.188873,-0.068261 52.188581,-0.068544 52.188719,-0.068593 52.188691,-0.069004 52.188429,-0.069146 52.188323,-0.069182 52.188287,-0.069251 52.188191,-0.069324 52.188071,-0.069340 52.188032,-0.069423 52.187713,-0.069473 52.187398,-0.069519 52.186983,-0.069569 52.186381,-0.069005 52.186190,-0.068884 52.186171,-0.068686 52.186182,-0.067604 52.186411,-0.066698 52.186658,-0.066366 52.186768,-0.066059 52.186886,-0.065798 52.187005,-0.065754 52.187036,-0.065745 52.187053,-0.065728 52.187187,-0.065706 52.187240,-0.065623 52.187330,-0.065581 52.187357,-0.065467 52.187406,-0.064991 52.187584,-0.065017 52.187658,-0.065261 52.187906,-0.065197 52.187930,-0.065325 52.188064,-0.064406 52.188472,-0.064254 52.188513,-0.064157 52.188467,-0.064132 52.188524,-0.064065 52.188631,-0.063823 52.189006,-0.063727 52.189134,-0.063615 52.189182,-0.063134 52.189559,-0.063246 52.189614,-0.063576 52.189308,-0.063639 52.189263,-0.063799 52.189293,-0.063874 52.189347,-0.064220 52.189516,-0.064306 52.189550,-0.064373 52.189590)))
point
POINT (-0.066887 52.187981)
notes
entry-date
2025-06-27
start-date

start-date must be a real date

1972-07-26
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 South Cambridgeshire District 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