Wikipedia talk:WikiProject Mountains Information & Wikipedia talk:WikiProject Mountains Links at HealthHaven.com

[edit] Article alerts

This is a notice to let you know about Article alerts, a fully-automated subscription-based news delivery system designed to notify WikiProjects and Taskforces when articles are entering Articles for deletion, Requests for comment, Peer review and other workflows (full list). The reports are updated on a daily basis, and provide brief summaries of what happened, with relevant links to discussion or results when possible. A certain degree of customization is available; WikiProjects and Taskforces can choose which workflows to include, have individual reports generated for each workflow, have deletion discussion transcluded on the reports, and so on. An example of a customized report can be found here.

If you are already subscribed to Article Alerts, it is now easier to report bugs and request new features. We are also in the process of implementing a "news system", which would let projects know about ongoing discussions on a wikipedia-wide level, and other things of interest. The developers also note that some subscribing WikiProjects and Taskforces use the display=none parameter, but forget to give a link to their alert page. Your alert page should be located at "Wikipedia:PROJECT-OR-TASKFORCE-HOMEPAGE/Article alerts". Questions and feedback should be left at Wikipedia talk:Article alerts.

Message sent by User:Addbot to all active wiki projects per request, Comments on the message and bot are welcome here.

Thanks. — Headbomb {^ταλκ_{κοντριβς} – WP Physics} 09:26, 15 March, 2009 (UTC)

I plan on enabling this for our project within a week unless there are any objections. RedWolf (talk) 20:34, 20 December 2009 (UTC)

Done I did this back in March. Check out Wikipedia:WikiProject Mountains/Article alerts. —hike395 (talk) 05:03, 21 December 2009 (UTC)

[edit] Memorial effort

As many of you might have seen in the Wikipedia Signpost, User:Fg2, who had been a significant contributor to much of our content related to Japan, has recently died. Some of us have decided to try to work to improve an article relative to his interests as a memorial to him, and the article chosen is Mount Fuji. This is also an article considered of "Top" importance by your project. I and I believe the rest of the people involved in the effort to improve this article in honor of Fg2 would more than welcome any input from members of this project. Thank you for your attention. John Carter (talk) 15:00, 13 October 2009 (UTC)

[edit] {{Canadian Rockies}}

Please see Template talk:Canadian Rockies about sectioning the mountain range section by major grouping; I'm a klutz with messing with template design - please have a looksee.Skookum1 (talk) 03:33, 29 October 2009 (UTC)

[edit] Boundary Peaks of the AK-BC and BC-AB borders

Please see Category_talk:Boundary_Ranges in re related categories and potential subcategories and their parents, and suggesting List of Boundary Peaks of the Alaska-British Columbia border or List of Boundary Peaks of the Alaska Boundary Settlement (or whatever title of t hat kind; the Hay-Herbert Treaty seems less descriptive for the context, which is geographic in nature); and related subcats Note the use of full caps on Boundary Peaks, these are official names/designations not simply peaks the border touches it; they are the border, quite literally, although there are some Boundary Monuments (also full caps) also at certain points, and designated latitude-longitude "corner turns", though the peaks are the dominant defining points of the boundary.Skookum1 (talk) 22:34, 2 November 2009 (UTC)

Took me a while but I made List of Boundary Peaks of the Alaska-British Columbia border and I think I've got them all; if someone could compare the GNIS search for "Boundary Peak", limited to Alaska to exclude those in NV and NM etc, that'd be great. Most do not have CGNDB cite - ony the fully named ones do - and not all are in BCGNIS, though I can't do those cites until BCGNIS is workign again (it hasn't been these last couple of days). I'm tempted to lump all the BCGNIS, GNIS and CGNDB columns into one just called "cites"; the "other" column is for any bivouac or peakbagger citations etc.; "range/region currently shows the US counties delivered up by GNIS but it should be for the range/environs/park. There are duplicate entries as GNIS has different ID nos. for each name, sometimes different coordinates; this might screw up displays in GeoGroupTemplate and I'm wondering about doing it in three chunks - Stewart to Skagway, Skagway to the Alsek, and then the St. Elias bunch, so that GeoGroup will "hone" in one the areas. As you can see form the redlinks there are articles needed and "legacy" mentions for such as Mount Quincy Adams on the [John Quincy Adams]] page to be made etc. The List of peaks on the British Columbia-Alberta border, with or without passes included, is gonna be harder to do as they're not named Boundary peaks, which is the case here; it'll be done from exploring maps, I guess.....comments column currently only is AK-BC/YT but could include bits of info on the namesakes of the named peaks.....some of the number-only peaks are very high, e.g. BP 187, near St. Elias, is over 13000'.....oh, yeah, I don't know how to use the {{conv}} template so if someone could take the time to add it to all the elevation fields and amend the column heading appropriately; the feet-elevation is all that GNIS gives on its table, though there are metric measures on the individual pages.....also note because of the YT having Boundary Peaks of this kind, a better title is needed - List of Boundary Peaks of the Alaska-British Columbia/Yukon border maybe or List of Boundary Peaks of the Alaska Boundary Settlement or something of that kind.... suggestions?Skookum1 (talk) 17:08, 4 November 2009 (UTC)

[edit] External Links

Excellent new resource for backcountry skiers. Not sure why an external link that I added to Front Range was reverted. http://www.skiingthebackcountry.com/ski_guide/UNITED-STATES/COLORADO/FRONT-RANGE. This link meets all wikipedia guidelines and would be an excellent resource for mountaineers. The specific route info for backcountry skiers is something that is not documented in an organized fashion anywhere else online. Please discuss this link and provide real feedback for or against including it in the external links section of the Front Range article. The community conclusions could impact similar links on other articles. (talk) 05:51, 4 November 2009 (UTC)]]

[edit] New list of BC-AB border peaks

I started List of peaks on the British Columbia-Alberta border of today, but only a very small start, it will eventually be huge; see Talk:List of peaks on the British Columbia-Alberta border for to-dos and instructions on how to expand it....too big a job for one person.....Skookum1 (talk) 17:40, 8 November 2009 (UTC)

Further to that, a look at it shows there are numerous peaks and passes on the divide/BC-AB border that could use articles; all the passes certainly, and I'd think most of the peaks; a List of mountain passes on the British Columbia-Alberta border also comes to mind; maybe that would better be List of mountain passes on the Great Divide of North America or the like might be a better solution, given the evident overlap.Skookum1 (talk) 18:31, 8 November 2009 (UTC)

And note this entry in BCGNIS}, for "The Trench" (trench) in BCGNIS, which I gather is a pass, or cleft; it's in the Kootenay Icefield area.Skookum1 (talk) 18:33, 8 November 2009 (UTC)

[edit] Mount Ulysses

I just made this as a result of adding Grand Pacific Pass so as to add it to the lede of List of Boundary Peaks of the Alaska-British Columbia/Yukon border (it's on the boundary though not SFAIK treaty-specified in the same way the peaks are, and the summits of the Chilkat, Chilkoot and White Passes). There's peaks in that area like Mount Root which are bare stubs or which are redlinks (as you'll find on that list), but the significance of Grand Pacific Pass in topographical terms is it's the prominence col for Mount Ulysses, which is the highest thing north of Lake Williston - within BC; not sure if Keele et al are higher. Anyway Ulysses is a very significant peak; pictures of it are few, especially public domain though there may be some aerials out there; the core part of those ranges is pretty unusual, I've "done the topos" in detail, be nice for someone to come up with some pics. Real remote country, not many people go in there, not easy to photography like Garibaldi or Manning or BAnff Parks, by comparison....anyway seemed like a significant enough peak to warrant gussy-ing up WP:Mountains-style, if someone would care to bother....(pls, though, use a terrain map or sat map for the location map rather than those icky regional district location maps....and lots of peaks on the Boundary Peaks page and its BC-Alberta sibling (in its see also); and I gather the continental divide also applies as boundary between YT and NWT....not sure many of those peaks are named, don't think so....Skookum1 (talk) 04:35, 10 November 2009 (UTC)

I have added the infobox and location map. For such a significant peak, a photo would certainly be nice — I have never been in that area so can't help with that. RedWolf (talk) 20:54, 20 December 2009 (UTC)

[edit] Why jurisdictional maps don't work for geographic items

In the course of finishing up the List of peaks on the British Columbia-Alberta border, I followed a lot of the resulting bluelinks, some of them I added a "(Canada)" dab too, others existed but many were written Alberta-only; I amended their text, but those that have maps have Alberta-only maps; this is inappropriate for peaks also in BC. What's needed is a pushpin-friendly terrain map of the Rockies, either Googlemap-satellite or one of the other landform series like that used on e.g. Bendor Range (which isn't pushpin-friendly, but the Googlemaps I think are...). Geographic maps should be used for geographic features; it really doesn't matter which BC regional district or Alberta improvement district they're in...it does matter where in the landscape they are....see Talk:Trapper Peak (Canada).Skookum1 (talk) 19:23, 12 November 2009 (UTC)

[edit] Hooker and Brown

I came across this while checking out Mount Hooker, which is one of the BC-Alberta border peaks; it's not about the real Mount Hooker so I separated their dabs on that page, but I'm also not sure how to categorize this or further "treat" it....anyone wanna take it on?Skookum1 (talk) 19:43, 12 November 2009 (UTC)

[edit] {{Infobox mountain}} code updates

Hey folks,

There's been a lot of work over several months to overhaul the codebase of {{infobox mountain}} to make it easier to maintain and to make it fit better with other infobox templates. At present, the code at {{infobox mountain/sandbox}} looks like it's good to go: a comparison between the old and new layouts is available at the test cases page. In addition to significant code cleanup, several bugs look to have been fixed compared to the deployed code. Thoughts? Chris Cunningham (not at work) - talk 14:06, 4 December 2009 (UTC)

I don't have any comments on the code, but just on the aesthetics:

I like the brown left column of the original infobox mountain: it immediately identifies the article being about a mountain (which is not always obvious from the picture, for the less prominent mountains). Can we restore a light brown left column? I realize that geobox does not have this, but I really like that feature.
It seems that the spacing between lines have increased. This is good for readability, but bad for the room it takes up. I wonder if we should use a little less space around the text? perhaps even 1px less?

—hike395 (talk) 17:23, 4 December 2009 (UTC)

"Brown" could immediately identify all sorts of things, from furniture to sausages. Mountains are not, to my knowledge, synonymous with the colour brown. Indeed, rather a lot of the Earth is brown. It's unnecessary decoration. Leaving it in the title is simply a concession to the common use of a colour bar in infobox headers. As for the spacing, it has increased slightly, but only to the same spacing as in all other {{infobox}}es. It can easily be decreased if really necessary, but is it really necessary to override this here as compared to a large majority of the rest of the encyclopedia's infobox templates? Chris Cunningham (not at work) - talk 01:45, 5 December 2009 (UTC)

I think you misunderstood my comment. I'm saying that existing mountain infoboxes are brown on thousands of pages, and that particular color immediately identifies pages associated with this WikiProject. If, 7 years ago, we had chosen blue, I would now be arguing for keeping that blue. It has nothing to do with actual colors of mountains (or sausages).

As for the spacing: you wanted feedback --- I gave it. I think that a slight compression of the spacing will make the infobox more compatible with existing mountain infoboxes. —hike395 (talk) 04:14, 5 December 2009 (UTC)

Can I just clarify that this is a replacement for the current code. It isn't going to be deployed alongside it. Right now, the mountain infobox looks out-of-place compared to other geography infoboxes, which it is deployed alongside. Chris Cunningham (not at work) - talk 08:50, 5 December 2009 (UTC)

I'm curious what the other WikiProject participants think: there are several devoted infobox-adders in the project, and I'd like to hear from them. —hike395 (talk) 07:26, 6 December 2009 (UTC)

I can understand the need to standardize infoboxes and try to use a common code base. This infobox has seen a lot of changes over the years and is now used in nearly 8,000 articles. There was an attempt a while back to get the project to convert to using the Geobox template but due to a number of major issues that remained unresolved, we decided not to switch to using Geobox for individual mountains. Geobox is however recommended for mountain ranges. Geobox does have some nice features that the current infobox does not have and it does make sense to try and make Infobox mountain and Geobox generate similiar results. The proposed changes do bring the infobox closer to Geobox (and some other project infoboxes) in terms of layout. As for my comments on the changes, I agree with Hike395 that there's a bit too much spacing. I do not feel as strongly about keeping the color shading on the left side —other infoboxes have stopped doing this and I somewhat agree that it's a decoration that perhaps no longer suits an encyclopedia like Wikipedia. Why not get rid of the line separators (the table's grid lines)? I do not think they are necessary and I actually find it distracting for them to be there if the left side color shading is no longer there. We might want to consider grouping some of the fields under a subheading (see Himalayan blue sheep for an example). RedWolf (talk) 01:59, 12 December 2009 (UTC)

I dug into the template coding a little bit. My attempts to override the default geography CSS class didn't work to my satisfaction, so I guess we can stick with the default spacing.

I really liked RedWolf's suggestion of using headers. Chris helpfully put the code for headers in, so it was easy to add: Mapping, Geology, and Mountaineering. I had to re-order the rows to make them group more sensibly into these headers. What do people think now?

I agree with RedWolf about the lines, but I am unsure how to get rid of them. —hike395 (talk) 08:22, 12 December 2009 (UTC)

Later: I managed to fix the spacing, font-size, and get rid of the lines. I'm now quite happy with the new infobox. I can see that it matches other infoboxes, and I appreciate the work of Chris (and others) in using the better {{Infobox}} code. Any comments on the new sandbox results at {{Infobox mountain/testcases}}?

Looking pretty good now — not seeing the range and location in the same area as elevation takes a bit of getting used to although it's probably fine the way it is. Should there be white spacing around the headers? The taxobox (see example link above) and albums (e.g. The Wall) add spacing which is probably done via CSS. RedWolf (talk) 15:55, 12 December 2009 (UTC)

I'm sorry: I just cannot figure out how to put white spacing around the headers. There's something about the geography infobox class that is blocking me. I'm certainly not a CSS expert. —hike395 (talk) 10:43, 13 December 2009 (UTC)

I like it although I think I like the Geobox style more (some of this is just down to the smaller text size though). I'm also a fan of the infoboxes on fr, it, sv, nl etc which move the map nearer the bottom. Some of these also have very slightly grey backgrounds for the headings which I think works quite well. If someone wanted to go live with the new template as is though I wouldn't object. JMiall ₰ 19:24, 12 December 2009 (UTC)

Font size: Do people prefer slightly smaller fonts (i.e., 90%)? I find them hard to read, so I overrode the default and made it 95% (to match the current infobox). But, if the consensus is to compress the infobox, I can change it back.

Map further down: I like the idea of the map further down --- that would conflict with the layout given by {{infobox}}, but it might be do-able.

Color of headers: I'm still partial to the color that we chose back in 2003, just to maintain continuity. —hike395 (talk) 10:43, 13 December 2009 (UTC)

I like the fonts a little smaller but if most prefer 95%, I'm okay with that. If there's a photo, then the map on the bottom might look better. However, if there is no photo, I think it looks better with the map on top. Perhaps the template logic could default to that but add an override parameter? I like the current color for the headers. I think we just need to see an example with the extra spacing added for the header rows as I suggested and if everyone likes that (or not), I think we can prepare for flipping the switch. RedWolf (talk) 02:16, 14 December 2009 (UTC)

I was unable to make the map move down without giving it a brown background, so that's no good. Hopefully someone else can try to put in the extra spacing —hike395 (talk) 04:31, 17 December 2009 (UTC)

I like it, particularly the useful subcategories in the right-hand column. Would there be any way of having a choice between "First ascent" (the row on the left) and "First recorded ascent" for cases when the mountain had obviously been ascended before the first recorded ascent (eg Ben Nevis, Piz da la Margna etc etc)? Can this be done manually on the new template or are we just stuck with "First ascent" and where there is a deviation from this it will have to be noted case by case? I have tried to alter it manually but the new template (as with the old) is resistant to this. Ericoides (talk) 16:30, 14 December 2009 (UTC)

Not sure how to do this, either. —hike395 (talk) 04:31, 17 December 2009 (UTC)

I can perhaps take a stab at this but won't have time until later this weekend. If anyone else can figure it out before then, that's great. RedWolf (talk) 00:48, 18 December 2009 (UTC)

I cannot figure it out either as to putting white spacing around the header lines. The geography css is somehow preventing it as all the other geography templates I have looked at do not use the geography css and simply use vcard and in those cases it displays with the white spacing around the heading lines. We need someone with more CSS expertise to help on this. RedWolf (talk) 22:17, 20 December 2009 (UTC)

Contents