Dorset & Somerset Canal Evidences

- click to open the interactive web map; you can always come back to view this information page from within the web map by clicking the ( i ) icon at the top left of the map.

(Author: Richard Thomas, March 2022)

Table of Contents:

Introduction

“One bomb fell on Wincanton during the last war and destroyed almost all known records of the Dorset & Somerset Canal” - Kenneth R. Clew (1970)

This project is to map the most likely path and features of the only part of the Dorset and Somerset Canal that was ever (partially) built - the branch line from Frome to Nettlebridge in Somerset. The project’s primary aims are:

An overview of the whole canal and its history can be found at the Dorset & Somerset Canal website.

Web Map Instructions

The web map (if not already opened) can be opened with the [View the map] button at the top of this page.

Layer Control pane (on the right hand side): use this to select the data layers to display/hide. Note that layer name text will be greyed out and italicized if it is not being rendered because it is out of range (zoom in more for it to appear). At the bottom of this (scrollable) pane a single base layer can be selected (map, aerial photography, LiDAR elevation) to display under the data. This pane can be hidden with the [»] icon at the top right.

Click/Touch a feature: display its attributes in a popup window. Specifically, if a section of the canal path is clicked (i.e. the “probable path evidence” layer) the evidence for why that section is thought to be located there is presented.

Map buttons (down the left hand side):

Other Mouse/Touch controls:

“BNG Coords” display (at the top left): gives the British National Grid (Easting, Northing) coordinates (in metres) of the cursor (or finger position on touch displays). To convert to a 6-digit OS Grid Reference, take digits 2-4 of each coordinate and prefix with “ST” - for example (366847,148822) = ST668488.

Initial Data Loading: note that with a slow network connection, the data layers may initially take a while to load as all data is loaded into the web browser at start-up. However, after that point (and on future visits to the web page if the data is still in the browser cache), the only data loaded over the network will be imagery for any base layer that is turned on, so data layer features should render quickly.

Offline Map Usage: Because the data layers are all loaded at start-up, if you keep the web map browser tab open (or if you re-visit the website and it is still in your browser cache), you can continue to use the web map when you do not have a network connection. You would only need a network connection to update any base layer imagery. In this situation it is recommended to turn off base layers (untick “Map Base Layer”) and to turn on the data layer group “OS Open Data (context if no base map)”.

Source Maps & Aerial Data

Outlined below are all the source maps and aerial photography/LiDAR data used in researching this project, with a note on how useful (or otherwise) each source was. For permissions reasons, most of these sources cannot be directly viewed in the web map but detailed canal features have been traced from many of them (licensing details given in the later Acknowledgements & References section). However, links are provided (where available) to websites where these maps can be directly viewed.

Historic maps

Contemporary Maps

The following maps were consulted both to check on the alignment of the historic maps and to see if they revealed any extra clues to the path of the canal:

Environment Agency LiDAR Elevation Data

(Note that “hillshade” (i.e. simulated shadows) renderings of this LiDAR data can be directly viewed within the web map as base layers. However, for tracing it was often more revealing to use a height colour-coded rendering to emphasize locations of notable changes in elevation).

Aerial Photography

Web Map Layer Descriptions

Details of each layer shown in the Layer Selector Pane:

Methodology Used to Re-align Map Features

The process of re-aligning (groups of) map features was a major challenge in accurately estimating the canal path. Although organisations like the National Library of Scotland and Bristol City Council have done a remarkable job in aligning their streaming digital scans of old maps to a modern coordinate system there are many sources of inaccuracies:

The re-alignment method used for most maps was to initially digitally trace all relevant map features and for LiDAR features to trace boundaries or centre-lines of any possibly relevant hollows. For the historic maps, it was then a case of using as reference points nearby well-defined features that still exist in current maps or aerial data to determine if (groups of) traced features should be shifted when generating a new “aligned” data set. For the reasons given above, these alignment shifts were often quite different at different places in a single map source:

For the earlier maps, the variability in accuracy was so great that it was necessary to first “warp” the whole map before tracing features by using point features still shown on contemporary maps as Ground Control Points (GCPs):

This map “warping” was achieved with the QGIS Georeferencer plugin, using the Thin Plate Spline (TPS) algorithm to “rubber sheet” the raster using multiple local polynomials to match the GCPs specified.

Summary of Results

Much of the routing of the canal (as built) is very clear and I believe that combining field undulations still visible in LiDAR with contemporary maps and (carefully re-aligned) historic maps has enabled the probable path to be mapped here to a significantly greater accuracy than previously done - to within a few metres in most places. Details of the mapping confidence for each segment of the canal can be viewed by clicking on each section of the canal in the web map. The resultant “popup” will explain the evidence for that segment from each data source and also the distance of any re-alignment shifting done on historic maps at that location.

Where there are very small gaps in evidence for the canal path, short links between known sections can be inferred with reasonable confidence. However, from the maps it is very unclear where the canal was/would be routed from the site of the bottom of the staircase of balance locks on the west side (section 94) to Elliots on the east side (section 103) - the earliest two maps (from 1808 and 1817) imply that this section was never built. However, features on the later maps suggest there might have been some canal workings here (sections 97-101), although much would have been lost by the building of the railway through this area not long after. If this was indeed the (intended) path of the canal, then the connecting path to the bottom of the balance locks (sections 95-96) is suggested based only on contour lines and hints from field boundaries. Where there are no further clues, the web map just shows dotted straight lines to indicate the possible logical links. Whichever route was intended to be taken here would require more than one additional balance lock as there is quite a large drop in height travelling east. The proposed route drawn in the 1796 Parliament Act is not helpful in this area as it diverges from the balance locks section by over 500 metres to the south-west.

The final (intended) eastern section of the branch line down into Frome also becomes progressively unclear. The earliest (1808 and 1817) maps imply the canal was only built as far as Whatcombe Farm (section 118), though an extension line (section 119) has been added based on following contours, enclosure boundaries and with reference to the proposed route in the 1796 Parliament Act.

The map does not attempt to combine features from the different maps other than the canal centre-line. However, it might be helpful to try to extract the most likely locations and outlines of balance locks, apparent canal basins or other canal widening.

Note that evidence presented in this web map is currently just from maps, LiDAR and aerial photography - additional confirmation/refutation of the marked “probable path” could be ascertained from physical evidence viewed by walking the route. Mapping of such additional evidence would ideally be done with either absolute locations measurement (e.g. with an accurate GPS measuring device) or relative measurements of distance from existing known features. Perhaps that is the next step for this project…

This Web Map: Open Data & Open Source code

The raw spatial data created for this web map is freely available as Open Data for re-use/re-work. It is contained in a single file in the OGC GeoPackage format which is readable by almost all GIS software. Data licensing:

All of the software and web source code used in producing this web map are Open Source.

Further details of the software/code/data are provided in the README page of the associated DS_Canal GitHub Repository.

Acknowledgements & References

Special thanks to Derrick Hunt of the Dorset & Somerset Canal Society for information, inspiration and various map images including earlier estimates of the canal path based on his extensive walking of the route. He is also the key author of the Dorset & Somerset Canal website (with web design by Liz Tuddenham) from which most of the locations in the “Notable Features” data layer in this web map are taken.

Source maps and aerial imagery used for this mapping project:

Other sources used:

Related further information on the Dorset & Somerset Canal (not directly used in this project):