Skip to main content
Historic England

Conservation area

There is a problem

  • entry-date column must be in YYYY-MM-DD format

Swindon Prospect Place

reference
4874
name
Swindon Prospect Place
designation-date
1990-06-25
document-url
https://www.swindon.gov.uk/download/downloads/id/5245/conservation_area_appraisal_-_swindon_prospect_place.pdf
documentation-url
geometry
MULTIPOLYGON (((-1.778089 51.553554,-1.777702 51.553560,-1.777702 51.553580,-1.777652 51.553580,-1.777616 51.553609,-1.777617 51.553837,-1.777786 51.553834,-1.777812 51.553932,-1.777843 51.554104,-1.777973 51.554090,-1.778230 51.554519,-1.778356 51.554748,-1.778609 51.555247,-1.778946 51.555214,-1.779062 51.555222,-1.779945 51.555164,-1.780453 51.555119,-1.780554 51.555098,-1.780987 51.555052,-1.780950 51.554914,-1.780879 51.554798,-1.780886 51.554776,-1.780717 51.554507,-1.781407 51.554335,-1.781115 51.553905,-1.781118 51.553874,-1.781145 51.553832,-1.781176 51.553804,-1.781217 51.553782,-1.781138 51.553675,-1.781081 51.553618,-1.781042 51.553557,-1.780839 51.553070,-1.780395 51.553121,-1.780326 51.553156,-1.779011 51.553287,-1.778956 51.553292,-1.778953 51.553281,-1.778546 51.553284,-1.778545 51.553415,-1.778088 51.553424,-1.778089 51.553554)))
point
POINT (-1.779585 51.554151)
notes
Documents are a page separated from source URL. Interactive map available Extra documents are available.
organisation
entry-date

entry-date must be a real date

2025-04-01
start-date
1990-06-25
end-date

How to fix this issue

Your dataset is missing the entry-date column.

The Conservation area guidance explains how to fix the issue:

entry-date

The date the record was last updated.

If the entity has never been updated, enter the same date as start-date.

Write in YYYY-MM-DD format.

Example:

2022-12-20

With dates, some data is better than no data, so:

  • 2022 is fine
  • 2022-12 is better
  • 2022-12-20 is brilliant

How to improve Historic England’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL