Talk:Mount Washington

Untitled

This removed text, from the ext links,

, the only railway in the world built entirely on trestles, 3.1 miles (5.2 km).

is either incoherant or just wrong. The tracks are laid on the ground at the summit, at the crossing with the Gulfside Trail, and apparently all the way between those two points; also at the Base Station and presumably large stretches between there and Gulfside. --Jerzy(t) 19:36, 2005 Jan 18 (UTC)

---

Modified avalanche text

and which have killed more than 130 people since 1849, largely in Tuckerman.

This number is more than all of the recorded deaths from all causes in all of the Presidentials, including falls, heart attacks, plane crashes, and railroad accidents. There were 2 Tucks avalanche deaths in 1954, 1 in 1956, and 2 in 2002, for a total of 5 , unless you add the one in 1996 on Lion's Head (which of course is 5 too many). Ref Howe, Nicholas(2000). Not Without Peril pp.299-304. and 11/29/2002 news at timefortuckerman.com. If we really need a fatality number, maybe it should cover all of Mt Washington, but maybe an external link to a compendium is sufficient. (updated talk) Lupinelawyer 01:45, 20 Jan 2005 (UTC)

Record precipitation?

Hi Ken Gallager, the source for Mount Mitchell's rainfall is: Livingston, Ian (2019-12-05). "In 2018, 94 inches of rain deluged Sperryville, Va., setting a state record". Washington Post. ISSN 0190-8286. Retrieved 2019-12-08.—which was for 139.94 inches of rain in 2018. This is clearly higher than the "record high for a calendar year anywhere in the U.S. east of the Cascade Range of 130.14 in (3,305.6 mm)" cited for Mt. Washington. It's probably better to leave off the "anywhere in the U.S. east of the Cascade Range" bit, because it appears to no longer be true and may be WP:OR, since it is apparently the conclusion of an editor looking at the data in the source, rather than reporting what another author wrote. Cheers, HopsonRoad (talk) 14:01, 29 June 2020 (UTC)

Great, thanks for the source. I'll add the ref to the article. Were you the editor who put up the statement? --Ken Gallager (talk) 15:38, 29 June 2020 (UTC)

No, that must have been someone else. I recommend simply deleting "anywhere in the U.S. east of the Cascade Range" and leaving it at that. HopsonRoad (talk) 15:41, 29 June 2020 (UTC)

Okay, thanks. --Ken Gallager (talk) 15:42, 29 June 2020 (UTC)

References

Requested move 29 June 2020

The following is a closed discussion of a requested move. Please do not modify it. Subsequent comments should be made in a new section on the talk page. Editors desiring to contest the closing decision should consider a move review after discussing it on the closer's talk page. No further edits should be made to this discussion.

The result of the move request was: moved -- JHunterJ (talk) 11:29, 6 July 2020 (UTC)

---

• Mount Washington (New Hampshire) → Mount Washington
• Mount Washington → Mount Washington (disambiguation)

– The mountain in New Hampshire is far and away the WP:PRIMARYTOPIC for "Mount Washington". This page draws more than 600 views per day, while other pages with the same name have a fraction of the page views [1]. A simple Google search finds numerous results for the NH mountain and scarce hits for the others. The fact that there are multiple Mount Washingtons in the world does not prevent this one from being the most prominent (pun intended). Calidum 16:50, 29 June 2020 (UTC)

• Support Clearly by far the most significant bearer of the name and the one assumed, when mentioned at large. HopsonRoad (talk) 17:15, 29 June 2020 (UTC)
• Support per nom. Primarytopic by usage and long-term significance. Helpful move for our readers and editors. Dohn joe (talk) 17:25, 29 June 2020 (UTC)
• Support per nom.--Ortizesp (talk) 17:41, 29 June 2020 (UTC)
• Support. I agree that this particular topic is primary. Shhhnotsoloud (talk) 11:59, 1 July 2020 (UTC)
• Oppose. As a frequent Oregon mountain trekker, the gnarly weathered mountain in New Hampshire (which I thought was in Vermont) is not the first Mount Washington I think of, nor do many in my region. By going to the disambiguation version of this page, one can be schooled in the amazing number of choices—which one should not underestimate the value of. (Once in Pittsburgh, I was told "just up the hill" is Mount Washington. I spent over an hour trying to find it. Turns out I had walked over it several times during the search.) —EncMstr (talk) 15:14, 1 July 2020 (UTC)

Just a reminder that a primary topic is not what first comes to your mind. In fact the two items I've items cited, page views and web searches, are recommended as ways to determine a primary topic. Calidum 15:37, 1 July 2020 (UTC)

---

The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

Infobox help

The infobox shows an error, regarding language: Native name Error: Error {{native name}}: an IETF language tag as parameter {{{1}}} is required (help): an IETF language tag as parameter {{{1}}} is required (help). The aboriginal language spoken was Western Abenaki, ISO 639-3 code: "abe". Anything that can be done to undo the error would be welcome!

HopsonRoad (talk) 18:53, 3 January 2022 (UTC)

It looks like a widespread issue. I haven't been able to fully parse what's going on, but there's a discussion here, which I found by looking up the template in the error: Template:Native_name. If you need more help, ask again. – Anon423 (talk) 19:13, 3 January 2022 (UTC)

(edit conflict)

According to d:Help:Wikimedia language codes/lists/all the Wikimedia software doesn't have an IETF code corresponding to the ISO tag 'abe', which explains why the error occurs. What should be done about it is another matter. Looking at the documentation and source code of {{Infobox mountain}} I see you can supply a separate parameter native_name_lang= which does accept the ISO tag - I tried it - so like this:

| native_name = Agiocochook
| native_name_lang = abe

Hope this helps. — jmcgnh^{(talk) (contribs)} 19:29, 3 January 2022 (UTC)

Pinging @HopsonRoad:. Normally, we expect to see the {{help me}} template used on your own talk page, where a ping would be superfluous. — jmcgnh^{(talk) (contribs)} 19:35, 3 January 2022 (UTC)

IETF language tags are assembled from a primary subtag (the ISO 639-1, -2, -3 language code) and optionally region, script, and variant subtags. |native_name_lang=, despite what the {{infobox mountain}} documentation says, is not constrained to accept only ISO 639-2 language codes. It is not clear to me why the documentation specifies ISO 639-2.

The goal of the discussion at Wikipedia talk:WikiProject Infoboxes § native name parameters is to cleanup the mess that is |native_name= and |native_name_lang=. Questions about that should be asked there.

—Trappist the monk (talk) 20:25, 3 January 2022 (UTC)

6,100 ft prominence...

The key col ridgeline prominence goes all the way to the Champlain Canal on the New York border over 100 miles away. The real prominence is more like 5,200 ft from the circa 1,000 ft elevation valley on the west side. B137 (talk) 08:38, 2 April 2023 (UTC)