Skip guidance navigation

Design code

There are 2 datasets you must provide for design codes:

Format

You can provide data in one of these formats:

  • CSV
  • GeoJSON
  • GML
  • Geopackage

For more information, see how to provide your data.

Design code dataset

This dataset is about conservation areas. These are areas where extra planning controls apply due to their special architectural and historic interest.

The dataset must contain at least one entry (row) for each design code

It must containing the following fields (columns):

description

An optional short description of the design code.

Example: A design code for urban development in Felpersham consistent with vernacular buildings in Borchester.

design-code-status

document-url

The URL of the HTML, PDF or other document documenting the design code.

Example: http://www.borchester.gov.uk/document/dc01.pdf

documentation-url

The URL of the webpage citing the design code document.

Each document should be linked to on a documentation webpage that includes a short description of the design code. The website URL should be unique for design code, either by creating a separate page or a separate anchor (fragment identifier) for each design code.

Example: http://www.borchester.gov.uk/design-codes/#dc01

end-date

If applicable, the date that the design code was no longer in effect, written in YYYY-MM-DD format. If it's still in effect, leave the cell blank.

Example: 1999-01-20

entity

entry-date

The date this dataset was created or last updated, written in YYYY-MM-DD format.

Example: 2022-12-20

name

This will be the title of the design code displayed on our website.

Example: The design of chimneys in Borchester

notes

Optional text on how this data was made or produced, or how it can be interpreted.

organisation

prefix

reference

A reference or ID for each design code that is:

unique within your local planning authority dataset permanent - it doesn't change when the dataset is updated

If you don't use a reference already, you will need to create one. This can be a short set of letters or numbers.

Example: DCO1

start-date

The date that the design code came, or comes into force, written in YYYY-MM-DD format.

Example: 1984-03-28

Design code area dataset

This dataset is about conservation areas. These are areas where extra planning controls apply due to their special architectural and historic interest.

The dataset must contain at least one entry (row) for each design code area

It must containing the following fields (columns):

description

design-code

The reference of the design code which applies to this area.

design-code-area-type

design-code-rules

documentation-url

end-date

If applicable, the date that the design code area was no longer in effect, written in YYYY-MM-DD format. If it's still in effect, leave the cell blank.

Example: 1999-01-20

entity

entry-date

The date this dataset was created or last updated, written in YYYY-MM-DD format.

Example: 2022-12-20

geometry

The boundary for the design code area as a single polygon or multipolygon value. Points must be in the WGS84 coordinate reference system.

This should be in GeoJSON format.

Example: MULTIPOLYGON (((1.188829 51.23478,1.188376 51.234909,1.188381 51.234917,1.187912 51.235022...

name

This will be the display name of the page hosting data about this design code area on our website.

Example: Felpersham town centre

notes

Optional text on how this data was made or produced, or how it can be interpreted.

organisation

point

prefix

reference

A reference or ID for each design code area that is:

unique within your dataset permanent - it doesn't change when the dataset is updated

If you don't use a reference already, you will need to create one. This can be a short set of letters or numbers. This reference may be the same as the design code if only one design code applies to the area.

Example: DCA01

start-date

The date that the design code came into force, written in YYYY-MM-DD format.

Example: 1984-03-28