This guide lists all of the fields in the London Development Database, along with the GLA provided definition of the field, our own view to the field's purpose and -- where appropriate -- a commentary of the fields.
You can use the search box below if there is a particular kind of data you are interested in, to see if it is present in the database
permission_id
Number
Primary key (i.e. main identifier/reference number) for this `table
GLA Definition:Unique ID of the permission
borough_idNumber
ID for the London Borough who is responsible for granting planning permission (not to be confused with the ID the London Borough gives the application)
GLA Definition:
ID of the borough submitting the permission
Comments:
That this field appears so early may not be coincidental – boroughs are the main trackable subject within the database, which may be understood as a technology for disciplining local authorities.
status_rc
Text
The status of the planning application i.e. has it been completed? Has it lapsed? Was it withdrawn?
GLA Definition:
application details from ref code domain STATUS
Possible values:
Pending
Invalid
Submitted
Started
Completed
Lapsed
Superseded
Deleted
borough_ref character varying(50) Text 4 not null Planning application details Borough Reference The internal reference number given for The reference for the proposed application. This is a key field that can backlink this record to the more extensive data contained within the planning application.
mayoral_ref character varying(7) Text 5 Planning application details Mayoral Reference
permission_date date Date 6 not null Dates Permission date The date permission was granted If you wish to track who is politically responsible for a decision, this is a key field. For instance, you can cross-reference with political control of the borough, who was a council leader and so on.
permission_type_rc character varying(3) Text 7 Planning application details Type of Permission Option of around 20 pre-defined permission types, representing the types of planning application that can be made
decision_agency_rc character varying(3) Text 8 Decision making Decision Agency Who decides on the planning permission (B=Borough, G=Government Dept etc) Another key field for tracking accountability – just because a planning application was within a borough, it does not mean they were responsible for the decision. Nonetheless, it is likely that reporting does hold borough’s responsible for such decisions.
permission_lapses_date date Date 9 Dates Date Permission Lapses The date that the permission lapses. There are records without a completed status that are passed their permission lapses date at time of upload. This may suggests a reporting lag in the database, or a delay between extraction and upload.
descr character varying(4000) Text 10 not null Planning application details Description of proposed development Short summary of what planning permission is sought for A key field for understanding what the application consists on. Note the language here is not to be understood as neutral, but justificatory of what is going to happen. Treat with caution.