Dataset

planning application

Records of applications submitted to planning authorities

Fields

• Reference:

  the reference for the planning application

  Reference: reference

  Cardinality: 1

  Needs this field satisfies

  Fields should only be added if they satisfy a user need. This field helps satisfy the following needs.

  • This field and field received-date satisfy need dd-need-017.
  • This field and field linked-applications satisfy need dd-need-001.
• Name:

  A plain-language label for the planning application so it can be identified without relying on its reference

  Reference: name

  Cardinality: 1

  No needs satisfied by this field.

• Description:

  the description of the proposed development

  Reference: description

  Cardinality: 1

  Needs this field satisfies

  Fields should only be added if they satisfy a user need. This field helps satisfy the following needs.

  • This field satisfies need dd-need-028.
• Application types:

  one or more codelist values describing the application type

  Reference: application-types

  Cardinality: n

  Codelist: application-type

  Needs this field satisfies

  Fields should only be added if they satisfy a user need. This field helps satisfy the following needs.

  • This field and field development-scale, field planning-application (dataset decision-notice) and field decision (dataset decision-notice) satisfy need need-ps-012.
  • This field and field development-scale, field planning-application (dataset decision-notice) and field decision (dataset decision-notice) satisfy need need-ps-013.
  • This field and field development-scale, field planning-application (dataset decision-notice) and field decision (dataset decision-notice) satisfy need need-ps-014.
  • This field and field development-scale, field planning-application (dataset decision-notice) and field decision (dataset decision-notice) satisfy need need-ps-015.
  • This field and field development-scale, field planning-application (dataset decision-notice) and field decision (dataset decision-notice) satisfy need need-ps-016.
  • This field and field development-scale, field planning-application (dataset decision-notice) and field decision (dataset decision-notice) satisfy need need-ps-017.
  • This field and field planning-application (dataset decision-notice), field decision (dataset decision-notice) and field decision-date (dataset decision-notice) satisfy need need-ps-024.
  • This field and field development-scale, field planning-application (dataset decision-notice) and field decision (dataset decision-notice) satisfy need need-ps-006.
  • This field and field development-scale, field planning-application (dataset decision-notice) and field decision (dataset decision-notice) satisfy need need-ps-007.
  • This field and field development-scale, field planning-application (dataset decision-notice) and field decision (dataset decision-notice) satisfy need need-ps-008.
  • This field and field development-scale, field planning-application (dataset decision-notice) and field decision (dataset decision-notice) satisfy need need-ps-010.
  • This field and field development-scale, field planning-application (dataset planning-permission-timeline), field permission-process-event (dataset planning-permission-timeline), field event-date (dataset planning-permission-timeline), field planning-application (dataset decision-notice) and field decision-date (dataset decision-notice) satisfy need need-ps-025.
  • This field and field development-scale, field planning-application (dataset planning-permission-timeline), field permission-process-event (dataset planning-permission-timeline), field event-date (dataset planning-permission-timeline), field planning-application (dataset decision-notice) and field decision-date (dataset decision-notice) satisfy need need-ps-026.
  • This field and field development-scale, field planning-application (dataset decision-notice) and field decision (dataset decision-notice) satisfy need need-ps-005.
  • This field satisfies need need-ps-005.
  • This field satisfies need need-ps-001.
  • This field satisfies need need-ps-011.
  • This field and field planning-application (dataset decision-notice), field decision (dataset decision-notice) and field decision-date (dataset decision-notice) satisfy need need-ps-021.
  • This field and field planning-application (dataset decision-notice), field decision (dataset decision-notice) and field decision-date (dataset decision-notice) satisfy need need-ps-019.
  • This field and field planning-application (dataset decision-notice), field decision (dataset decision-notice) and field decision-date (dataset decision-notice) satisfy need need-ps-023.
  • This field and field planning-application (dataset decision-notice), field decision (dataset decision-notice) and field decision-date (dataset decision-notice) satisfy need need-ps-020.
• Site:

  the reference for the related site

  Reference: site

  Cardinality: 1

  Links to dataset: site

  Needs this field satisfies

  Fields should only be added if they satisfy a user need. This field helps satisfy the following needs.

  • This field and field geometry (dataset site), field address-text (dataset site) and field description (dataset site) satisfy need dd-need-051.
• Received date:

  the date the planning authority received the application

  Reference: received-date

  Cardinality: 1

  Needs this field satisfies

  Fields should only be added if they satisfy a user need. This field helps satisfy the following needs.

  • This field and field reference satisfy need dd-need-017.
  • This field and field planning-application (dataset planning-permission-timeline), field permission-process-event (dataset planning-permission-timeline) and field event-date (dataset planning-permission-timeline) satisfy need dd-need-066.
• Planning authority:

  Identifier of the planning authority that received this planning application

  Reference: planning-authority

  Cardinality: 1

  Codelist: planning-authority

  No needs satisfied by this field.

• Case officer:

  Name of the planning officer responsible for handling the application

  Reference: officer-name

  Cardinality: 1

  No needs satisfied by this field.

• Development scale:

  the local planning authority's classification of a full or outline planning application by development scale

  Reference: development-scale

  Cardinality: 1

  Codelist: development-scale

  Needs this field satisfies

  Fields should only be added if they satisfy a user need. This field helps satisfy the following needs.

  • This field and field application-types, field planning-application (dataset decision-notice) and field decision (dataset decision-notice) satisfy need need-ps-012.
  • This field and field application-types, field planning-application (dataset decision-notice) and field decision (dataset decision-notice) satisfy need need-ps-013.
  • This field and field application-types, field planning-application (dataset decision-notice) and field decision (dataset decision-notice) satisfy need need-ps-014.
  • This field and field application-types, field planning-application (dataset decision-notice) and field decision (dataset decision-notice) satisfy need need-ps-015.
  • This field and field application-types, field planning-application (dataset decision-notice) and field decision (dataset decision-notice) satisfy need need-ps-016.
  • This field and field application-types, field planning-application (dataset decision-notice) and field decision (dataset decision-notice) satisfy need need-ps-017.
  • This field and field application-types, field planning-application (dataset decision-notice) and field decision (dataset decision-notice) satisfy need need-ps-006.
  • This field and field application-types, field planning-application (dataset decision-notice) and field decision (dataset decision-notice) satisfy need need-ps-007.
  • This field and field application-types, field planning-application (dataset decision-notice) and field decision (dataset decision-notice) satisfy need need-ps-008.
  • This field and field application-types, field planning-application (dataset decision-notice) and field decision (dataset decision-notice) satisfy need need-ps-010.
  • This field and field application-types, field planning-application (dataset planning-permission-timeline), field permission-process-event (dataset planning-permission-timeline), field event-date (dataset planning-permission-timeline), field planning-application (dataset decision-notice) and field decision-date (dataset decision-notice) satisfy need need-ps-025.
  • This field and field application-types, field planning-application (dataset planning-permission-timeline), field permission-process-event (dataset planning-permission-timeline), field event-date (dataset planning-permission-timeline), field planning-application (dataset decision-notice) and field decision-date (dataset decision-notice) satisfy need need-ps-026.
  • This field and field application-types, field planning-application (dataset decision-notice) and field decision (dataset decision-notice) satisfy need need-ps-005.
• Planning performance agreement:

  whether the application was subject to a Planning Performance Agreement

  Reference: planning-performance-agreement

  Cardinality: 1

  Needs this field satisfies

  Fields should only be added if they satisfy a user need. This field helps satisfy the following needs.

  • This field and field planning-application (dataset planning-permission-timeline), field permission-process-event (dataset planning-permission-timeline) and field event-date (dataset planning-permission-timeline) satisfy need need-ps-027.
  • This field satisfies need need-ps-025.
  • This field satisfies need need-ps-026.
• Withdrawn date:

  the date the planning application was withdrawn

  Reference: withdrawn-date

  Cardinality: 1

  Needs this field satisfies

  Fields should only be added if they satisfy a user need. This field helps satisfy the following needs.

  • This field satisfies need dd-need-075.
• Linked applications:

  references to earlier applications this application directly links to

  Reference: linked-applications

  Cardinality: n

  Needs this field satisfies

  Fields should only be added if they satisfy a user need. This field helps satisfy the following needs.

  • This field and field reference satisfy need dd-need-001.
• Document URL:

  a URL to the completed application form

  Reference: document-url

  Cardinality: 1

  Needs this field satisfies

  Fields should only be added if they satisfy a user need. This field helps satisfy the following needs.

  • This field and field planning-application (dataset decision-notice) and field decision (dataset decision-notice) satisfy need dd-need-032.
  • One of these fields or field documentation-url satisfy need dd-need-032.
• Documentation URL:

  the URL where supporting documents for the application can be accessed

  Reference: documentation-url

  Cardinality: 1

  Needs this field satisfies

  Fields should only be added if they satisfy a user need. This field helps satisfy the following needs.

  • This field and field planning-application (dataset decision-notice) and field decision (dataset decision-notice) satisfy need dd-need-032.
  • One of these fields or field document-url satisfy need dd-need-032.
• Notes:

  Optional notes that provide additional context about the planning application

  Reference: notes

  Cardinality: 1

  No needs satisfied by this field.

Needs satisfied by this dataset

Datasets should only be included in the specification if they satisfy user needs.

No recorded links yet.