Skip to main content
Historic England

Conservation area

There is a problem

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

Fittleton and Haxton

reference
2593
name
Fittleton and Haxton
designation-date
1981-02-05
document-url
documentation-url
https://www.wiltshire.gov.uk/planning-conservation-areas
geometry
MULTIPOLYGON (((-1.793674 51.245703,-1.793689 51.245483,-1.793729 51.245231,-1.793734 51.244954,-1.793764 51.244771,-1.793744 51.244481,-1.793861 51.244294,-1.793878 51.244299,-1.793897 51.244267,-1.793821 51.244253,-1.793719 51.244193,-1.793539 51.244041,-1.793381 51.243886,-1.793019 51.243619,-1.792930 51.243567,-1.792822 51.243474,-1.792677 51.243365,-1.792622 51.243291,-1.792555 51.243247,-1.792520 51.243212,-1.792499 51.243226,-1.792177 51.243043,-1.791930 51.242953,-1.791579 51.242809,-1.791502 51.242784,-1.791392 51.242762,-1.791146 51.242750,-1.790942 51.242759,-1.790846 51.242772,-1.790712 51.242773,-1.790520 51.242769,-1.790424 51.242756,-1.790424 51.242782,-1.790317 51.242772,-1.790318 51.242753,-1.790226 51.242745,-1.790222 51.242764,-1.789653 51.242729,-1.789690 51.242669,-1.789712 51.242623,-1.789708 51.242617,-1.789287 51.242535,-1.789265 51.242580,-1.789142 51.242547,-1.788967 51.242484,-1.788946 51.242498,-1.788485 51.242309,-1.788344 51.242244,-1.788320 51.242227,-1.788288 51.242166,-1.788191 51.242072,-1.788016 51.241877,-1.787868 51.242008,-1.787271 51.242476,-1.787234 51.242438,-1.787107 51.242337,-1.786977 51.242256,-1.786782 51.242162,-1.787167 51.241904,-1.786875 51.241748,-1.786716 51.241855,-1.786499 51.242029,-1.786491 51.242025,-1.786468 51.242042,-1.785829 51.241782,-1.785456 51.241650,-1.785314 51.241580,-1.785275 51.241658,-1.785114 51.241845,-1.785054 51.241927,-1.785520 51.242081,-1.785571 51.242122,-1.785836 51.242231,-1.785595 51.242447,-1.786005 51.242653,-1.786427 51.242852,-1.786487 51.242871,-1.786706 51.242974,-1.787381 51.243311,-1.787877 51.243539,-1.787908 51.243546,-1.787528 51.243797,-1.787868 51.244026,-1.787976 51.244114,-1.788330 51.243949,-1.788754 51.244359,-1.789142 51.244771,-1.789095 51.244855,-1.789069 51.244921,-1.789037 51.244929,-1.789022 51.245054,-1.789035 51.245121,-1.788984 51.245134,-1.789039 51.245246,-1.789102 51.245440,-1.789098 51.245554,-1.789125 51.245642,-1.789107 51.245645,-1.789116 51.245681,-1.789263 51.246057,-1.789493 51.246039,-1.789532 51.246044,-1.789732 51.246549,-1.789811 51.246640,-1.789900 51.246686,-1.789767 51.246892,-1.789656 51.247133,-1.789627 51.247181,-1.789562 51.247260,-1.789497 51.247313,-1.789392 51.247365,-1.789326 51.247388,-1.788743 51.247524,-1.788800 51.247590,-1.788900 51.247841,-1.789348 51.247760,-1.789392 51.247838,-1.789380 51.247958,-1.790107 51.247981,-1.790565 51.248035,-1.790663 51.248038,-1.790716 51.247907,-1.790749 51.247871,-1.790805 51.247835,-1.790837 51.247828,-1.790917 51.247844,-1.791142 51.247857,-1.791176 51.247850,-1.791264 51.247807,-1.791338 51.247735,-1.791389 51.247707,-1.791522 51.247692,-1.791553 51.247699,-1.791617 51.247635,-1.791679 51.247555,-1.791786 51.247451,-1.791870 51.247379,-1.792151 51.247166,-1.792320 51.247013,-1.792457 51.246939,-1.792574 51.246861,-1.792779 51.246777,-1.792887 51.246707,-1.793473 51.246444,-1.793597 51.246384,-1.793624 51.246364,-1.793688 51.246271,-1.793721 51.246072,-1.793710 51.245961,-1.793675 51.245788,-1.793674 51.245703)))
point
POINT (-1.790489 51.244739)
notes
No Appraisal document. Documents need to be requested by email to developmentmanagement@wiltshire.gov.uk
organisation
entry-date

entry-date must be a real date

2025-04-01
start-date
1981-02-05
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