Template talk:Infobox bridge/Archive 1
![]() | This is an archive of past discussions. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page. |
Archive 1 | Archive 2 |
US data
In the US, most of this data appears in the national bridge inventory data; if you need a copy I can send it. --SPUI 02:02, 27 Nov 2004 (UTC)
id 8 4-18
coordinates 16/17 130-137/138-146
maint 21 151-152
open 27 157-160
below 39 190-193
- when closed (for a lift bridge): 116 386-389
design 43 202-204
mainspan 48 218-222
length 49 223-228
width 52 239-242
clearance 53 243-246
how to add a photo to this template
From: Pulaski Skyway
- |bridge_name=[[image:Pulaski_Skyway_northbound_plaque.jpg|300px|Northbound at the span over the Passaic River.]]|official_name=General Pulaski Skyway|
Cacophony 20:03, September 10, 2005 (UTC)
- This still works but there is now an "Image=" parm that works as well or better ++Lar: t/c 14:46, 20 January 2006 (UTC)
Term defintions
Am I correct that Vertical clearance is the height of the bridge structure above the roadway and that Clearance below is the distance between the water and the bottom of the bridge? --Jason McHuff 00:40, 26 September 2005 (UTC)
- Yes that is the correct interpretation. I have all of this info in my newly received National Bridge Inventory Data CD, but I am having trouble deciphering the 300 character long codes. Ack! Cacophony 06:14, 26 September 2005 (UTC)
- I admit to still being a bit confused, is the vertical clearance the total height of the structure (the tower height, for example, for a suspension bridge) or the clearance for the opening in the tower (continuing with the same example) that determines how tall a vehicle can be and pass through. If the latter, is that as significant as the height of the tallest part of the structure? I dunno... I just added this box to a few bridges and I got all confused trying to do this, usually the clearance you get from other sites such as structurae.de is the bridge to water clearance for ships... not the other one. PS: where did you guys get these data CDs? Thanks! ++Lar 05:15, 20 December 2005 (UTC)
- The information on how to get a CD is here. The term vertical clearance is used to describe how tall a vehicle can be. I personally think that it shouldn't be included in the infoboxes. Cacophony 06:31, 20 December 2005 (UTC)
- OK... I guess it makes sense. So for a deck truss like Poughkeepsie Bridge do you suggest 'infinite' as the value there? ++Lar 12:32, 20 December 2005 (UTC)
- The national bridge inventory lists the value as infinite. I don't really like having it included in the infobox. Cacophony 23:15, 25 December 2005 (UTC)
- maybe make it optional? I think you can probably tell I'm not a huge fan. I can go fix the articles I put the box into to get rid of ? (I gotta stop putting ? in!) ++Lar 02:27, 26 December 2005 (UTC)
- The national bridge inventory lists the value as infinite. I don't really like having it included in the infobox. Cacophony 23:15, 25 December 2005 (UTC)
- OK... I guess it makes sense. So for a deck truss like Poughkeepsie Bridge do you suggest 'infinite' as the value there? ++Lar 12:32, 20 December 2005 (UTC)
- The information on how to get a CD is here. The term vertical clearance is used to describe how tall a vehicle can be. I personally think that it shouldn't be included in the infoboxes. Cacophony 06:31, 20 December 2005 (UTC)
- I admit to still being a bit confused, is the vertical clearance the total height of the structure (the tower height, for example, for a suspension bridge) or the clearance for the opening in the tower (continuing with the same example) that determines how tall a vehicle can be and pass through. If the latter, is that as significant as the height of the tallest part of the structure? I dunno... I just added this box to a few bridges and I got all confused trying to do this, usually the clearance you get from other sites such as structurae.de is the bridge to water clearance for ships... not the other one. PS: where did you guys get these data CDs? Thanks! ++Lar 05:15, 20 December 2005 (UTC)
- Yes that is the correct interpretation. I have all of this info in my newly received National Bridge Inventory Data CD, but I am having trouble deciphering the 300 character long codes. Ack! Cacophony 06:14, 26 September 2005 (UTC)
how do you make fields optional? Cacophony 06:32, 26 December 2005 (UTC)
- Beats me! I just went and checked and I think they already were. Apologies if I am confused but don't constructs like this:
|- class="hiddenStructure{{{id|}}}" | '''[[National Bridge Inventory#ID numbers|ID number]]''' | {{{id}}}
- make the parm ("id" in this case) optional? I am only an egg when it comes to template writing, I must confess. switches and qifs and things are not something I totally grok. ++Lar 06:56, 26 December 2005 (UTC)
- Neato, I didn't realize how that worked. I saw some templates that had a question marks in them, but those have to be deleted in order for the field to disappear. Check 10-4. Cacophony 08:30, 26 December 2005 (UTC)
- Well cool! Glad to "sort of cluelessly" be of service! And thanks for fixing that in some of the articles I've been editing. I would have done it "eventually"... (meaning: probably would have forgotten about it for a while) so coolness all around. ++Lar 14:19, 26 December 2005 (UTC)
- Neato, I didn't realize how that worked. I saw some templates that had a question marks in them, but those have to be deleted in order for the field to disappear. Check 10-4. Cacophony 08:30, 26 December 2005 (UTC)
Deprecated?
(asked this on Template talk:Infobox BridgeSpecificWithMap too) I just noticed on the Wikipedia:WikiProject Bridges page that this template is said to be deprecated and that Template:Infobox BridgeSpecificWithMap should be used instead. But I don't have a map for (for example: Kingston-Rhinecliff Bridge. It does say that the map is optional. Can someone help me out by explaining how to use that template? Thanks! ++Lar 22:42, 20 December 2005 (UTC)
- The above comment is obsolete, the WithMap version's features have been merged in as optional parms and ..WithMap is now the obsolete/deprecated one. Deleted even, IIRC... (as evidenced by the redlinks) ++Lar: t/c 15:14, 20 January 2006 (UTC)
Demolished Bridges
For bridges that have been razed, do we want an optional field that gives their destruction date? Also is it worth noting somewhere that the geolocation stuff won't show you a pic of the bridge (because it isn't there any more) some how? I can hack the first one in, no worries (if folks agree... call it what "demolished date" ??) but the second one I dunno about. Thoughts? ++Lar 00:13, 30 December 2005 (UTC)
- I think that is a good idea. Why not throw in average daily traffic as well. That info is on the CD. The optional fields are great, put anything in there and only use it if you have the information. Cacophony 20:08, 2 January 2006 (UTC)
- I added both fields just now. I see no reason not to add information being that the field will only be shown if the data is present. Cacophony 00:16, 7 January 2006 (UTC)
- K, I did Niagara Cantilever Bridge and Sky Ride... see what you think. We may or may not want to tweak the wording on the field, because for one I knew the month and for the other I didn't. Tacoma Narrows Bridge if it gets a box, can use this presumably. Although maybe we need to figure out how to handle successive bridges at the same location (consider Carquinez for an example... the first one was built in the 20s, the second similar one in the 50's, now they're building a new (and different) one and will tear the first one down. arguably these all belong in one article not split out. So maybe they get 3 boxes? ++Lar: t/c 02:17, 7 January 2006 (UTC)
- I added both fields just now. I see no reason not to add information being that the field will only be shown if the data is present. Cacophony 00:16, 7 January 2006 (UTC)
carries?
Should the carries field include #1 what type of traffic (highway, pedestrian, etc), #2 what roads or rail lines, or #3 how many lanes/tracks? I have seen all three used. My preference would be the name of the road or rail line carried, maybe "3 lanes of Interstate 6". Cacophony 18:58, 2 January 2006 (UTC)
- I'll answer this if you answer some of mine! ... OK, kidding. I think the number of lanes and direction, what type of traffic, and what designation/ownership for each type would ALL be useful information and broadening carries oror expanding it into several subfields might be goodness. A (clearly) hypothetical (and clearly exaggerated) example: The Mumble Bridge carries 3 eastbound general use lanes and one bidirectional HOV lane of US 29/I 52, a narrow gauge track of the D&RGW tourist railway, two standard gauge tracks of the BNSF, a busway restricted to buses of the greater Billings Mass Transit Authority, a bidirectional pedestrian path, and the Montana section of the trans Alaska Pipeline. Fitting all that into "carries" is a bit much. For more real examples, see Williamsburg Bridge and Sydney Harbour Bridge ++Lar: t/c 20:00, 2 January 2006 (UTC)
move?
How about, for the sake of simplicity, moving this template to Template:Bridge? Cacophony 00:10, 7 January 2006 (UTC)
- I thought the convention was to use Infobox in the name for infoboxy things but I could be confused. ++Lar: t/c 00:25, 7 January 2006 (UTC)
- K, scope out this little search (which by the way is really handy, you may want to save it: ) all pages in template space that start with infobox .... there are hundreds of them. So I would say it's a convention. (not to be confused with being OPPOSED to a move, mind you) Hope that helps. ++Lar: t/c 00:32, 7 January 2006 (UTC)
- It is convention, mostly to prevent arguments and inconsistency when an infobox, a footer, a series box, or any other template would all relate to "Bridge". -- Netoholic @ 00:34, 7 January 2006 (UTC)
Option vs required
I'm thinking locale and opening date may want to be optional parms. Not sure. Thoughts? ++Lar: t/c 07:08, 11 January 2006 (UTC)
- You'll probably want to discuss this on Wikipedia talk:WikiProject Bridges. My feeling is that, if you want to have a high-quality and consistent Infobox, you should limit the optionals to those which are impossible to fill in/not applicable on more than around 25% of potential articles. The benefit of showing the empty rows is that editors will be prompted to fill them in. If you're hiding to many, you should reconsider whether they are truly important to the Infobox. Some things are so infrequent that mention in the article itself is better. -- Netoholic @ 07:59, 11 January 2006 (UTC)
- Maybe it could be discussed there but this IS the talk page for the template. I guess I think the template ought to have as much optional as possible, because I can think of a plausible scenario for just about every field not having a known value. That doesn't contradict the view that editors should strive to fill in as many fields as they can, which I do agree with. ++Lar: t/c 15:12, 11 January 2006 (UTC)
- I suggest contacting the WikiProject be cause they define what the articles contain and look like overall. This template is just part of how that is implemented and may not be on all their watchlists. This talk page here is more about technical aspects. The way I see it, if fields are not visible, few editors will even realize those options are available. Also, some fields are almost trivial and can really stray from the core set of information that this infobox should present. -- Netoholic @ 16:10, 11 January 2006 (UTC)
- Netoholic, I'm sorry for any confusion, I am already a member of the bridges project, have made several suggestions about how things ought to be done there, many of which have been adopted, and I've already used this box in several new bridge articles I authored, as well as adding it to bridge articles I happened to edit that were in existance already. The use of the <noinclude> tagging to show an example of the template usage alleviates the "won't tend to fill it out" concern in my view. Again, I can think of a plausible scenario for any particular field needing to be optional, even in an article where most other fields are used. I'm not really seeing this as a big an issue as you may think, though. I'll just go ahead and make the changes myself when I get a chance. Hope that helps. ++Lar: t/c 16:47, 11 January 2006 (UTC)
- I suggest contacting the WikiProject be cause they define what the articles contain and look like overall. This template is just part of how that is implemented and may not be on all their watchlists. This talk page here is more about technical aspects. The way I see it, if fields are not visible, few editors will even realize those options are available. Also, some fields are almost trivial and can really stray from the core set of information that this infobox should present. -- Netoholic @ 16:10, 11 January 2006 (UTC)
- Maybe it could be discussed there but this IS the talk page for the template. I guess I think the template ought to have as much optional as possible, because I can think of a plausible scenario for just about every field not having a known value. That doesn't contradict the view that editors should strive to fill in as many fields as they can, which I do agree with. ++Lar: t/c 15:12, 11 January 2006 (UTC)
Map standards?
I'm new to this... what are the standards for this map and map size thing? Do you use Google Maps? Other satellite sources? When I upload the image from this source, under what license should it be? Thanks! —Rob 18:51, 14 January 2006 (UTC)
- A discussion about bridge maps has been taking place at Wikipedia_talk:WikiProject_Bridges#Maps. Ideally the license should be GFLD compatible. There are several websites that generate public domain maps that you can edit. If I were more proficient with Photoshop I would be able to give you an example. Right now the best example that comes to mind is on San Francisco-Oakland Bay Bridge, but I would say that it could use labels. A map of the state with a pushpin on the bridge location would also be handy. Just think about what it would take for you, having no prior knowledge, to understand exatcly where a bridge is located. Cacophony 20:14, 14 January 2006 (UTC)
- And no, you should not use Google Maps to generate maps for Wikipedia because they are copyrighted. That's generally the run for any for-profit site. Cacophony 20:23, 12 February 2006 (UTC)
Coordinates
I've added a line similar to the one in Template:Infobox Lighthouse. I find the existing "lat=" "long=" a bit problematic because it requires conversion from DMS to DD just to enter it into the lat= "long=" box. The "coordinates=" line should be used with {{coor d}} {{coor dm}} or {{coor dms}} and will point all the images that the "lat=" and "long=" point to. If not used it should remain hidden so all the pages currently using this template should not need to be changed. It also links to the maps and all the aerial photos similar to the existing "lat=" "long=" lines. See the infobox for Fred Schwengel Memorial Bridge as an example of usage. --Dual Freq 16:24, 25 March 2006 (UTC)
- Who was that? SPUI I am guessing? Personally I strongly prefer the lat/long DD format because the coords I can find easily for most bridges are in that form and conversion is extra work. I'd strongly oppose breaking this template in any way or requiring any sort of recalculations. I think when making changes, discussing them first is often a good approach unless one is sure they don't break anything. ++Lar: t/c 14:10, 6 May 2006 (UTC)
Sorry about that, I must have only hit two tildes when I signed the above comment. I intended for the "coordinates=" line to be used with any of the following {{coor d}} {{coor dm}} or {{coor dms}}. They do the same thing as the geolinks and it takes up less space. I prefer DMS because I use software that outputs DMS and DMS looks better displayed in the template. --Dual Freq 14:40, 6 May 2006 (UTC)
- I think it's a matter of taste as to whether DMS looks better or not. Further DD seems to be more widespread on sites that can take, or supply, coordinates and that's more important to my way of thinking... enabling readers and editors to produce accurate and generally high quality articles takes precedence. IMHO anyway. So if the upshot is that this template is broken, I'd like to see that corrected. But if the upshot is that it works with any style, great. As long as the next step isn't to try to get rid of DD, I'm all for it. ++Lar: t/c 15:41, 6 May 2006 (UTC)
I hadn't noticed the changes made recently, I see that they have changed the maps portion. Looks like the maps section was changed [here] by User:SPUI. My changes were done in March and didn't affect the map section, just allowed one or both to be used depending on the editor's choice. Personally, I prefer just the coordinates section instead of the lat= long=, but I didn't want to affect the other pages using the template nor did I want to change all the pages to a new format. As for right now, I recommend either remove lat= and long= and convert to coordinates= on all pages or revert to the template before SPUI changed the maps section. (I'd say revert to previous, it's easier than changing all the pages) --Dual Freq 15:57, 6 May 2006 (UTC)
- I didn't catch that this was an older change, sorry! Right now it's broken it seems. Take a look at Kingston-Port Ewen Suspension Bridge for example. There's a tick at the top above the box that does nothing, and the nice links to Google, Terraserver, and Yahoo we used to have in the bottom of the box are replaced with a link to a page with SO MANY MAPS that it's effectively useless. I am not up for warring with SPUI about stuff though, that's just a no win situation. Apologies if I cast aspersions on you... ++Lar: t/c 16:03, 6 May 2006 (UTC)
lat long vs coordinates
I reverted because it is the editors choice to use either lat= or long=. If an editor wants the stuff similar to {{Geolinks-US-cityscale}} then use lat= and long=. If an editor just wants {{coor d}} / coor dms then use coordinates=. Using a "template within a template" should be avoided as was done by putting coor d into this template. --Dual Freq 16:20, 6 May 2006 (UTC)
- It's probably necessary to mention that the datum used by this template is WGS84 or equivalent. Using a different datum might pull up the wrong image. Old sources that use NAD27 or others should probably be converted as they can be off by 200 meters. Don't blame me, I didn't make up the coor d or geolinks template that this template uses. --Dual Freq 11:50, 7 May 2006 (UTC)
Height needed
Could someone please add a height parameter to the template? Think of the Golden Gate Bridge for a reason why. What parameter would you use for the height of the towers? Also then I can fix Conowingo Dam, although using Infobox Bridge there is still an uneasy fit. Thanks. I'd attempt it, but it would be my first template edit and the inevitable screw up(s) would be way too visible.--J Clear 02:44, 1 July 2006 (UTC)
Architect / Builder
Anyone mind if I add in two optional parameters to specify the architect and builder (construction company or organisation) of the bridge? I am working on some Australian bridge articles and would like to include the information. amitch 13:03, 17 October 2006 (UTC)
Maps missing
Looking at San Francisco-Oakland Bay Bridge I couldn't see a map with the changes from User:NE2, I'm not sure what the problem was, but reverting them seemed to fix the Bay Bridge article. --Dual Freq 17:50, 29 December 2006 (UTC)
- I found my error; now James River Bridge and San Francisco-Oakland Bay Bridge both work properly. --NE2 18:43, 29 December 2006 (UTC)
Color of title
I know that some older browsers have trouble with white text. could we maybe try black text on a pastel background instead of white on black? I'll make such a change shortly, revert me if you really think it's bad. ++Lar: t/c 19:27, 1 January 2007 (UTC)
- I tried it, and I see VerructeDan went back to no color background. I support that change as well. I'm just concerned about white text not always working. ++Lar: t/c 15:17, 3 January 2007 (UTC)
"Troll" field
Is this field meant to be a joke? Laïka 16:04, 11 February 2007 (UTC)
- Looks like a joke added by NE2 a while ago that went uncaught. I have removed it. —Dgiest c 19:02, 11 February 2007 (UTC)
- That was not my addition; it was added by Lar in this edit. --NE2 22:50, 11 February 2007 (UTC)
Microformat
I've added the necessary spans and HTML class names for an hCard microformat; plus documentation. Andy Mabbett 16:58, 17 April 2007 (UTC)
The Geolinks format
Please monitor the format of Template:Geolinks-US-buildingscale and use it format for offering mapping services.--SallyForth123 03:33, 5 August 2007 (UTC)
map_text parameter
I don't think the map_text parameter is being handled correctly -- it shows up in the label column, not under the image (and even then only if map_cue is defined). If map_cue is not defined, the text never shows up at all. It looks pretty ugly in 10th Avenue Bridge (granted, I think that page has too much map_cue text anyways). I'm pretty sure the "<br>{{{map_text}}}" text needs to be moved to the map image line, not the map_cue line. I could be wrong though since I've never looked at or touched this template before, so I don't want to change it without checking first. Carl Lindberg 19:48, 5 August 2007 (UTC)
Sufficiency Rating
The sufficiency rating for US bridges is available here. This might be added to the box. --Ace Telephone 23:41, 7 August 2007 (UTC)
Use "coor title d" in preference to "coor d"?
Over the last year or so a convention seems to have developed whereby coordinates are expected to appear on an article's title line at the right. To conform, this template would have to be modified to use "coor title d" in preference to "coor d". Thoughts or objections anyone? -Arb. (talk) 21:24, 10 February 2008 (UTC)
- What does this mean? I use { {coord} } for all my coords. - Denimadept (talk) 00:35, 11 February 2008 (UTC)
See {{Coor title d}} -Arb. (talk) 01:06, 11 February 2008 (UTC)
- See the display of the following example for why I'm puzzled: 43°28′25″N 72°23′01″W / 43.47361°N 72.38361°W I put the like on the "coordinates" line of the infobox. - Denimadept (talk) 03:09, 11 February 2008 (UTC)
OK, to put it another way, is it correct to have the coords buried near the bottom of the infobox or would it be better to follow the new/developing convention and have them display on the top right of the title line as at eg Winchester? -Arb. (talk) 11:54, 12 February 2008 (UTC).
- I think you're missing what I did with that coord above. It is listing in both places: where I put it and in the title line. - Denimadept (talk) 17:01, 12 February 2008 (UTC)
You are right. I missed the title line display. My bad. The page that brought me here is Bennerley Viaduct. Its bridge infobox uses "|coordinates= {{coor d|52.988|N|1.3|W|region:UK_type:landmark}}". Following your example at Cornish-Windsor Covered Bridge (which uses "|coordinates= {{coord|43|28|25|N|72|23|01|W|region:US_type:landmark|display=inline,title}}" I've tried several variations but none of them give both the title line display and the N and W needed in the inline display. Perhaps with your expertise you can sort it more quickly than I can? Regards, -Arb.
- How's that? I revised the whole Infobox using the source template, got a more on-target coordinate value (try right-clicking in either Yahoo or Google maps), used the convert template to make the measurements more like what people expect, and plugged in more data from your article. - Denimadept (talk) 18:36, 12 February 2008 (UTC)
You've done a good job over there. Thanks. -Arb. (talk) 20:49, 12 February 2008 (UTC)
Closed != Destructed
The parameter "closed" indicates in the template "Destruction date". Bridges can be closed and not destroyed. For example, the Waldo-Hancock Bridge was closed on December 30, 2006 but remains standing. 65.125.133.211 (talk) 21:15, 23 January 2008 (UTC)
- Agreed. It'd be better to have two entries: one for "closed" and another for "destroyed" or "removed". - Denimadept (talk) 21:47, 23 January 2008 (UTC)
- So the $64,000 question: does "closed" parameter become "Closed date" or does the new "destruction" parameter become "Destruction date"? Rough survey shows about 1100 transclusions of this template and I have no idea if the closed parameter has been used as named or displayed...
- Perhaps neither. The tenses on "open" and "closed" don't agree. So how about leaving "closed" as-is and adding "close" and "destroy". This allows for gradual transition to the correct parameter as each bridge is assessed. Once the parameter is no longer used then it can be removed. Cburnett (talk) 00:08, 24 January 2008 (UTC)
FYI: since the parameter was added it has always displayed as "Destruction date". Cburnett (talk) 00:22, 24 January 2008 (UTC)
- Now see Lyndon Bridge. The revision just made [1] was clearly made due to the fact that "closed" means "destroyed" in this template. We need to update the template. I have no idea how to even see the template's code, so I can't do it. Would someone please do this? As part of the change, all existing use of the "closed" parameter should be replaced with "destroyed", in order to make "closed" available for its obvious use. - Denimadept (talk) 21:45, 19 March 2008 (UTC)
- Okay, I see how to see the code. The main issue is to replace "closed" with "destroyed" and update every article which uses that entry. Does anyone have a bot which can do this? - Denimadept (talk) 21:48, 19 March 2008 (UTC)
Template changes
How does "number of arches" differ from "number of spans"? I'd think the latter would be more general. - Denimadept (talk) 20:32, 22 May 2008 (UTC)
- You are probably right - as an artist rather than engineer I think of arches. Just done one test so far. Hope you approve the other additions which I felt needed to be included. Regards Motmit (talk) 20:39, 22 May 2008 (UTC)
- The rest of your changes look good. I downloaded the national db from the Feds yesterday. There's a LOT more we can add! I have to write a program to read the Federal data and then figure out what to do with it. Maybe I could have it emit populated "infobox bridge" entries. - Denimadept (talk) 20:48, 22 May 2008 (UTC)
Toll Prices
The policies at WP:NOPRICES and WP:NOTTRAVEL are unequivocal about this. Wikipedia is not a catalog and not a travel guide so prices can not be included unless absolutely necessary for the article. I fail to see how including toll rates follows this policy and the actual tolls need to be deleted. -- KelleyCook (talk) 21:34, 21 August 2008 (UTC)
Remove Terraserver
Chain of Rocks Bridge | |
---|---|
![]() | |
Coordinates | 38°45′38″N 90°10′35″W / 38.76056°N 90.17639°W |
Carries | Pedestrians and bicycles |
Crosses | Mississippi River |
Locale | St. Louis, Missouri |
Maintained by | Trailnet |
Characteristics | |
Design | Cantilever through-truss |
Total length | 5,353 feet (1,632 m) |
Width | 24 feet (7 m) |
History | |
Opened | 1929 |
Location | |
![]() |
Terraserver is a commercial website which charges US$29/month subscription to access high resolution images. I think it should be removed from the infobox. Discuss... --Cheesy Mike 07:36, 9 June 2007 (UTC)
- I agree, but that whole section of the infobox should go, and be replaced with a coordinates link, as per my comments, above. Andy Mabbett 08:46, 9 June 2007 (UTC)
- As nobody objected I am removing Terraserver. Anyone care to pick up on Andy Mabbett's comments? --Cheesy Mike 13:06, 22 June 2007 (UTC)
- Terraserver usa, the one linked here, is free and run by Microsoft see TerraServer-USA vs Terraserver.com. I prefer its interface, allowing easy viewing of aerial images and topo maps. --Dual Freq 13:12, 22 June 2007 (UTC)
Point taken, I hadn't realised the difference. So now a new argument for removing the Terraserver-USA (and Topozone) link: it only covers the USA. Infobox Bridge covers bridges all over the world, so what is the point of putting links in an infobox if they don't result in any useful data? e.g. Humber Bridge. Given that country specific data can be easily provided using the coord template, I would suggest that both Terraserver USA and Topozone be removed as they are US only. --Cheesy Mike 15:05, 22 June 2007 (UTC)
- That section is basically optional anyway. |coordinates= line is meant for the {{coor dms}} or similar templates. Use Lat= and long= or |coordinates= See example at right, you don't need to use that part of the template, it's in there for backward compatibility. --Dual Freq 03:51, 24 June 2007 (UTC)
- Older coordinates templates are now deprecated, Please use {{coord}}. Thank you. Andy Mabbett (User:Pigsonthewing); Andy's talk; Andy's edits 18:51, 26 September 2008 (UTC)
Closing vs. destruction
The instructions say that "closed= Closing date", but it displays as "Destruction date", which seems different. The destruction of a bridge may begin on the closing date, or not.
—WWoods (talk) 19:54, 26 October 2008 (UTC)
- Look above. - Denimadept (talk) 20:43, 26 October 2008 (UTC)
coord "display=title"
Why was "title" removed from the "display=inline,title"? [2] I noticed that an icon for a bridge, specifically Boone Bridge, is not showing up in Google Earth and I believe this is why, since I think I've read that "title" has to be used.[3] Note that this will also probably affect Google Maps since it can now show Wikipedia links too. Jason McHuff (talk) 12:36, 8 January 2009 (UTC)
- It was related to a discussion having to do with the basic concept of infoboxes, IIRC. Defaulting to "title,display" means the infobox affects something outside of its own bounds. You should note that the change was labeled "for now". Consensus isn't really stable on this issue. - Denimadept (talk) 15:17, 8 January 2009 (UTC)
- Thanks for the explanation. It does make a little sense given how I've read that info boxes (and maybe templates in general) can be confusing to new editors, since the output can look a lot different than what's visible in the edit box. And I did see the "for now", but didn't really see any discussion and the edit was in September. Jason McHuff (talk) 14:46, 9 January 2009 (UTC)
- Pigs changed this which is fine, but it does mean that where a coord had been added outside the box with title, there are now some overlapping coords at the head of page. Any ideas on how to sort this out apart from individual edits? Regards Motmit (talk) 15:01, 9 January 2009 (UTC)
I added "title" and then removed that part as it broke some of the uses (overlapping with other templates used in articles). Before readding it, one should check the articles for overlaps. -- User:Docu
It appears that the change was already done. Of four checked articles, two are now messed up:
To avoid users breaking this infobox, you may want to ask it to be protected so that only administrators can edit it. -- User:Docu
- Thanks for the explanation. It looks like there's some work to do. I at least fixed the two examples. Jason McHuff (talk) 11:49, 12 January 2009 (UTC)
Templates for merging and deletion
I have nominated three bridge templates and two aqueduct templates for deletion, following merger, with this template. Please feel free to comment at the linked debates. Andy Mabbett (User:Pigsonthewing); Andy's talk; Andy's edits 01:43, 25 January 2009 (UTC)
predecessors, followers, and order of presentation
Instead of the current format (apparently recently merged in from "Infobox bridge2") I would prefer it if the preceded parameter was renamed to preceded_by and if the followed parameter was renamed to followed_by. However, in order to not break any articles still using either the preceded or the followed parameters I would also include them in the template. In order to present the dates and structures in chronological order I would prefer that preceded_by (and preceded) precede the begin parameter and that followed_by (and followed) follow the closed parameter. In other words I would prefer to see this:
|begin = |complete = |open = |heritage = |collapsed = |preceded = |followed = |closed =
be changed to:
|preceded_by = |preceded = |begin = |complete = |open = |heritage = |collapsed = |closed = |followed_by = |followed =
Would any of you object to such a change? 67.86.73.252 (talk) 13:26, 28 February 2009 (UTC)
How do I use this with...
...another infobox? I just created Columbia Bridge (New Hampshire) and added the NRHP infobox after the Bridges infobox. In Cornish-Windsor Covered Bridge, I added the Bridges infobox to an existing article containing the NRHP infobox. They both look clumsy. How should I do this? —The preceding unsigned comment was added by Denimadept (talk • contribs) 03:39, August 23, 2007 (UTC).
- I would suggest asking WP:NRHP about removing their infobox from their articles in cases where there is already another infobox, such as Infobox Bridge, and adding the NRHP data to fields in that infobox. I'd say nearly any other infobox takes precedence as NHRP is regionally restricted to the USA. WP:NRHP already sets exclusions for lighthouses, after all. --Geopgeop 11:36, 10 September 2007 (UTC)
- That would mean we should add the features to Infobox Bridge which are currently only in the NRHP box. What might be better is if there were a way to incorporate an arbitrary infobox into another infobox. Then we could have any arbitrary features in Infobox Bridge that are added to another Infobox without having to modify Infobox Bridge further. Is this functionality available? I expect that NRHP is already USA-specific, not so? Is there a more global organization which does the same work? - Denimadept 13:00, 10 September 2007 (UTC)
- The issue also arises in the UK, where bridges can enjoy heritage status as a listed structure. The addition of a field to show heritage status would be useful, but I doubt if more than one field would be appropriate. cheers Kbthompson (talk) 18:46, 26 November 2008 (UTC)
- Done - free form "Heritage status" field added. Motmit (talk) 19:39, 26 November 2008 (UTC)
I've found an answer to my original question. See the documentation on {{Infobox nrhp}}, specifically the EMBED option. - Denimadept (talk) 21:03, 15 July 2009 (UTC)
Add {{Location map}} to infobox?
If a {{coord}} exists in the infobox, and a new line, "locmapin" (as in {{infobox nrhp}}) exists, and points at an image that exists, invoke {{Location map}} as in that infobox? - Denimadept (talk) 21:09, 15 July 2009 (UTC)
- Here's an example of what I mean, using the existing "extra" line: Norwottuck Rail Trail Bridge - Denimadept (talk) 21:15, 15 July 2009 (UTC)
Closed != Destroyed (part 2)
I see that this was discussed a while back, but apparently not addresed by someone good at adding new fields.
Until a new field is added, the template should use "Closed", since all destroyed bridges are closed, but not all closed bridges are destroyed.
P.S. "Opened" vs. "Opening Date" etc. – the former takes less space (good in an infobox) and means the same thing.
—MJBurrage(T•C) 22:47, 17 November 2009 (UTC)
Designation
My suggestion is to add a field Designation to this template as per Template:Infobox theatre, so that formal listings (e.g. historic places) can be recorded. Schwede66 (talk) 22:48, 15 January 2010 (UTC)
- Is that different from the {{Infobox nrhp}}? - 143.112.32.4 (talk) 23:35, 15 January 2010 (UTC)
- Thanks for the response. I've now seen that there is a field 'Heritage', which does what I want. But it's good to be aware of infobox nrhp, as that can be embedded into other infoboxes - that might come handy one day. Schwede66 (talk) 03:11, 16 January 2010 (UTC)
Coordinates
I would like to replace
{{#if: {{{lat<includeonly>|</includeonly>}}}{{{long|}}}| {{!}} colspan="2" {{!}} * [{{Coor URL}}{{{lat}}}_N_{{{long}}}_E_type:landmark_region:US Maps and aerial photos] ** Street map from [http://maps.google.com/maps?ll={{{lat}}},{{{long}}}&spn=0.015,0.025 Google Maps] or [http://maps.yahoo.com/maps_result?lat={{{lat}}}&lon={{{long}}}&mag=2 Yahoo! Maps] ** Topographic map from [http://topozone.com/map.asp?lat={{{lat}}}&lon={{{long}}}&s=24&size=m&datum=nad83 TopoZone] ** Aerial image or topographic map from [http://terraserver-usa.com/image.aspx?s=11&lat={{{lat}}}&lon={{{long}}}&w=2 TerraServer-USA] ** Satellite image from [http://maps.google.com/maps?ll={{{lat}}},{{{long}}}&spn=0.015,0.025&t=h Google Maps] or [http://virtualearth.msn.com/default.aspx?cp={{{lat}}}{{!}}{{{long}}}&style=h&lvl=15&v=1 Microsoft Virtual Earth]}}
to use {{coord}}, display the coordinates, add a geo microformat remove the US-specific region and remove the specific links, which belong on {{GeoTemplate}}.
I think the new code should be:
{{#if: {{{coordinates<includeonly>|</includeonly>}}}| ! style="vertical-align: middle;" {{!}} [[Geographic coordinate system|Coordinates]] {{!}} {{Coord|{{{lat}}}|N|{{{long}}}|E|type:landmark|display=inline,title}}
but that doesn't seem to work. Can anyone assist, please? Andy Mabbett 22:58, 10 May 2007 (UTC)
- I removed the N and E parameters because it was making negative east coordinates here in the western hemisphere. 117Avenue (talk) 05:09, 3 March 2010 (UTC)
Reorganised
The fields were reorganised by the following notional categories:
- naming
- image
- function
- location
- design
- construction
- operation
- geolocation
It might still benefit from further reorganisation and say the addition of a |dismantled/demolished field. Stuffed cat (talk) 12:58, 10 June 2010 (UTC)
- Sounds good. Plastikspork ―Œ(talk) 00:27, 14 June 2010 (UTC)
Bridge name/Native name
If both of these are provided, there's no line break between them. See Hohenzollernbrücke after I finish editing it soon. - Denimadept (talk) 21:25, 8 February 2011 (UTC)
Fixed 117Avenue (talk) 23:15, 8 February 2011 (UTC)
- Thanks. Some day, I may have to learn the microformatting language used here. - Denimadept (talk) 23:48, 8 February 2011 (UTC)
This template is impossible to understand
I've tried to improve the Teston bridge article by switching from {{infobox historic building}} to {{infobox bridge}}. I'm sorry to say that I found the instructions for using this template not helpful. There is no example to copy from so that one can see what needs to be put where. For whatever reason, the map will display, but no red dot appears to show the location of the bridge on the map. There is nothing here saying how to achieve this! Mjroots (talk) 07:02, 2 July 2011 (UTC)
- BTW, the reason you're seeing a map displayed correctly is that I've hidden the bridge infobox until such time as it will display everything correctly. Until then, the historic building infobox is in use. At least that template has detailed instructions. Mjroots (talk) 07:06, 2 July 2011 (UTC)
- It looks like you figured it out? As far as I can tell, this template doesn't have a "built-in" location map feature, so it has to be added manually as you have done. That could be added, but it hasn't been yet. Thanks! Plastikspork ―Œ(talk) 01:58, 4 July 2011 (UTC)
US centric
The information for this template is very US centric. In particular, the field for 'id' links to the National Bridge Inventory, which only applies to US bridges. There are many other forms of number that could be put there (eg in the UK, Historic Engineering Work number, listed building number). Espresso Addict (talk) 19:52, 6 December 2012 (UTC)
- So add the other options as ... other options. - Denimadept (talk) 09:31, 7 December 2012 (UTC)
- Sadly I don't speak template speak; I'd be terrified of breaking it. Espresso Addict (talk) 14:32, 7 December 2012 (UTC)
How about adding an |id_type=
parameter to change the label, ie
| label8 = {{{id_type|[[National Bridge Inventory#ID numbers|ID number]]}}}
Or if soemone does an AWB run to add the new parameter to US articles, then the default could be ID number (without the link). Thoughts? - Evad37 [talk] 16:56, 27 November 2013 (UTC)
Added id_type parameter, after 1½ months with no objections or discussion - Evad37 [talk] 04:33, 14 January 2014 (UTC)
- I don't speak "template" either. Now to see how this works out. :-) - Denimadept (talk) 20:48, 14 January 2014 (UTC)
Copy edit
The harbour bridge example shows (start-date) where the Infobox example says to use (start date).
One takes ddmonyy to give yy mm dd, the other vice versa. And the date examples used does nothing as it's already in the correct format but then corrupted(?) by the wrong conversion ...
Does the use of (start date) provide a benefit (HTML micro code) that the date in plain text doesn't give? --Dave Rave (talk) 21:10, 16 August 2014 (UTC)
- the benefits of using {{start date}} are listed in the documentation for
{{start date}}
. feel free to fix any inaccuracies or inconsistencies in the documentation for that template, or this template. Frietjes (talk) 14:07, 17 August 2014 (UTC)
map_type map type
Replacing {{Location map}} with |map_type=
sometimes changes the map from a political (?) map to a relief map, as in Anderson Memorial Bridge. Other times, such as in Amtrak Susquehanna River Bridge, it stays with the political (?) map. Why the difference, and does anyone see the inconsistency as a problem? Is there anything I should be doing differently here? ‑‑Mandruss ☎ 12:22, 16 November 2014 (UTC)
- Mandruss, the difference is between Template:Location map USA Maryland and Module:Location map/data/USA Massachusetts. the Maryland template has no relief map, so it fallsback to use the political map. Frietjes (talk) 17:57, 16 November 2014 (UTC)
- Thank you. I will infer that the answers to my second and third questions are no and no. ‑‑Mandruss ☎ 18:19, 16 November 2014 (UTC)
- I see it as a problem. I don't want the map to change. Depending on the situation, the political map may make more sense than the relief map, or vise versa. - Denimadept (talk) 21:43, 16 November 2014 (UTC)
- @Denimadept and Mandruss: if you want the political map, set
|map_relief=
as blank or0
orno
. if you want the relief map, set|map_relief=1
oryes
. if the relief map does not exist, then it won't matter, since it only has one map. Frietjes (talk) 15:18, 17 November 2014 (UTC)- Excellent, @Frietjes:! - Denimadept (talk) 00:08, 18 November 2014 (UTC)
- @Denimadept and Mandruss: if you want the political map, set
- I see it as a problem. I don't want the map to change. Depending on the situation, the political map may make more sense than the relief map, or vise versa. - Denimadept (talk) 21:43, 16 November 2014 (UTC)
- Thank you. I will infer that the answers to my second and third questions are no and no. ‑‑Mandruss ☎ 18:19, 16 November 2014 (UTC)
Namesake
Can a parameter for who a bridge is named for be added to the template? Allen (Morriswa) (talk) 15:48, 13 December 2014 (UTC)
- Allen (Morriswa), added
|named_for=
from template:infobox settlement. Frietjes (talk) 18:43, 13 December 2014 (UTC)
A usefull link
Could someone link ; clearance_below to air draft? Peter Horn User talk 17:08, 6 May 2015 (UTC)
- Already done. Thanks. Alakzi (talk) 17:10, 6 May 2015 (UTC)
- Similarly link |clearance= to air draft, see Gerald Desmond Bridge.There are no doubt many others. Peter Horn User talk 18:56, 6 May 2015 (UTC)
- Case in point: Captain Cook Bridge, Brisbane. Peter Horn User talk 19:51, 6 May 2015 (UTC)
- Caveat! I found this: Laurier Railway Bridge |clearance = AAR structure gauge. Peter Horn User talk 20:43, 6 May 2015 (UTC)
- Ditto Bordeaux Railway Bridge |clearance = AAR structure gauge. Peter Horn User talk 20:53, 6 May 2015 (UTC)
- Caveat! I found this: Laurier Railway Bridge |clearance = AAR structure gauge. Peter Horn User talk 20:43, 6 May 2015 (UTC)
- Case in point: Captain Cook Bridge, Brisbane. Peter Horn User talk 19:51, 6 May 2015 (UTC)
- Similarly link |clearance= to air draft, see Gerald Desmond Bridge.There are no doubt many others. Peter Horn User talk 18:56, 6 May 2015 (UTC)
Infobox bridge/Archive 1 | |
---|---|
Characteristics | |
Clearance above | AAR ? |
- Clarification required. | clearance was eleminated Peter Horn User talk 20:55, 12 May 2015 (UTC)
- I'm a little confused. What would you like me to clarify? Alakzi (talk) 21:06, 12 May 2015 (UTC)
Characteristics | |
---|---|
Clearance above | (above the deck?) AAR structure gauge? |
Clearance below | (?) |
The nomenclature is not consistent. Peter Horn User talk 03:35, 13 May 2015 (UTC)
- There is a problem with "to the bridge deck" which is somewhat ambiguous, if not meaningless, to sailors.
See Goodwill Bridge#Specifications
- Height: Clearance for River Vessels 11.4 to 12.7 metres (37 to 42 feet) from high water level to the bridge deck (same height as Victoria and Captain Cook bridges) Peter Horn User talk 17:14, 14 May 2015 (UTC)
|clearance=
is the old parameter name of|clearance_above=
; they both refer to clearance above the deck. It'll take some time to clean up all transclusions of the infobox. Alakzi (talk) 18:12, 14 May 2015 (UTC)- @Peter: See Category:Articles using Template:Infobox bridge with clearance - I could use some help with cleaning all of these up. We need to determine whether
|clearance=
refers to clearance above or below and change the parameter name accordingly. Alakzi (talk) 01:25, 16 May 2015 (UTC)
- @Peter: See Category:Articles using Template:Infobox bridge with clearance - I could use some help with cleaning all of these up. We need to determine whether
- Ah yes, The captain of a ship, etc. would be interested in knowing how much room is available under the bridge, taking into consideration such factors as tides in the case of seas or high run off in the case of rivers and lakes. Clearance above could refer to clearance above the deck as being synonymous, in the case of truss bridges and others, with structure gauge signifying the maximum size of vehicles or trains, loading gauge, being able to cross. A parameter called overall hight would be interesting for all pilots who would want to avoid flying into the bridge. I may not have time to help because I'm often busy with the usages of template:infobox locomotive etc. Peter Horn User talk 16:18, 20 May 2015 (UTC)
- Btw, I just realized that overall height is covered simply by |height. Peter Horn User talk 01:16, 2 September 2015 (UTC)
- Perhaps "clearance above" could be linked to structure gauge. Peter Horn User talk 01:21, 2 September 2015 (UTC)
duplicate items
I could probably do it, easily enough, but number_of_spans / spans and a couple of others needs to be in the documentation Dave Rave (talk) 00:43, 5 September 2015 (UTC)
Proposed deletion of maintenance Category:Pages using deprecated coordinates format
A maintenance category used for this template, Category:Pages using deprecated coordinates format, is being considered for deletion here. Your input is requested. ~ Tom.Reding (talk ⋅dgaf) 14:34, 16 January 2016 (UTC)
Map marker
I want to be able to specify a map marker. The default red marker is fine for most cases, but I prefer to use the black pog for bridge which are no longer present. How can I do this? See Suffield and Thompsonville Bridge for an example. - Denimadept (talk) 08:38, 8 April 2016 (UTC)
- Denimadept, try using
|map_dot_mark=
Frietjes (talk) 15:41, 7 May 2016 (UTC)- Can we get that documented, please? - Denimadept (talk) 20:20, 4 July 2016 (UTC)
Rail data fields
There appears to be no provision for rail data fields as is the case with Template:Infobox tunnel. Peter Horn User talk 00:47, 9 September 2016 (UTC)
- Such as
| notrack = number of tracks
| gauge = 1,435 mm (4 ft 8+1⁄2 in) standard gauge
| el = or electrification =
Peter Horn User talk 01:30, 9 September 2016 (UTC)
- @Frietjes: This info is relevant in the following:
- Laurier Railway Bridge
- Bordeaux Railway Bridge
- Victoria Bridge (Montreal)
- Quebec Bridge
and others
In addition Template:Infobox tunnel has the field | lanes = relevant in - Victoria Bridge (Montreal)
- Quebec Bridge
and others
Peter Horn User talk 14:18, 9 September 2016 (UTC)
- Peter Horn, we can definitely add this, but will wait a day or two to see if there are any objections. Frietjes (talk) 14:35, 9 September 2016 (UTC)
- Noted. Peter Horn User talk 15:21, 9 September 2016 (UTC)
- @Frietjes: So far no objections. Peter Horn User talk 00:24, 12 September 2016 (UTC)
- Peter Horn, added see documentation for example. Frietjes (talk) 13:41, 12 September 2016 (UTC)
- @Frietjes:I don't see the additional fields in the "copy and paste" list yet. Can I now add the fields in the existing infoboxes in the way that I proposed them? Peter Horn User talk 13:49, 12 September 2016 (UTC)
- Peter Horn, search the documentation page for "electrification" and you will find them. the parameters in the cut-and-paste are in the order that they appear in the infobox. Frietjes (talk) 13:51, 12 September 2016 (UTC)
- @Frietjes:I don't see the additional fields in the "copy and paste" list yet. Can I now add the fields in the existing infoboxes in the way that I proposed them? Peter Horn User talk 13:49, 12 September 2016 (UTC)
- Peter Horn, added see documentation for example. Frietjes (talk) 13:41, 12 September 2016 (UTC)
- @Frietjes: So far no objections. Peter Horn User talk 00:24, 12 September 2016 (UTC)
- Noted. Peter Horn User talk 15:21, 9 September 2016 (UTC)
- @Frietjes:Thanks. Just one more. In the case of carriage ways, a field for the number of lanes. In addition, I have used clearance above as synonymous with structure gauge. That is perhaps not quite right. Peter Horn User talk 14:03, 12 September 2016 (UTC)
- Peter Horn, added
|structure_gauge=
, will add|lanes=
shortly. Frietjes (talk) 14:12, 12 September 2016 (UTC)- @Frietjes: "Number of lanes", a link, would be nice. Peter Horn User talk 17:10, 12 September 2016 (UTC)
- Peter Horn, Template:Infobox tunnel doesn't link this common word. Frietjes (talk) 17:12, 12 September 2016 (UTC)
- @Frietjes:You are right, but it wouldn't do any harm to link lane in both templates. In addition, in the case of the tunnel template gives "height" as the clearance above the roadway. Peter Horn User talk 17:52, 12 September 2016 (UTC)
- Peter Horn, go ahead, but someone may delink it as a COMMONWORD. Frietjes (talk) 22:31, 12 September 2016 (UTC)
- @Frietjes:You are right, but it wouldn't do any harm to link lane in both templates. In addition, in the case of the tunnel template gives "height" as the clearance above the roadway. Peter Horn User talk 17:52, 12 September 2016 (UTC)
- Peter Horn, Template:Infobox tunnel doesn't link this common word. Frietjes (talk) 17:12, 12 September 2016 (UTC)
- @Frietjes: "Number of lanes", a link, would be nice. Peter Horn User talk 17:10, 12 September 2016 (UTC)
- Peter Horn, added
- @Frietjes: The field "|clearance =" shows as "clearance above". I assume that this is the clearance from the deck to the underside of the lowest structural member across the deck. Correct me if I be wrong. Time here is 20:42. I'll look at this tomorrow. Peter Horn User talk 00:27, 13 September 2016 (UTC)
- Peter Horn, there are two clearance parameters,
|clearance_above=
and|clearance_below=
. uses of|clearance=
are being tracked in Category:Articles using Template:Infobox bridge with clearance presumably either (a) for inspection, or (b) for parameter replacement since it's ambiguous. for|clearance_above=
, I would say this is as you described, basically what restricts the height of vehicles which may pass over the bridge. Frietjes (talk) 13:33, 13 September 2016 (UTC)- @Frietjes: So then
|clearance_above=
should be linked to structure gauge as well, like this|Structure gauge=clearance_above
? Peter Horn User talk 21:53, 14 September 2016 (UTC)- Peter Horn, from the article, structure gauge = "minimum height and width", so I would think that
|clearance_above=
is the "minimum height" (i.e., height but not width). someone at WT:WikiProject Trains would probably know for sure. Frietjes (talk) 21:56, 14 September 2016 (UTC)
- Peter Horn, from the article, structure gauge = "minimum height and width", so I would think that
- @Frietjes: So then
- Peter Horn, there are two clearance parameters,
- @Frietjes: That should have read
|clearance_above=
. In Template:infobox tunnel the corresponding parameter is|height=
In addition, if|width=
refers to the clear or net width of the bridge and not to the over-all width then we could possibly have|width=
Peter Horn User talk 22:17, 14 September 2016 (UTC)
Clearance below
@Frietjes: Hello, I just realized that | Clearance_below is not really synonymous with air draft. Clearance_below is really air draft plus Engineering tolerance#Clearance (civil engineering). Also, in the case of overpasses the clearance_below means the distance from the underside of the overpass to the pavement or the top of rail below. Peter Horn User talk 01:15, 10 October 2016 (UTC)
Earthquake standards
How about including a field denoting how bridges rank with regards to current seismic standards? Most municipalities compile listings of these, it'd be great to increase the visibility. --Hooperbloob (talk) 20:08, 18 March 2017 (UTC)
Carries field
Currently the Carries field is listed to contain what mode uses it, i.e. trains, motor vehicles, pedestrians or bicycles as applicable. Given that just about all railway lines and many major roads have articles, would it be of more value to include the relevant wikilinked articles instead, as done at Golden Gate Bridge, Menangle Railway Bridge and Mooney Mooney Bridge in this field? Avgas7 (talk) 03:52, 18 April 2017 (UTC)
"Construction begin"
The label "Construction begin" is not very good grammar. Unless there are any objections, I will change it to "Construction start", without renaming the parameter, in a few days time. Thryduulf (talk) 13:11, 28 April 2017 (UTC)
- With no objections raised I've now made this change. Thryduulf (talk) 13:16, 2 May 2017 (UTC)
Embedded infobox modules
I'd like to be able to embed Infobox NRHP within Infobox bridge for bridges listed on the National Register of Historic Places; does anyone know how to edit this template so that it can take embedded infoboxes? Many thanks to anyone who can help!-Bryanrutherford0 (talk) 15:09, 26 October 2017 (UTC)
- Bryanrutherford0, at the moment, the best way to do this is through the
|extra=
parameter. Frietjes (talk) 16:31, 26 October 2017 (UTC)- Ah, thank you! The documentation on the other end only mentioned the parameters
|module=
and|embedded=
; I'll edit there to mention "extra" as another likely label. Much appreciated!-Bryanrutherford0 (talk) 17:32, 26 October 2017 (UTC)
- Ah, thank you! The documentation on the other end only mentioned the parameters
"Independent Design Verifier" to be added to infobox
On infrastructure projects, especially large-scale ones, there is always an independent design verifier that works for the client, alongside the main design company, that has the role of checking and coming up with suggestions on how the design can be corrected or improved. This is a very important role in the design process. I suggest adding a new item to the infobox called "Independent Design Verifier", with the parameter "|verifier". — Preceding unsigned comment added by Mainsubject (talk • contribs) 10:01, 15 July 2018 (UTC)
Road number or Rail line name
There is no parameter that I can see which should be used to write Road number or Rail line name. Some usage of the template uses the parameter "carries" for this, but it is against the documentation advice.--BIL (talk) 17:01, 20 July 2018 (UTC)
Localize maps
The map of the whole state with a little dot doesn't seem as useful as a map of the local metropolitan area which then has the dot. See for example Bridge to Nowhere (San Gabriel Mountains). -Inowen (nlfte) 06:40, 20 September 2018 (UTC)
Number of tracks
How many tracks has a bridge with a gauntleted track? One or two? My specific case is Prince of Wales Bridge. On google streetview you can see the gauntleted track. --Nobelium (talk) 20:45, 24 July 2017 (UTC)
- Wait, the bridge is indeed just one track with strange additional "rails" in between. But the general question remains. --Nobelium (talk) 15:48, 25 July 2017 (UTC)
- looks like a rail with a maintenance track in between ....
but still, what about a two into almost the same space as one gauntlet ? Dave Rave (talk) 07:45, 17 July 2018 (UTC) - a gauntleted track could be two tracks, interlinking, with points, into a single set of rails, or, two tracks, crossing without points, into two tracks adjacent but not one, four rails, to save the wear and tear on the points, and extra the interlocking Dave Rave (talk) 00:01, 27 October 2018 (UTC)
- looks like a rail with a maintenance track in between ....
Location vs Locale
I'd like to change the label from Locale to Location. Location to me is much clearer. Says "this is where the bridge is located". Locale can also mean the style for a particular location. To be clear, {{{locale}}}
would still work...--Zackmann (Talk to me/What I been doing) 17:32, 26 October 2018 (UTC)
- when does locale infer a style ? Dave Rave (talk) 23:57, 26 October 2018 (UTC)
- @Dave Rave: Locale (computer software) --Zackmann (Talk to me/What I been doing) 00:03, 27 October 2018 (UTC)
- that's a little application specific to be a generic stumbling block on a location Dave Rave (talk) 00:32, 27 October 2018 (UTC)
- @Dave Rave: maybe its just me, but I do software development for a living. I've always heart "locale" to mean to style and customs of a location. But if there is an objection to the change than fine. Literally every other infobox I've looked at on here uses "location" so... --Zackmann (Talk to me/What I been doing) 00:39, 27 October 2018 (UTC)
- okay, back to front, a location would be specific-ish but a locale 'could' infer more than just a location. not sure if relevant, or necessary, but ... Dave Rave (talk) 00:51, 27 October 2018 (UTC)
- @Dave Rave: maybe its just me, but I do software development for a living. I've always heart "locale" to mean to style and customs of a location. But if there is an objection to the change than fine. Literally every other infobox I've looked at on here uses "location" so... --Zackmann (Talk to me/What I been doing) 00:39, 27 October 2018 (UTC)
- that's a little application specific to be a generic stumbling block on a location Dave Rave (talk) 00:32, 27 October 2018 (UTC)
- @Dave Rave: Locale (computer software) --Zackmann (Talk to me/What I been doing) 00:03, 27 October 2018 (UTC)
Mapframe
I've added {{Infobox mapframe}} to the sandbox, so that it will display whenever there is no location map. Although I'm a template editor and could add it to the main template immediately, I'll wait a few days to see if anyone has concerns about its implementation. Jc86035 (talk) 09:02, 5 December 2018 (UTC)
- Jc86035, for me, Dumbarton Bridge (California) has a repeated caption and a large blank where the map frame would be. Frietjes (talk) 15:55, 13 December 2018 (UTC)
- @Frietjes: Fixed for transclusions using
|map_image=
. The blank is phab:T158657 (open since February 2017) and the server should handle it in a few hours, although I didn't anticipate it being this bad. Jc86035 (talk) 15:59, 13 December 2018 (UTC) - For what it's worth, Tsing Ma Bridge shows what it's supposed to look like. The image generation seems to require a page save action (no content change needed). Jc86035 (talk) 16:04, 13 December 2018 (UTC)
- Jc86035, how do we get rid of the stray caption in Jacob Beltzhoover? seems like we should only add the caption if the map exists. Frietjes (talk)
- @Frietjes: I've removed the default caption. I think checking for P625 would be sufficient but it's not clear if having the caption is useful (I only did it for consistency). Jc86035 (talk) 16:20, 13 December 2018 (UTC)
- Jc86035, how do we get rid of the stray caption in Jacob Beltzhoover? seems like we should only add the caption if the map exists. Frietjes (talk)
- @Frietjes: Fixed for transclusions using
- Jc86035: How do we fix Great Belt Fixed Link? There are two mapframe maps, and both point to the same place. The best situation would be if the map for the East bridge pointed to the centre of the East bridge, and the map for the West bridge pointed to the centre of the West bridge. Thanks! Plastikspork ―Œ(talk) 13:43, 2 January 2019 (UTC)
- It looks like Module:Infobox mapframe does not accept
|coordinates=
as an override to the wikidata-provided coordinates for the article's subject. Pinging Evad37, who might be able to help and/or explain. – Jonesey95 (talk) 15:09, 2 January 2019 (UTC)- @Jonesey95 and Plastikspork: I've created separate Wikidata items for the two bridges (and for the tunnel). This has the added bonus of allowing the OpenStreetMap elements to display on the map, which should happen within a few days. (I could have just used
|mapframe_lat=
and|mapframe_long=
, although I decided to use Wikidata instead.) Jc86035 (talk) 15:22, 2 January 2019 (UTC)- Creating/using separate Wikidata items would have been my suggestion too. The other option would be to turn off the maps using
|mapframe=no
and use {{maplink}} directly, which would allow more complicated/customised maps to be displayed. - Evad37 [talk] 01:38, 4 January 2019 (UTC)
- Creating/using separate Wikidata items would have been my suggestion too. The other option would be to turn off the maps using
- @Jonesey95 and Plastikspork: I've created separate Wikidata items for the two bridges (and for the tunnel). This has the added bonus of allowing the OpenStreetMap elements to display on the map, which should happen within a few days. (I could have just used
- It looks like Module:Infobox mapframe does not accept
Template-protected edit request on 20 August 2019
![]() | This edit request to Template:Infobox bridge has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
The documentation lists the field 'open' before 'inaugurated' and this makes sense to me as typically the maintaining agency will open the bridge whenever the safety inspection concludes successfully and some time later the local government will arrange a ceremonial opening at their convenience. However when the template is parsed the Inaugurated date is displayed in the article infobox above the Opened date. My request is that the template source code be changed to display them in the reverse order in keeping with the documentation, with the Opened date above the Inaugurated date. — ⚞🐈ℛogueScholar🗨₨Talk⚟ 12:44, 20 August 2019 (UTC)
Done chi (talk) 14:00, 22 August 2019 (UTC)
Fix the coordinates with a bot?
I feel bad, but when the maps/coordinates were introduced to the infobox it has caused a headache in the top right corner of overlapping coordinate templates. I am an admin, but I'm a meh coder at best, so if we can send a bot to cleanup the mess made by. Mitch32(Fame is a four letter word.) 19:49, 10 November 2019 (UTC)
- Mitchazenia: When you are reporting a problem, it is always helpful to link to at least one page that demonstrates the problem. I just checked eight of the 5,000+ articles that use this infobox, and I did not see any problems. This infobox has accepted coordinates for many years. – Jonesey95 (talk) 23:53, 10 November 2019 (UTC)
- Look at the bridges over the Delaware River. Portland–Columbia Toll Bridge, Darlington's Bridge at Delaware Station. I have had to fix this in a couple others. There has to be more. Mitch32(Fame is a four letter word.) 20:35, 13 November 2019 (UTC)
- Thanks for the links. I see what you mean. It looks like Rehman added the ability for this template to retrieve coordinates from Wikidata, and when there are also coordinates in the article but outside of the infobox, two sets of coordinates are displayed. Normally, when there are coordinates in the infobox and in the article, the article will display a red error message and be placed in Category:Pages with malformed coordinate tags. It looks like bringing in coordinates from Wikidata does not trigger this error. – Jonesey95 (talk) 01:02, 14 November 2019 (UTC)
- Ah. Wikidata stuff is a bit over my head. Even though I was just at WikiConference North America, which is why my response was delayed, i still can't grasp it. Mitch32(Fame is a four letter word.) 02:56, 14 November 2019 (UTC)
- Thanks for the links. I see what you mean. It looks like Rehman added the ability for this template to retrieve coordinates from Wikidata, and when there are also coordinates in the article but outside of the infobox, two sets of coordinates are displayed. Normally, when there are coordinates in the infobox and in the article, the article will display a red error message and be placed in Category:Pages with malformed coordinate tags. It looks like bringing in coordinates from Wikidata does not trigger this error. – Jonesey95 (talk) 01:02, 14 November 2019 (UTC)
- Look at the bridges over the Delaware River. Portland–Columbia Toll Bridge, Darlington's Bridge at Delaware Station. I have had to fix this in a couple others. There has to be more. Mitch32(Fame is a four letter word.) 20:35, 13 November 2019 (UTC)