Describes the fields in data returned by the API

Planning Applications

Principal planning application data fields

  • address -> Postal address or location of the property to which the planning application applies
  • altid -> Any alternative identifier(s) for the application (alternative to 'uid' and 'reference' see below) (eg historical identifier)
  • authority_id -> Identifier for the planning authority of this application
  • authority_name -> Short name of the planning authority of this application
  • description -> The text describing the planning application proposal
  • link -> Link for accessing the planning application details locally on this website
  • name -> UK wide unique name assigned to the application on this system
  • rec_type -> Type of API record - in this case 'PlanApplic'
  • reference -> The latest unique identifier assigned to the application, if different from the 'uid' (usually this stays the same but can sometimes be changed in the source)
  • source_url -> Web address for the authority's planning information website (where these data come from)
  • uid -> The unique identifier for this application when it was first discovered
  • url -> Link for accessing the planning application details remotely on the planning authority website
  • when_updated -> Date and time this information was obtained from the planning authority website. (YYYY-MM-DDTHH:MM:SS format) (Note this is NOT when the planning information was last updated on the source website)

Secondary fields derived from source planning application fields (see below)
Note values can be null if there is no information to make the classification

  • associated_id -> Identifier(s) of other associated application(s) from the same planning authority (extracted from 'description' field)
  • app_size -> Size of the proposed development (note value can be null if there is no information to make the classification)
    • Large Major, large scale developments
    • Medium Other applications involving multiple dwellings
    • Small All others
  • app_state -> Decision status for the application (note value can be null if there is no information to make the classification)
    • Undecided The application is currently active, no decision has been made
    • Permitted The application was approved
    • Conditions The application was approved, but conditions were imposed
    • Rejected The application was refused
    • Withdrawn The application was withdrawn before a decision was taken
    • Referred The application was referred to government or to another authority
    • Unresolved The application is no longer active but no decision was made eg split decision
    • Other Status not known
  • app_type -> Type of the application (note value can be null if there is no information to make the classification)
    • Full Full and householder planning applications
    • Outline Proposals prior to a full application, including assessments, scoping opinions, outline applications etc
    • Amendment Amendments or alterations arising from existing or previous applications
    • Conditions Discharge of conditions imposed on existing applications
    • Heritage Conservation issues and listed buildings
    • Trees Tree and hedge works
    • Advertising Advertising and signs
    • Telecoms Telecommunications including phone masts
    • Other All other types eg agricultural, electrical
  • consulted_date -> Date consultation expired (the latest of the 'consultation_end_date', 'neighbour_consultation_end_date', 'last_advertised_date', 'latest_advertisement_expiry_date' or 'site_notice_end_date' fields - depending on which is available). (This and all other _dates are in YYYY-MM-DD format)
  • decided_date -> Date decision reached (the earliest of the 'decision_date', 'decision_issued_date' or 'decision_published_date' fields - depending on which is available).
  • distance -> Distance of the application from the centre, if returned as part of a location search (km)
  • id_type -> An application type description derived from the application identifier (if 'application_type' or 'development_type' do not exist)
  • lat -> Latitude (N/S location cordinate, rounded to 6 decimal places in range 48 to 62) (extracted from 'northing'/'latitude' if supplied in source, otherwise derived from 'postcode')
  • lng -> Longitude (E/W location coordinate, rounded to 6 decimal places in range -11 to 4) (extracted from 'easting'/'longitude' if supplied in source, otherwise derived from 'postcode')
  • n_statutory_days -> Statutory time period (in days) between registration and expected decision (usually 56, 91 or 112 days) (interval between the latest of the 'date_received' or 'date_validated' fields and the latest of the 'application_expires_date' or 'target_decision_date' fields)
  • postcode -> Normalised full postcode (extracted from address field(s) if not supplied in source)
  • start_date -> Date application made (the earliest of the 'date_received' or 'date_validated' fields - depending on which is available).

Source data fields scraped from planning application records (these fields, along with the 'uid', 'reference', 'altid', 'address', 'postcode' and 'description' above, are derived directly from the planning authority website)
Note these fields are optional and will be missing if not present in the source

  • agent_address -> Address of the person or company acting for the planning applicant
  • agent_company -> Any company or partnership acting for the planning applicant
  • agent_name -> Name of the person or company acting for the planning applicant For Data Protection reasons this value is not stored but there is a note if it is available in the source
  • agent_tel -> Telephone number of the person or company acting for the planning applicant
  • appeal_date -> Date of any appeal (date the appeal process was started or registered)
  • appeal_decision_date -> Date of appeal decision (date the appeal process ended)
  • appeal_reference -> Identifier for any appeal
  • appeal_result -> The outcome of any appeal
  • appeal_status -> Current status of any appeal
  • appeal_type -> Type of any appeal
  • applicant_company -> Any company or partnership applying for the planning application
  • applicant_name -> Name of the person or company applying for the planning application For Data Protection reasons this value is not stored but there is a note if it is available in the source
  • applicant_address -> Address of the person or company applying for the planning application
  • application_type -> Type of planning application
  • application_expires_date -> Date on which the statutory period for a decision expires (8 weeks after date validated or 13 weeks for large applications) (see 'target_decision_date')
  • case_officer -> Name of the case officer For Data Protection reasons this value is not stored but there is a note if it is available in the source
  • comment_url -> Web address for comments on the planning application to be added by the publlic
  • comment_date -> Last date on which comments can be accepted
  • consultation_end_date -> Date that the consultation period ends
  • consultation_start_date -> Date that the consultation period starts (probably the same as the date validated / registered / statutory start date)
  • date_received -> Date the application was first received
  • date_validated -> Date the application was deemed valid. Also known as the statutory start date or the date of registration on the authority's register of planning applications
  • decided_by -> The committee / person / contact that made the decision or recommendation. Can be just an indication that it was 'Delegated' to a person or decided by a 'Committee'
  • decision -> The decision or recommendation made regarding the planning application
  • decision_date -> Date the determination was actually made
  • decision_issued_date -> Date decision was issued
  • decision_published_date -> Date decision was published
  • development_type -> Type of development proposed in the planning application
  • district -> Name of the geographical district for this application
  • docs -> List of application document details (possibly including URL, title, type and date) where available and accessible for scraping
  • docs_url -> Web address if the document details for this application are on a different website
  • easting -> OSGB36 easting value (OSIE36 in Northern Ireland)
  • first_advertised_date -> Date advertisement first appeared in press
  • last_advertised_date -> Date advertisement last appeared in press
  • latest_advertisement_expiry_date -> Expiry date for responses from most recent advertisement
  • latitude -> WGS84 latitude value (if specified on the source website)
  • longitude -> WGS84 longitude value (if specified on the source website)
  • map_url -> Web address for any online map showing the planning development
  • meeting_date -> Date of the planning committee meeting that will decide the application
  • n_constraints -> Number of constraints placed on this application (integer)
  • n_comments -> Number of comments made on this application
  • n_documents -> Number of documents associated with this application
  • neighbour_consultation_end_date -> Date that the neighbour consultation period ends (not necessarily the same as the main consultation period)
  • neighbour_consultation_start_date -> Date that the neighbour consultation period starts (not necessarily the same as the main consultation period)
  • northing -> OSGB36 northing value (OSIE36 in Northern Ireland)
  • parish -> Name of the local authority parish for this application (community council in Scotland and Wales)
  • permission_expires_date -> Date given planning permission expires (generally three years from the date granted)
  • planning_portal_id -> Some councils list the planning application on the Planning Portal, this is the identifier (format PP-nnnnnnnn) (extracted from 'altid' field if not supplied in source)
  • site_notice_end_date -> Date that any site notice expired during the consultation period
  • site_notice_start_date -> Date that any site notice was first issued during the consultation period
  • status -> Status of the application (which will change over its lifetime)
  • target_decision_date -> Date the decision is intended to be made in the future (see 'application_expires_date')
  • uprn -> The unique property reference number from the National Address Gazetteer For OS licensing reasons this value is not shown but there is a note if it is available in the source
  • ward_name -> Name of the local authority electoral division/district for this application

Planning Areas

Data fields in planning area records

  • area_id -> Identifier for this planning area
  • area_type -> Type of geographical or administrative area
  • branch -> Branch level from apex of linked areas (where trunk is zero)
  • gss_code -> ONS GSS identifier for this local authority or region
  • iso31662_code -> ISO 3166-2 code for this area
  • name -> Short unique name of this planning area
  • linked_regions -> List of names of regions this area is associated with
  • long_name -> Official name of this planning area
  • mapit_code -> Identifier for this local authority or region on mapit.mysociety.org
  • n_applications -> Number of planning applications available from this and any child planning authorities
  • n_children -> Number of child areas this area is linked to
  • n_siblings -> Number of sibling areas this area is associated with
  • own_applications -> Number of planning applications available from this planning authority
  • osm_rel_code -> Identifier for any relation defining the boundary of this area on OpenStreetMap
  • parent_id -> Identifier of the parent for this planning area
  • parent_name -> Name of the parent for this planning area
  • planning_url -> Web address for the authority's planning information website
  • rec_type -> Type of API record - in this case 'PlanArea'
  • snac_code -> ONS SNAC identifier for this local authority or region
  • source -> Name of the source of the area's boundary information
  • source_url -> Web address for the source of the area's boundary information
  • url -> Web address for the area's main information website
  • when_updated -> Date and time the area's boundary information was obtained from source. (YYYY-MM-DDTHH:MM:SS format)