The Library of Congress > Linked Data Service > LC Subject Headings (LCSH)

Somersetshire Coal Canal (England)


  • URI(s)

  • Instance Of

  • Scheme Membership(s)

  • Collection Membership(s)

  • Variants

    • Somerset Coal Canal (England)
  • Broader Terms

  • Sources

    • found: Work cat: Plan of the proposed navigable canal, between the River Kennet at Newbury, in the County of Berks; and the River Avon at Bath, in the County of Somerset, 1794:Map. Sub-title (whereby a navigable communication will be opened between the cities of London and Bristol. Likewise of a branch of the said canal near a place called Marsh Barn to the towns of Calne & Chippenham, to which is added a plan of the proposed Somersetshire Coal Canal)
    • found: Halse, R. The Somersetshire Coal Canal, 2011.
    • found: Inland Waterways Association website, July 17, 2019(The Somersetshire Coal Canal was originally a very profitable canal, providing a means of transport for the coal from the Somerset mines, and feeding traffic to the Kennet & Avon and Wilts & Berks canals. Only a very small portion of it now remains in water, at its junction with the Kennet & Avon Canal, where it is used as private moorings.)
    • found: Wikipedia, July 17, 2019(Somerset Coal Canal (originally known as the Somersetshire Coal Canal) was a narrow canal in England, built around 1800. Its route began in basins at Paulton and Timsbury, ran to nearby Camerton, over two aqueducts at Dunkerton, through a tunnel at Combe Hay, then via Midford and Monkton Combe to Limpley Stoke where it joined the Kennet and Avon Canal. This link gave the Somerset coalfield (which at its peak contained 80 collieries) access east toward London.)
  • Change Notes

    • 2019-07-17: new
    • 2019-10-04: revised
  • Alternate Formats

Suggest terminology


The LC Linked Data Service welcomes any suggestions you might have about terminology used for a given heading or concept.

Would you like to suggest a change to this heading?

Please provide your name, email, and your suggestion so that we can begin assessing any terminology changes.

Fields denoted with an asterisk (*) are required.