Skip to main content

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

Your data has issues

There is a problem

  • document-url column must have valid URIs
Reference Name Developer agreement type Planning application Document URL Notes Organisation Entry date Start date End date
S106-00633 section-106 PK01/3133/F

Invalid URI

2024-05-15 2024-05-15
S106-00634 section-106 PK01/3133/F

Invalid URI

1970-01-01 1970-01-01
S106-00614 section-106 PK04/1965/O

Invalid URI

2022-05-26 2022-05-26
S106-00615 section-106 PK04/1965/O

Invalid URI

2022-05-22 2022-05-22
S106-00142 section-106 PK04/1965/O

Invalid URI

2013-06-12 2013-06-12
S106-00204 section-106 PK04/1965/O

Invalid URI

2016-11-28 2016-11-28
S106-00300 section-106 PK04/1965/O

Invalid URI

2018-06-28 2018-06-28
S106-00438 section-106 PK04/1965/O

Invalid URI

2019-12-18 2019-12-18
S106-00174 section-106 PK09/0927/F

Invalid URI

2009-08-14 2009-08-14
S106-00078 section-106 PK10/0057/F

Invalid URI

2010-04-09 2010-04-09
S106-00430 section-106 PK10/1057/F

Invalid URI

2019-05-09 2019-05-09
S106-00431 section-106 PK10/1057/F

Invalid URI

2019-05-09 2019-05-09
S106-00432 section-106 PK10/1057/F

Invalid URI

2019-05-09 2019-05-09
S106-00154 section-106 PT11/1441/O

Invalid URI

2013-03-08 2013-03-08
S106-00155 section-106 PT11/1441/O

Invalid URI

2015-11-25 2015-11-25
S106-00607 section-106 PT06/1001/O

Invalid URI

2014-05-27 2014-05-27
S106-00433 section-106 PK10/2627/F

Invalid URI

2019-04-04 2019-04-04
S106-00388 section-106 PT13/0002/O

Invalid URI

2017-12-01 2017-12-01
S106-00214 section-106 PK12/0429/O

Invalid URI

2014-09-05 2014-09-05
S106-00013 section-106 PK12/1619/F

Invalid URI

2013-05-02 2013-05-02
S106-00215 section-106 PT12/0263/EXT

Invalid URI

2017-01-19 2017-01-19
S106-00216 section-106 PT12/0263/EXT

Invalid URI

2017-01-17 2017-01-17
S106-00033 section-106 PT13/3541/O

Invalid URI

2014-11-13 2014-11-13
S106-00152 section-106 PT12/2395/O

Invalid URI

2013-04-23 2013-04-23
S106-00225 section-106 PT13/0510/F

Invalid URI

2017-03-29 2017-03-29
S106-00665 section-106 PK12/1913/O

Invalid URI

2024-11-08 2024-11-08
S106-00229 section-106 PT14/1886/O

Invalid URI

2017-09-20 2017-09-20
S106-00128 section-106 PT14/1886/O

Invalid URI

2016-02-02 2016-02-02
S106-00212 section-106 PT14/4573/RVC

Invalid URI

2017-01-26 2017-01-26
S106-00086 section-106 PT14/1260/O

Invalid URI

2015-07-16 2015-07-16
S106-00087 section-106 PT14/1260/O

Invalid URI

2015-07-16 2015-07-16
S106-00088 section-106 PT14/1260/O

Invalid URI

2015-07-16 2015-07-16
S106-00089 section-106 PT14/1260/O

Invalid URI

2015-07-16 2015-07-16
S106-00146 section-106 MODK15/0001

Invalid URI

2015-05-29 2015-05-29
S106-00361 section-106 PT15/1179/O

Invalid URI

2015-07-29 2015-07-29
S106-00362 section-106 PT15/1179/O

Invalid URI

2015-07-29 2015-07-29
S106-00363 section-106 PT15/1179/O

Invalid URI

2015-07-29 2015-07-29
S106-00364 section-106 PT15/1179/O

Invalid URI

2015-07-29 2015-07-29
S106-00365 section-106 PT15/1179/O

Invalid URI

2015-07-29 2015-07-29
S106-00366 section-106 PT15/1179/O

Invalid URI

2015-07-29 2015-07-29
S106-00367 section-106 PT15/1179/O

Invalid URI

2015-07-29 2015-07-29
S106-00368 section-106 PT15/1179/O

Invalid URI

2015-07-29 2015-07-29
S106-00369 section-106 PT15/1179/O

Invalid URI

2015-07-29 2015-07-29
S106-00370 section-106 PT15/1179/O

Invalid URI

2015-07-29 2015-07-29
S106-00386 section-106 PT14/5028/O

Invalid URI

2018-11-19 2018-11-19
S106-00132 section-106 PT14/5028/O

Invalid URI

2014-12-01 2014-12-01
S106-00133 section-106 PT14/5028/O

Invalid URI

2014-12-01 2014-12-01
S106-00164 section-106 PK15/3537/F

Invalid URI

2014-12-01 2014-12-01
S106-00220 section-106 PT15/2917/O

Invalid URI

2017-06-29 2017-06-29
S106-00221 section-106 PT15/2917/O

Invalid URI

2017-06-16 2017-06-16

Showing rows 1 to 50 of 489

How to fix this issue

Your dataset is missing the document-url column.

The Developer agreement guidance explains how to fix the issue:

document-url

How to improve South Gloucestershire 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