Template talk:Infobox mountain pass

Traversed
The change from transversed to traversed is absolutely correct. However, it now needs to be changed in each of the articles using this template. Nationalparks 05:06, 15 December 2006 (UTC)


 * In the meantime, I put "Transversed by" in as an undocumented parameter.
 * —wwoods 00:12, 17 December 2006 (UTC)

Pyreneean mountain passes
I have been adding bits to Tour de France pages, and was surprised how few articles there are on the mountain passes, especially in the Pyrenees. I'll quite happily start creating articles about some of the climbs to be used in this year's tour, but before I do so can I briefly comment on the Template:Infobox Mountain Pass that's currently in use. If you compare the template on Col d'Aubisque with its French equivalent, I hope you'll agree that the French one is far more informative. Would there be any objection to me creating an improved template based on the French one? Daemonic Kangaroo 12:41, 3 July 2007 (UTC)
 * I think it's time we improve this template and as you said in WikiProject Cycling the french one looks fine. It would be better if some member of Wikiproject Mountains could give another view on the matter before someone changes the template.Drunt 13:43, 17 September 2007 (UTC)
 * Unless someone has a better idea I think we should add the same information that french template currently displays:

lalitude/longitude could be just coordinates. Maybe adding percentages is too technically? Should this template also be used for roads up to ski stations(Alpe d'Huez) or other one-road climbs(Angliru)?Drunt (talk) 20:14, 8 December 2007 (UTC)

Use of national flags?
In fixing a few pass articles just now, I note that national flags have been used to decorate the infoboxes. There doesn't seem to be any purpose to their presence but decoration, and I'm of a mind to take them out; unless there's already been a discussion justifying their presence? See WP:FLAGCRUFT.Skookum1 (talk) 17:36, 9 June 2009 (UTC)

coordinates generated by this infobox
The problem I see with Infobox mountain pass passing geocoordinates to Infobox mountain/main is that Infobox mountain/main transcludes Coord with  hardcoded, whereas Infobox mountain pass ought to have.

There are a couple ways to fix this. One would be to break free of Infobox mountain/main. Another would be to add an optional  parameter to Infobox mountain/main. Any opinions on how to proceed? --Stepheng3 (talk) 03:50, 1 March 2010 (UTC)


 * I like using Infobox mountain/main, because the two infoboxes share a lot of code and formatting. I like your suggestion about an optional coord_type: I am happy to implement it. —hike395 (talk) 04:51, 1 March 2010 (UTC)


 * ✅ --- I checked the Mountain testcases and Wolf Creek Pass --- the coordinates seem to be the correct type. Let me know if you see any problems. —hike395 (talk) 05:06, 1 March 2010 (UTC)


 * Well done. Thanks for the quick response. --Stepheng3 (talk) 05:15, 1 March 2010 (UTC)

Geobox
I have proposed that we delete geobox. That may effect this templates. You are invited to participate in the Geobox deletion dicussion. Andy Mabbett ( Pigsonthewing ); Talk to Andy; Andy's edits 19:43, 6 January 2012 (UTC).

Fix typo
There was a typo in the child parameter. Must this template be admin protected? It only has c. 600 transclusions and has never been vandalized.

Copy Template:Infobox mountain pass/sandbox to Tempate:Infobox mountain pass and replace template sandbox notice with Documentation. —hike395 (talk) 10:24, 22 April 2012 (UTC)


 * Hi Hike395. The template is only semi-protected so I fixed it myself. I'm sorry for the error and thanks for picking up on it.&#32;– droll  &#91;chat&#93;  15:45, 22 April 2012 (UTC)

Map, Photo, width and size parameters not working?
I have done a bit of cleanup work on Khawak Pass. One thing I did was move an image of a map into the Infobox. I wanted to change the image size to 300px. It didn't change from the default 280px (photo) or 272px (map).

I tried this:

(Yes, I know that normally one isn't supposed to use the .  But, doing so proves that the image size can be changed within the confines of the template.)

That made the image the correct size. Ahead of the image (above in the Infobox) the image was: ; sort of like this:



(except that here the extraneous text is on the sides—you get the idea) The markup for that is:



which I think is a good mimic of what the template is doing.

From this I'm guessing that there is something wrong with the template code that is forcing the default width values to be used regardless of what the photo_width value is. If it were working correctly, one would think that the extraneous text following the image would match 400 that I used in my test case.

All of this is the same if I used map parameters instead of photo parameters.

—Trappist the monk (talk) 03:44, 22 July 2012 (UTC)
 * This is by design. 280px and 272px are are maximum sizes. Any size specified that is larger that the maximum is set to the maximum. If left unspecified, the maximum size is used. —hike395 (talk) 04:05, 22 July 2012 (UTC)


 * What are the design constraints? What is it about this infobox that requires images and maps be a certain size or smaller? This infobox is the first one that I've encountered where image-size limits have been imposed by the template rather than by the article's community of editors. Similarly, why two different maximums for map and photo images?


 * —Trappist the monk (talk) 11:48, 22 July 2012 (UTC)

Template broken?
Recent changes to this template, or perhaps to templates used within it, appear to be broken. For example, see Grimsel Pass or Furka Pass. The coordinates are followed by an unexpected string like this (for the Furka pass):



I get the same effect on both Google Chrome and Microsoft Internet Exploder. My knowledge of complex template syntax isn't up to resolving this. Can somebody take a look at it. -- chris_j_wood (talk) 11:41, 31 October 2014 (UTC)


 * I will investigate. Looks likes it might be a problem in coord —hike395 (talk) 05:50, 1 November 2014 (UTC)
 * Looks like it was fixed today. —hike395 (talk) 06:23, 1 November 2014 (UTC)