World Library  
Flag as Inappropriate
Email this Article

Cuspate foreland

Article Id: WHEBN0009189674
Reproduction Date:

Title: Cuspate foreland  
Author: World Heritage Encyclopedia
Language: English
Subject: Coastal geography, List of landforms, Coastal management, Lydd Airport, Physical oceanography
Collection: Coastal and Oceanic Landforms, Coastal Geography, Geological Processes, Physical Oceanography
Publisher: World Heritage Encyclopedia
Publication
Date:
 

Cuspate foreland

A cuspate foreland, solidified by vegetation

Cuspate forelands, also known as cuspate barriers or nesses in Britain, are geographical features found on coastlines and lakeshores that are created primarily by longshore drift.[1] Formed by accretion and progradation of sand and shingle, they extend outwards from the shoreline in a triangular shape.[1] Some cuspate forelands may be stabilised by vegetation, while others may migrate down the shoreline. Because some cuspate forelands provide an important habitat for many flora and fauna, effective management is required to reduce the impacts from both human activities and physical factors such as climate change and sea level rise.

Contents

  • Formation 1
    • Formation in narrow straits or on open coastlines 1.1
    • Formation in the lee of an island 1.2
    • Formation along lakeshores 1.3
  • Features 2
  • Movement 3
  • Succession 4
  • Biological habitat 5
  • Impacts and management 6
  • See also 7
  • References 8
  • External links 9

Formation

Longshore drift is usually the main process in the formation of a cuspate foreland

The debate involving how cuspate forelands form is ongoing.[2] However, the most widely accepted process of formation involves long shore drift.[1] Where longshore drift occurs in opposite directions, two spits merge into a triangular protrusion along a coastline or lakeshore.[1] Their formation is also dependent on dominant and prevailing winds working in opposite directions.[1] Formation can also occur when waves are diffracted around a barrier.[3]

Cuspate forelands can form both along coastlines and along lakeshores. Those formed along coastlines can be in the lee of an offshore island, along a coastline that has no islands in the vicinity, or at a stream mouth where disposition occurs.[4]

Formation in narrow straits or on open coastlines

A cuspate foreland can form in a strait or along a coastline that has no islands or shoals in the area.[4] In this case, longshore drift as well as prevailing wind and waves bring sediment together from opposite directions.[2] If there is a large angle between the waves and the shoreline, the sediment converges, accumulates, and forms beach ridges.[2][5] Over time, a cuspate foreland forms as a result of continued accretion and progradation.[4] An example of this type of cuspate foreland is the one found at Dungeness along the southern coast of Britain.[6] This cuspate foreland has formed as a result of the merging of SW waves from the English Channel, and waves from the east from the Strait of Dover.[4] Another example is the cuspate foreland found between Awatere River and White Bluffs in Marlborough, New Zealand.[7] This foreland has ridges on the eastern and northern sides which face the prominent waves.[7]

In other circumstances, spits are formed when long shore drift moves beach material down the beach until the coastline makes an abrupt change in direction, leading to the beach material 'spilling over' the corner to create a protrusion. This normally occurs across a river mouth. In the case of a cuspate foreland, the prevailing wind and a powerful secondary wind in the opposite direction move shingle down the coastline from both directions to a place where the coastline changes, causing a foreland to develop.[8] The majority of cuspate forelands are formed over a coastline that juts out into the sea at enough of an angle to allow the drifting beach material to 'spill over' as a result of long shore drift in both directions.

Formation in the lee of an island

A cuspate foreland can form in the lee of an island. In this case, oncoming waves are diffracted around the island, protecting the coastline from the oncoming wave fronts.[1] Sediments brought along the shoreline via longshore drift are then able to settle and accumulate in the lee of the island where there is less wave energy.[1] This type of foreland has formed on the west shore of the North Island of New Zealand, in the lee of Kapiti Island.[9] Waves refract around Kapiti Island, forming an area of low wave energy where sediment from the Waikanae River is able to settle.[9] There is uncertainty whether the cuspate foreland has formed as a result of sediments coming from the north via longshore drift, or whether it has formed as a result of a complex cycle of sediments moving out to the continental shelf and then back again.[9]

Point Pelee cuspate foreland location

Formation along lakeshores

As well as forming along coastlines, cuspate forelands can also form along lake shores, although less is known about this type of cuspate foreland. This type of cuspate foreland includes Point Pelee along the shoreline of Lake Erie, and those found along the shoreline of Lake Victoria in Australia. There are two theories with regard to the formation of Point Pelee. Firstly, it is thought that Point Pelee has formed from depositional processes.[10] Alternatively, it is suggested that Point Pelee is a relic of a past feature that has eroded over time.[10] This gap in knowledge provides the opportunity for further research. It is likely that Point Pelee is migrating westwards since accretion is occurring on the western side, and erosion is occurring on the eastern side.[10] Lake Victoria in Australia also has a number of cuspate forelands. Point Scott is a cuspate foreland along this lakeshore that has formed from the gradual accumulation of sand and gravel.[11]

Features

Cuspate forelands can be separated into three distinct areas: the central nose or apex, and two marginal wings.[9] The apex usually has ridges that run parallel to the converging shorelines.[6] Cuspate forelands can extend up to 5 km from the shoreline, and an underwater shoal may extend much further, up to 15 km from the exposed apex.[2] Located between the mainland and the foreland are often lagoons or marshy areas.[6] In some areas, such as along the North Carolina coastline, a series of cuspate forelands may form at least 100 km apart.[5] In areas that have a large amount of shingle, such as the cuspate foreland at Dungeness, it is also common for a fresh water table to be present.[12]

Movement

Once formed, cuspate forelands can remain where they are and continue to develop as sediment accumulates, or alternatively they may migrate down the coast as one side of the foreland erodes and the other side accretes.[4] Cuspate Forelands that move are typical of those that are formed on open coastlines.[1] The direction of migration is often indicated by a series of successive beach ridges on the advancing side of the foreland where there is less wave energy.[1][4] The movement of cuspate forelands is commonly explained by longshore drift acting as the main process. However, there have been observed cases where two cuspate forelands on the same shoreline have migrated in opposite directions, showing that longshore drift does not always provide a sufficient explanation for their migration.[1]

If there is an offshore sandbank present, the position of the cuspate foreland is usually related to its position.[1] If there is a change in the position of the sandbank, the position of the cuspate foreland typically follows.[1] Not only does the sandbank act like an island since it causes waves to refract around it, but it also provides a source of sediment.[1] As sand erodes from the sandbank, it is pushed towards the coastline, contributing to the formation of the cuspate foreland as the sandbank migrates along the coast.[1] This often occurs in the opposite direction to longshore drift.[1]

In the case of a cuspate foreland that has formed close to an island, it is possible for it to extend right up to the island, forming a tombolo.[1] Depending on the physical conditions such as storms, the feature can alternate between a cuspate foreland and a tombolo.[1] Gabo Island in South Australia is an example of where this occurs.[1]

Succession

After the formation of the cuspate foreland into its distinctive triangular shape, it will start to be colonised by pioneer species that are hardy and tough enough to survive in the environment. These pioneer species secure the cuspate foreland and allow a greater amount of sediment to further secure it. Colonization and

  • Dungeness, Romney Marsh
  • Point Pelee National Park, Parks Canada
  • Dungeness National Nature Reserve, Romney Marsh Countryside Project
  • Cuspate Forelands at Lakes Entrance, Department of Primary Industries

External links

  1. ^ a b c d e f g h i j k l m n o p q r Craig-Smith, S. J., Cuspate Forelands. In: M. L. Schwartz, ed. 2005. Encyclopedia of Coastal Science. The Netherlands: Springer, pp. 354–355.
  2. ^ a b c d McNinch, J. E., and Luettich, R. A., 2000. Physical processes around a cuspate foreland: implications to the evolution and long-term maintenance of a cape-associated shoal. Continental Shelf Research. 20, pp. 2367–2389.
  3. ^ Woodroffe, C. D., 2002. Coasts: form, process and evolution. UK: Cambridge University Press.
  4. ^ a b c d e f Bird, E., 2008 Coastal geomorphology: an introduction. 2nd ed. England: John Wiley & Sons Ltd.
  5. ^ a b Ashton, A., et al., 2001. Formation of coastline features by large-scale instabilities induced by high-angle waves. Nature, 414(6861), pp. 296–300.
  6. ^ a b c Davis, R. A., and FitzGerald, D., 2004. Beaches and Coasts. Blackwell Publishing: Australia.
  7. ^ a b Pickrill, R. A., 1977. Coastal processes, beach morphology, and sediments along the north-east coast of the South Island, New Zealand. New Zealand Journal of Geology and Geophysics. 20(1). pp. 1–15.
  8. ^ Puget Sound Shorelines: Shore Forms
  9. ^ a b c d Wright, L. W., 1988. The sand country of the ‘Golden Coast’, Wellington, New Zealand. New Zealand Geographer. 44(1). pp. 28–31.
  10. ^ a b c d e f g h i j Trenhaile, A. S., 2000. Point Pelee: a large cuspate foreland on Lake Erie. Canadian Geographer, 44(2), pp. 191–195.
  11. ^ a b c Department of Primary Industries Point Scott – Raymond Island, Department of Primary Industries, 2008. Accessed 31 March 2011.
  12. ^ a b c d e f g h i j k l m n o Randall, R. E., 2004. Management of coastal vegetated shingle in the United Kingdom. Journal of Coastal Conservation, 10, pp. 159–168.
  13. ^ Parks Canada, Point Pelee National Park of Canada, Parks Canada, 2010. Accessed 8 April 2011.
return p

end

', table.concat(classes, ' '), s )
%s
function p._hatnote(s, options) checkType('_hatnote', 1, s, 'string') checkType('_hatnote', 2, options, 'table', true) local classes = {'hatnote'} local extraclasses = options.extraclasses local selfref = options.selfref if type(extraclasses) == 'string' then classes[#classes + 1] = extraclasses end if selfref then classes[#classes + 1] = 'selfref' end return string.format( '

function p.hatnote(frame) local args = getArgs(frame) local s = args[1] local options = {} if not s then return p.makeWikitextError( 'no text specified', 'Template:Hatnote#Errors', args.category ) end options.extraclasses = args.extraclasses options.selfref = args.selfref return p._hatnote(s, options) end


-- Hatnote -- -- Produces standard hatnote text. Implements the template.


function p._formatLink(link, display) -- Find whether we need to use the colon trick or not. We need to use the -- colon trick for categories and files, as otherwise category links -- categorise the page and file links display the file. checkType('_formatLink', 1, link, 'string') checkType('_formatLink', 2, display, 'string', true) link = removeInitialColon(link) local namespace = p.findNamespaceId(link, false) local colon if namespace == 6 or namespace == 14 then colon = ':' else colon = end -- Find whether a faux display value has been added with the | magic -- word. if not display then local prePipe, postPipe = link:match('^(.-)|(.*)$') link = prePipe or link display = postPipe end -- Find the display value. if not display then local page, section = link:match('^(.-)#(.*)$') if page then display = page .. ' § ' .. section end end -- Assemble the link. if display then return string.format('%s', colon, link, display) else return string.format('%s%s', colon, link) end end

function p.formatLink(frame) local args = getArgs(frame) local link = args[1] local display = args[2] if not link then return p.makeWikitextError( 'no link specified', 'Template:Format hatnote link#Errors', args.category ) end return p._formatLink(link, display) end


-- Format link -- -- Makes a wikilink from the given link and display values. Links are escaped -- with colons if necessary, and links to sections are detected and displayed -- with " § " as a separator rather than the standard MediaWiki "#". Used in -- the template.


function p.makeWikitextError(msg, helpLink, addTrackingCategory) -- Formats an error message to be returned to wikitext. If -- addTrackingCategory is not false after being returned from -- Module:Yesno, and if we are not on a talk page, a tracking category -- is added. checkType('makeWikitextError', 1, msg, 'string') checkType('makeWikitextError', 2, helpLink, 'string', true) yesno = require('Module:Yesno') local title = mw.title.getCurrentTitle() -- Make the help link text. local helpText if helpLink then helpText = ' (help)' else helpText = end -- Make the category text. local category if not title.isTalkPage and yesno(addTrackingCategory) ~= false then category = 'Hatnote templates with errors' category = string.format( '%s:%s', mw.site.namespaces[14].name, category ) else category = end return string.format( '%s', msg, helpText, category ) end

function p.formatPageTables(...) -- Takes a list of page/display tables and returns it as a list of -- formatted links. Nil values are not allowed. local pages = {...} local links = {} for i, t in ipairs(pages) do checkType('formatPageTables', i, t, 'table') local link = t[1] local display = t[2] links[i] = p._formatLink(link, display) end return links end

function p.formatPages(...) -- Formats a list of pages using formatLink and returns it as an array. Nil -- values are not allowed. local pages = {...} local ret = {} for i, page in ipairs(pages) do ret[i] = p._formatLink(page) end return ret end

function p.findNamespaceId(link, removeColon) -- Finds the namespace id (namespace number) of a link or a pagename. This -- function will not work if the link is enclosed in double brackets. Colons -- are trimmed from the start of the link by default. To skip colon -- trimming, set the removeColon parameter to true. checkType('findNamespaceId', 1, link, 'string') checkType('findNamespaceId', 2, removeColon, 'boolean', true) if removeColon ~= false then link = removeInitialColon(link) end local namespace = link:match('^(.-):') if namespace then local nsTable = mw.site.namespaces[namespace] if nsTable then return nsTable.id end end return 0 end

local function removeInitialColon(s) -- Removes the initial colon from a string, if present. return s:match('^:?(.*)') end

local function getArgs(frame) -- Fetches the arguments from the parent frame. Whitespace is trimmed and -- blanks are removed. mArguments = require('Module:Arguments') return mArguments.getArgs(frame, {parentOnly = true}) end


-- Helper functions


local p = {}

local libraryUtil = require('libraryUtil') local checkType = libraryUtil.checkType local mArguments -- lazily initialise Module:Arguments local yesno -- lazily initialise Module:Yesno


return p-------------------------------------------------------------------------------- -- Module:Hatnote -- -- -- -- This module produces hatnote links and links to related articles. It -- -- implements the and meta-templates and includes -- -- helper functions for other Lua hatnote modules. --

end

', table.concat(classes, ' '), s )
%s
function p._hatnote(s, options) checkType('_hatnote', 1, s, 'string') checkType('_hatnote', 2, options, 'table', true) local classes = {'hatnote'} local extraclasses = options.extraclasses local selfref = options.selfref if type(extraclasses) == 'string' then classes[#classes + 1] = extraclasses end if selfref then classes[#classes + 1] = 'selfref' end return string.format( '

function p.hatnote(frame) local args = getArgs(frame) local s = args[1] local options = {} if not s then return p.makeWikitextError( 'no text specified', 'Template:Hatnote#Errors', args.category ) end options.extraclasses = args.extraclasses options.selfref = args.selfref return p._hatnote(s, options) end


-- Hatnote -- -- Produces standard hatnote text. Implements the template.


function p._formatLink(link, display) -- Find whether we need to use the colon trick or not. We need to use the -- colon trick for categories and files, as otherwise category links -- categorise the page and file links display the file. checkType('_formatLink', 1, link, 'string') checkType('_formatLink', 2, display, 'string', true) link = removeInitialColon(link) local namespace = p.findNamespaceId(link, false) local colon if namespace == 6 or namespace == 14 then colon = ':' else colon = end -- Find whether a faux display value has been added with the | magic -- word. if not display then local prePipe, postPipe = link:match('^(.-)|(.*)$') link = prePipe or link display = postPipe end -- Find the display value. if not display then local page, section = link:match('^(.-)#(.*)$') if page then display = page .. ' § ' .. section end end -- Assemble the link. if display then return string.format('%s', colon, link, display) else return string.format('%s%s', colon, link) end end

function p.formatLink(frame) local args = getArgs(frame) local link = args[1] local display = args[2] if not link then return p.makeWikitextError( 'no link specified', 'Template:Format hatnote link#Errors', args.category ) end return p._formatLink(link, display) end


-- Format link -- -- Makes a wikilink from the given link and display values. Links are escaped -- with colons if necessary, and links to sections are detected and displayed -- with " § " as a separator rather than the standard MediaWiki "#". Used in -- the template.


function p.makeWikitextError(msg, helpLink, addTrackingCategory) -- Formats an error message to be returned to wikitext. If -- addTrackingCategory is not false after being returned from -- Module:Yesno, and if we are not on a talk page, a tracking category -- is added. checkType('makeWikitextError', 1, msg, 'string') checkType('makeWikitextError', 2, helpLink, 'string', true) yesno = require('Module:Yesno') local title = mw.title.getCurrentTitle() -- Make the help link text. local helpText if helpLink then helpText = ' (help)' else helpText = end -- Make the category text. local category if not title.isTalkPage and yesno(addTrackingCategory) ~= false then category = 'Hatnote templates with errors' category = string.format( '%s:%s', mw.site.namespaces[14].name, category ) else category = end return string.format( '%s', msg, helpText, category ) end

function p.formatPageTables(...) -- Takes a list of page/display tables and returns it as a list of -- formatted links. Nil values are not allowed. local pages = {...} local links = {} for i, t in ipairs(pages) do checkType('formatPageTables', i, t, 'table') local link = t[1] local display = t[2] links[i] = p._formatLink(link, display) end return links end

function p.formatPages(...) -- Formats a list of pages using formatLink and returns it as an array. Nil -- values are not allowed. local pages = {...} local ret = {} for i, page in ipairs(pages) do ret[i] = p._formatLink(page) end return ret end

function p.findNamespaceId(link, removeColon) -- Finds the namespace id (namespace number) of a link or a pagename. This -- function will not work if the link is enclosed in double brackets. Colons -- are trimmed from the start of the link by default. To skip colon -- trimming, set the removeColon parameter to true. checkType('findNamespaceId', 1, link, 'string') checkType('findNamespaceId', 2, removeColon, 'boolean', true) if removeColon ~= false then link = removeInitialColon(link) end local namespace = link:match('^(.-):') if namespace then local nsTable = mw.site.namespaces[namespace] if nsTable then return nsTable.id end end return 0 end

local function removeInitialColon(s) -- Removes the initial colon from a string, if present. return s:match('^:?(.*)') end

local function getArgs(frame) -- Fetches the arguments from the parent frame. Whitespace is trimmed and -- blanks are removed. mArguments = require('Module:Arguments') return mArguments.getArgs(frame, {parentOnly = true}) end


-- Helper functions


local p = {}

local libraryUtil = require('libraryUtil') local checkType = libraryUtil.checkType local mArguments -- lazily initialise Module:Arguments local yesno -- lazily initialise Module:Yesno


-- Module:Hatnote -- -- -- -- This module produces hatnote links and links to related articles. It -- -- implements the and meta-templates and includes -- -- helper functions for other Lua hatnote modules. --


References

See also

The management of coastlines needs to take into account the natural processes that occur on cuspate forelands since many provide a habitat for birds. Alternative ways of managing coastal erosion is needed, such as the use of ‘soft’ defences instead of high impact defences such as sea walls.[12] Some cuspate forelands naturally do not contain any vegetation due to a high level of disturbance from physical factors such as wave action.[12] However, with the frequency of storms arising from climate change, the effect on forelands and their associated vegetation needs to be effectively managed.

When there is an aquifer present under a cuspate foreland, regulation of water removal is required. At Dungeness, water restrictions have been put in place to maintain the aquifer level.[12]

At Point Pelee, approximately 1,900 hectares of former agricultural land on the cuspate foreland is now under water as a result of wind erosion and compaction of organic soils on the foreland.[10] This foreland is particularly vulnerable to erosion when high lake levels are combined with spring and autumn cyclonic activity.[10] Erosion can also occur as spring storms cause ice to scour the lake bottom at the edge of the foreland.[10] Because there is uncertainty about its formation, there is uncertainty with regard to management, although Parks Canada realises the importance of including Point Pelee National Park in management plans.[10][13]

There are different management issues with regard to cuspate forelands depending on their formation. If a cuspate foreland has formed from deposition, it may be vulnerable if human interference alters the transport of sediments from the shoreline.[10] However, if the cuspate foreland is a relic of a past feature that has eroded, human interference with longshore sediment movement will not have a significant impact on the cuspate foreland.[10] For a cuspate foreland to be maintained, the input of sediment must be greater than output of sediment.[10] Activities such as coastal development or engineering must be regulated for sediment to continue moving towards the foreland where it can be deposited.[11] Development along cuspate forelands is risky due to erosion and the vulnerability to storms and sea level rise.[11][12] As sea levels rise, cuspate forelands are likely to be at risk as they could move inland.[12]

Impacts and management

Cuspate forelands provide a habitat for various flora and fauna. If a foreland is relatively stable and experiences low wave impact, it may be possible for vegetation to grow.[12] In the United Kingdom, 11 taxa of invertebrates are found on shingle habitats.[12] Shingle beaches also provide a habitat for birds to breed, nest, and rest en route while migrating.[12]

Biological habitat

[12] Vegetation above the high tide line is common on cuspate forelands that are stable and composed of shingle.[12] Plants also cause the soil to develop and water retention to increase, therefore providing a habitat where more plants can grow.[12]

This article was sourced from Creative Commons Attribution-ShareAlike License; additional terms may apply. World Heritage Encyclopedia content is assembled from numerous content providers, Open Access Publishing, and in compliance with The Fair Access to Science and Technology Research Act (FASTR), Wikimedia Foundation, Inc., Public Library of Science, The Encyclopedia of Life, Open Book Publishers (OBP), PubMed, U.S. National Library of Medicine, National Center for Biotechnology Information, U.S. National Library of Medicine, National Institutes of Health (NIH), U.S. Department of Health & Human Services, and USA.gov, which sources content from all federal, state, local, tribal, and territorial government publication portals (.gov, .mil, .edu). Funding for USA.gov and content contributors is made possible from the U.S. Congress, E-Government Act of 2002.
 
Crowd sourced content that is contributed to World Heritage Encyclopedia is peer reviewed and edited by our editorial staff to ensure quality scholarly research articles.
 
By using this site, you agree to the Terms of Use and Privacy Policy. World Heritage Encyclopedia™ is a registered trademark of the World Public Library Association, a non-profit organization.
 


Copyright © World Library Foundation. All rights reserved. eBooks from Project Gutenberg are sponsored by the World Library Foundation,
a 501c(4) Member's Support Non-Profit Organization, and is NOT affiliated with any governmental agency or department.