Skip to main content

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

London Borough of Waltham Forest

Conservation area

There is a problem

  • 1 entry must have a valid URI

Leyton Town Centre

reference
CA12
name
Leyton Town Centre
designation-date
2013-01-01
document-url

document-url must be a real URL

documentation-url
https://www.walthamforest.gov.uk/planning-and-building-control/design-and-conservation/conservation-areas-and-listed-buildings
geometry
MULTIPOLYGON (((-0.012702 51.559190,-0.012699 51.559192,-0.012712 51.559186,-0.012722 51.559178,-0.012725 51.559170,-0.012726 51.559162,-0.012722 51.559154,-0.012715 51.559146,-0.012593 51.559038,-0.012576 51.559028,-0.012554 51.559018,-0.012542 51.559010,-0.012398 51.558884,-0.012277 51.558774,-0.012259 51.558743,-0.012053 51.558563,-0.012022 51.558552,-0.012006 51.558553,-0.011993 51.558555,-0.011941 51.558577,-0.011926 51.558594,-0.011751 51.558669,-0.011419 51.558808,-0.011055 51.558965,-0.010735 51.559100,-0.010451 51.559224,-0.010440 51.559215,-0.010423 51.559214,-0.010238 51.559294,-0.010237 51.559301,-0.010239 51.559305,-0.010248 51.559313,-0.009917 51.559453,-0.009356 51.559696,-0.009258 51.559628,-0.009187 51.559558,-0.009065 51.559446,-0.008890 51.559521,-0.008850 51.559483,-0.008839 51.559430,-0.008667 51.559280,-0.008645 51.559265,-0.008493 51.559243,-0.008482 51.559247,-0.008470 51.559247,-0.008460 51.559243,-0.008455 51.559236,-0.008458 51.559235,-0.008282 51.559070,-0.008136 51.558930,-0.008048 51.558849,-0.007948 51.558751,-0.008400 51.558557,-0.008373 51.558545,-0.008347 51.558523,-0.007909 51.558121,-0.007887 51.558104,-0.007250 51.558371,-0.007228 51.558372,-0.007048 51.558448,-0.006948 51.558493,-0.006847 51.558503,-0.006854 51.558498,-0.006860 51.558489,-0.006862 51.558482,-0.006859 51.558472,-0.006830 51.558434,-0.006711 51.558288,-0.006648 51.558196,-0.006570 51.558076,-0.006556 51.558058,-0.006479 51.557935,-0.006435 51.557852,-0.006425 51.557831,-0.006424 51.557821,-0.006317 51.557616,-0.006261 51.557515,-0.006252 51.557504,-0.006213 51.557424,-0.006180 51.557362,-0.006174 51.557358,-0.006134 51.557352,-0.006083 51.557337,-0.006072 51.557326,-0.005977 51.557206,-0.005946 51.557216,-0.005648 51.557297,-0.005559 51.557357,-0.005771 51.557523,-0.005814 51.557647,-0.006007 51.557857,-0.005946 51.557890,-0.005970 51.557910,-0.006138 51.558068,-0.006136 51.558214,-0.006213 51.558289,-0.006222 51.558286,-0.006257 51.558330,-0.006302 51.558373,-0.006255 51.558388,-0.006295 51.558427,-0.006326 51.558417,-0.006486 51.558618,-0.006505 51.558635,-0.006573 51.558713,-0.006716 51.558850,-0.006680 51.558865,-0.006685 51.558870,-0.006751 51.558925,-0.006901 51.559061,-0.007060 51.559113,-0.007109 51.559156,-0.007084 51.559166,-0.007092 51.559174,-0.007077 51.559180,-0.007132 51.559225,-0.007104 51.559239,-0.007320 51.559395,-0.007351 51.559419,-0.007398 51.559448,-0.007540 51.559491,-0.007585 51.559521,-0.007599 51.559514,-0.007965 51.559742,-0.007957 51.559884,-0.007982 51.559901,-0.008116 51.559981,-0.008203 51.560038,-0.008223 51.560016,-0.008230 51.560011,-0.008377 51.559862,-0.008413 51.559887,-0.008395 51.559901,-0.008330 51.559967,-0.008358 51.559985,-0.008387 51.559969,-0.008428 51.559995,-0.008442 51.560012,-0.008445 51.560022,-0.008626 51.560146,-0.008768 51.560200,-0.009156 51.560480,-0.009204 51.560507,-0.009673 51.560255,-0.009722 51.560241,-0.009733 51.560221,-0.010311 51.560020,-0.010628 51.559907,-0.011024 51.559769,-0.011296 51.559676,-0.012144 51.559381,-0.012488 51.559263,-0.012621 51.559219,-0.012702 51.559190)))
point
POINT (-0.009042 51.559168)
notes
entry-date
2025-02-14
start-date
2013-01-01
end-date

How to fix this issue

Your data is missing a document-url.

The Conservation area guidance explains how to fix the issue:

document-url

A URL to the document containing the authoritative source for the area. This is usually a PDF containing the area drawn on a map.

Example: http://www.LPAwebsite.org.uk/data/conservationareas/smithroad-area.pdf

How to improve London Borough of Waltham Forest’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