Ganesh NW (Ganesh II/III)

Ganesh NW (or Ganesh II, or sometimes Ganesh III) is a peak of the Ganesh Himal, which is a subrange of the Himalayan range.

Ganesh NW
Ganesh II
Ganesh Himal massif. Ganesh NW is the third peak from the right
Highest point
Elevation7,118 m (23,353 ft)
Prominence1,198 m (3,930 ft)
Coordinates28°22′45″N 85°03′24″E 
Geography
Ganesh NW
Location in Nepal
LocationNepal
Parent rangeGanesh Himal, Himalaya
Climbing
First ascent16 October 1981
Easiest routerock/snow/ice climb

Ganesh NW, and the entire Ganesh Himal, lie between the Budhi Gandaki and Trisuli Gandaki valleys, about 70 km northwest of Kathmandu. Ganesh NW lies about seven km west of Yangra (Ganesh I).

Nomenclature for this peak is ambiguous and confusing, and varies between sources. Many sources refer to this peak as Ganesh III, and also as Salasungo. However Salasungo more properly refers to a different peak in the Ganesh Himal, Ganesh SE or Ganesh III. The name Ganesh II is used on the Finnmap, the most recent authoritative source.

Notable features

Although low in elevation among the major mountains of Nepal, Ganesh NW is exceptional in its steep rise above local terrain. For example, it rises 5800 m from the Burhi Gandaki in a horizontal distance of about 16 km.

Climbing history

There were six unsuccessful attempts on this peak, including attempts in 1953 and 1954, before two simultaneous first ascents in October 1981. The two successful teams were a German-Sherpa team (Hermann Warth, Ang Chappal, Nga Temba) on the North Ridge, and a Japanese-Sherpa group (N. Kuwahara, J. Nakamura, N. Hase, Tendi Sherpa, Kirke Sherpa) on the Northeast Spur. The two groups combined at 6,300 metres and finished on the North Face.

There have been two additional unsuccessful attempts since 1981, in 1988 and 1992, but no more ascents of the peak.[1]

Sources
  • H. Adams Carter, "Classification of the Himalaya," American Alpine Journal 1985.
  • Jill Neate, High Asia: An Illustrated History of the 7000 Metre Peaks, ISBN 0-89886-238-8
  • DEM files for the Himalaya (Corrected versions of SRTM data)
gollark: Disregarding its responses, you'd be able to probably switch skynet to use EXT's backend with no code changes.
gollark: The protocols *are* 90% compatible, though, honestly.
gollark: ... as if.
gollark: Skynet's `send` and `receive` functions handle the connection and listening stuff automatically, yes.
gollark: <@94122472290394112> EXT vs Skynet:Skynet:* wildcard channel - allows listening to all system messages* API may be nicer to use, as you don't *need* to call skynet.listen anywhere - you do need to call EXT.run somewhere, in parallel or something* Skynet's backend (not the CC side) assigns each connected socket an ID, and tells you which IDs recevied messages. This is not much use.EXT:* messages only readable by people on same channel or server operator* somewhat more complete API - allows closing channels - Skynet can do this but the CC side doesn't handle it

References
  1. "Himalayan Index". Retrieved 2006-09-20.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.