Skip to main content

This is a new service – your feedback will help us to improve it.

Cornwall Council

Conservation area

There is a problem

  • 87 entries must have valid URIs

LUDGVAN CHURCHTOWN

reference
DCO68
name
LUDGVAN CHURCHTOWN
designation-date
document-url
documentation-url

documentation-url must be a real URL

geometry
MULTIPOLYGON (((-5.495310 50.144453,-5.495058 50.144362,-5.494773 50.144274,-5.494404 50.144167,-5.494338 50.144144,-5.494283 50.144129,-5.494023 50.144045,-5.494078 50.143971,-5.494091 50.143944,-5.494118 50.143907,-5.494141 50.143884,-5.494259 50.143728,-5.494257 50.143703,-5.494379 50.143561,-5.494319 50.143545,-5.494100 50.143475,-5.494066 50.143490,-5.494058 50.143492,-5.494055 50.143502,-5.494036 50.143508,-5.494021 50.143538,-5.493999 50.143544,-5.493778 50.143628,-5.493761 50.143625,-5.493538 50.143896,-5.493503 50.143924,-5.493414 50.143882,-5.492941 50.143648,-5.492190 50.144164,-5.492096 50.144153,-5.492090 50.144157,-5.492084 50.144187,-5.492089 50.144255,-5.492186 50.144310,-5.492270 50.144354,-5.492301 50.144375,-5.492435 50.144434,-5.492472 50.144460,-5.492256 50.144542,-5.492087 50.144617,-5.492030 50.144636,-5.492071 50.144686,-5.492169 50.144811,-5.492177 50.144819,-5.492163 50.144819,-5.492041 50.144845,-5.491925 50.144873,-5.491876 50.144887,-5.491691 50.144930,-5.491629 50.144929,-5.491599 50.145040,-5.491597 50.145050,-5.491598 50.145053,-5.491587 50.145089,-5.491507 50.145323,-5.491503 50.145329,-5.491502 50.145337,-5.491481 50.145392,-5.491441 50.145486,-5.491410 50.145580,-5.491373 50.145709,-5.492025 50.145827,-5.492192 50.145859,-5.492229 50.145864,-5.492218 50.145884,-5.492389 50.145911,-5.492449 50.145922,-5.492613 50.145958,-5.492635 50.145915,-5.492643 50.145894,-5.492653 50.145853,-5.492667 50.145806,-5.492679 50.145773,-5.492710 50.145700,-5.492717 50.145678,-5.492729 50.145654,-5.492738 50.145643,-5.492758 50.145610,-5.492786 50.145569,-5.492864 50.145471,-5.492901 50.145419,-5.492983 50.145327,-5.493048 50.145245,-5.493076 50.145219,-5.493115 50.145191,-5.493177 50.145151,-5.493244 50.145112,-5.493312 50.145069,-5.493388 50.145025,-5.493391 50.145025,-5.493410 50.145016,-5.493425 50.145007,-5.493434 50.144994,-5.493434 50.144998,-5.493437 50.144994,-5.493443 50.144992,-5.493499 50.145002,-5.493583 50.145028,-5.493706 50.145057,-5.493715 50.145043,-5.493736 50.145053,-5.493766 50.145055,-5.493801 50.145047,-5.493818 50.145040,-5.493832 50.145027,-5.493947 50.144903,-5.493950 50.144898,-5.493904 50.144886,-5.493918 50.144853,-5.494022 50.144660,-5.494175 50.144684,-5.494220 50.144581,-5.494300 50.144598,-5.494389 50.144416,-5.495002 50.144499,-5.495003 50.144498,-5.495066 50.144504,-5.495236 50.144534,-5.495239 50.144530,-5.495252 50.144533,-5.495320 50.144457,-5.495310 50.144453)))
point
POINT (-5.492989 50.144694)
notes
entry-date
2024-09-10
start-date
1985-12-04
end-date

How to fix this issue

Your data is missing a documentation-url.

The Conservation area guidance explains how to fix the issue:

documentation-url

The URL of the webpage on your website that introduces the document.

Each document should be linked to from a documentation webpage that includes a short description of the data and the document you’re linking to. Each conservation area should have a unique URL. This means you can create a separate page for each one, or you could list several on one page. If you do that, there must be a separate anchor (fragment identifier) for each one. This means each section of your page should have its own URL. Most publishing systems will allow you to use a hashtag to create the identifiers for each conservation area you list - as in the examples shown.

Examples:

One conservation area per page: http://www.LPAwebsite.org.uk/conservationareas/smithroad

More than one conservation area per page with an anchor link for each one:

http://www.LPAwebsite.org.uk/conservationareas#smithroad

http://www.LPAwebsite.org.uk/conservationareas#broadhousepark

How to improve Cornwall Council’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