London to Portsmouth canal

From Infogalactic: the planetary knowledge core
Jump to: navigation, search
London to Portsmouth Canal
288px
Stewarts Bridge on the Arundel to Portsmouth section of the canal
History
Date completed 1823
Date closed 1847
Geography
Start point London
End point Portsmouth
London to Portsmouth Canal
River Thames to London
Richmond Lock
3 locks - Teddington to Sunbury
Shepperton Lock
River Wey Navigation
4 locks plus stoplock
Basingstoke Canal
8 locks
Guildford
Wey and Godalming Navigations
2 locks
Wey and Arun Canal
To Godalming
7 locks
16 locks
Arun Navigation
6 locks
River Arun
Portsmouth and Arundel Canal
2 locks
Chichester Canal
2 locks
Chichester Harbour
Thorney Island
Hayling Island
Canal across Portsea Island
Portsmouth

The London to Portsmouth canal was a proposal for the construction of a secure inland canal route from the capital London to the headquarters of the Royal Navy at Portsmouth. It would have allowed craft to move between the two without having to venture into the English Channel and possibly encounter enemy ships. There is no naturally navigable route between the two cities, resulting in several schemes.

Proposed routes

River Wey

The River Wey in Surrey is a tributary of the River Thames. The source of the north branch is at Alton, Hampshire and of the south branch at Liphook. The branches join at Tilford. The river is navigable for around 20 miles (32 km) from Godalming to the Thames at Weybridge[1] to the south-west of London. It has in the past been proposed to dig a canal south, or to expand and make navigable the existing river.

Wey and Arun Canal

In 1810, the Earl of Egremont began to promote the idea of a canal to link the Rivers Wey and Arun,[1] separated by only 15 miles (24 km). Part of the justification for this canal through a very rural area, with few of the cargoes which had made other canals profitable, was to provide an inland route from London to the south coast of England, utilising these two rivers and the Portsmouth and Arundel Canal. This was considered an important consideration as England was at war with France and thus coastal shipping at risk of attack.[2]

Josias Jessop (son of the more well known William Jessop) was appointed consulting engineer and made an estimate of £72,217 for construction of the canal, later increased to £86,132 when part of the route was changed.

A survey was carried out in the same year by Francis and Netlam Giles for an alternative route, from the Croydon Canal to Newbridge, via Merstham, Three Bridges, Crawley and Horsham.

An Act of Parliament received the Royal Assent on 19 April 1813, entitled "An Act for making and maintaining a navigable Canal, to unite the Rivers Wey and Arun, in the counties of Surrey and Sussex". This authorised the construction of the canal from the Godalming Navigation (an extension of the River Wey) near Shalford, south of Guildford to the northern terminus of the Arun Navigation at Newbridge.[3] May Upton was appointed resident engineer in July, and work began. Construction was completed in 1816.[2]

The route of the canal was 18.5 miles (29.8 km) with 23 locks.[1]

By the time it was opened, however, the war with France was over and thus one of the key reasons for its construction was removed.[1] As a result it was never very prosperous, but did reasonably well, with a maximum of 23,000 tons carried in 1839. However, railway competition hit hard in 1865 with the opening of the Guildford and Horsham Railway, which was in direct competition with the canal. There were also engineering problems with few sources of water to tap into, compounded by porous soil on the summit level, which led to water shortages.[1]

An Act of Abandonment obtained in 1868 authorised closure. It was offered for sale in 1870, but officially abandoned in 1871,[4] with the land sold to many along its route.

Bibliography

  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.

References

  1. 1.0 1.1 1.2 1.3 1.4 Cumberlidge 2009, pp. 327-330
  2. 2.0 2.1 Ware 1989, p. 107
  3. Priestley 1831, pp. 673-674.
  4. Hadfield 1969, p. 135.

See also

Lua error in package.lua at line 80: module 'strict' not found.