Skip to main content

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

East Riding of Yorkshire Council

Tree preservation zone

There is a problem

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

Harland Way, Cottingham No. 2 - 1970

reference
tpo1764
name
Harland Way, Cottingham No. 2 - 1970
tree-preservation-order
181
tree-preservation-zone-type
woodland
geometry
MULTIPOLYGON (((-0.443394 53.789771,-0.443258 53.789676,-0.443058 53.789563,-0.442138 53.789073,-0.441901 53.788960,-0.441139 53.788725,-0.440893 53.788612,-0.440719 53.788554,-0.440075 53.788387,-0.439938 53.788330,-0.439155 53.788171,-0.438627 53.788137,-0.437940 53.788128,-0.437241 53.788196,-0.437047 53.788188,-0.437081 53.788249,-0.436559 53.788325,-0.436576 53.788358,-0.436221 53.788424,-0.436263 53.788530,-0.436372 53.788597,-0.436519 53.788637,-0.436611 53.788649,-0.436714 53.788634,-0.436902 53.788571,-0.437100 53.788491,-0.437305 53.788477,-0.437660 53.788427,-0.438060 53.788404,-0.438292 53.788407,-0.438542 53.788422,-0.438828 53.788464,-0.439297 53.788575,-0.439672 53.788728,-0.439814 53.788664,-0.440057 53.788628,-0.440510 53.788667,-0.440767 53.788759,-0.440864 53.788881,-0.440874 53.789112,-0.440918 53.789184,-0.441035 53.789042,-0.441269 53.788996,-0.441352 53.788997,-0.441528 53.789021,-0.441842 53.789047,-0.441924 53.789087,-0.442122 53.789271,-0.442320 53.789433,-0.442412 53.789467,-0.442559 53.789491,-0.442743 53.789537,-0.442807 53.789582,-0.442823 53.789637,-0.442886 53.789699,-0.443041 53.789772,-0.443394 53.789771)))
point
POINT (-0.439502 53.788615)
notes
entry-date
2026-03-17
start-date

start-date must be a real 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 East Riding of Yorkshire 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