Describes the fields in data returned by the API

Planning Applications

Principal data fields in planning application records

  • 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' see below)
  • app_state -> Combination of the 'status' and 'decision' fields - depending on which is available
  • app_type -> Combination of the 'application_type' and 'development_type' fields - depending on which is available
  • 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 appication proposal
  • lat -> Latitude (N/S location cordinate, rounded to 6 decimal places in range 48 to 62)
  • link -> Link for accessing the planning application details locally on this website
  • lng -> Longitude (E/W location coordinate, rounded to 6 decimal places in range -11 to 4)
  • name -> Unique name assigned to the application on this system
  • postcode -> Normalised full postcode (extracted from address fields if not supplied in source)
  • source_url -> Web address for the authority's planning information website
  • start_date -> The earliest of the 'date_received' or 'date_validated' fields - depending on which is available. (This and all other dates are in YYYY-MM-DD format)
  • uid -> A unique identifier assigned to the application by its planning authority
  • 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)

Other data fields in planning application records (these fields, along with the 'uid', 'address' and 'description' fields sbove, are derived directly from the source record)

  • 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_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 application lapses (statutory expiry date - 8 weeks after date validated or 13 weeks for large applications)
  • associated_application_uid -> The planning application id for an associated planning application. This may be because a revised application has been made
  • 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
  • easting -> OSGB36 easting value (OSIE36 in Northern Ireland)
  • 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
  • longitude -> WGS84 longitude value
  • meeting_date -> Date of the planning committee meeting that will decide the 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)
  • os_grid_ref -> Ordnance Survey grid reference (in letter number format e.g. TM 11400 52500)
  • parish -> Name of the local authority parish for this application (community council in Scotland and Wales)
  • permission_expires_date -> Date given planning permission expires
  • planning_portal_id -> Some councils list the planning application on the Planning Portal
  • reference -> Identifier or reference number assigned to the planning application by its authority - usually the same as the 'uid', but is also used for alternative identifiers if they exist
  • 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
  • uprn -> The unique property reference number from the National Land and Property Gazetteer (NLPG)
  • 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
  • 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)