Template talk:Infobox military structure

From Wikipedia, the free encyclopedia
Jump to: navigation, search
WikiProject Military history
MILHIST This template is within the scope of the Military history WikiProject. If you would like to participate, please visit the project page, where you can join the project and see a list of open tasks. To use this banner, please see the full instructions.
Temp Templates do not require a rating on the quality scale.

Contents

[edit] New parameters

Perhaps a field for noting if a structure was captured, and by whom? --Loopy e 03:58, 4 February 2006 (UTC)

I've added a "Notable battles" field (as in the unit infobox); presumably any notable sieges/captures can be indicated there. —Kirill Lokshin 16:17, 4 February 2006 (UTC)
I think primary construction materials would be a good one considering could cover things like wooden forts.
There are some additional parameters I'd like to have, but they're fairly specific. For defensive lines I'd like to see # of emplacements/bunkers and length, but that wouldn't make much sense on a castle. Oberiko 05:13, 9 February 2006 (UTC)
I've added a "materials" field; I'm not sure if we'd want to have any extensive breakdown of emplacements in the infobox, given how complex that could get. —Kirill Lokshin 14:24, 9 February 2006 (UTC)

[edit] additional related infobox

What about an infobox relating just to a base or facility? This infobox seems more geared to a building or structure - something that could be part of a base, but not all of a base. Thoughts, comments? - NDCompuGeek 06:55, 5 March 2007 (UTC)

It's been used quite well for an entire base, too; it's just that a lot of parameters don't get used, in that scenario. Are there additional fields that you'd like to see added? Kirill Lokshin 10:13, 5 March 2007 (UTC)
What about the PIN (Permanent Installation Number), ILC (Installation Location Code), Installation Location Kind (ILK), or other types of facility identification? (See http://www.airforcebase.net/inst_101.html for further information.) Just a suggestion.... - NDCompuGeek 00:16, 9 March 2007 (UTC)
It's not a problem to add a field for them, but is there a generic term we could used for the various types here? Kirill Lokshin 02:34, 9 March 2007 (UTC)
Geez, making me think! :-) I was thinking of something like "locationcode" or "facilitycode" or the like. I believe that the ILC nomenclature is U.S. military-wide, not just for the Air Force, so it would be applicable to all US military branches. Not too sure about the military nomenclature for other countries.... Another item that I would find useful is map coordinates, in addition to geographic location (possibly using {{coor dms}} as a basis). - NDCompuGeek 07:04, 9 March 2007 (UTC)
Okay, I've added a |code= field to the box; does that work? Kirill Lokshin 13:32, 15 March 2007 (UTC)

←←(unindent conversation)←← That should - thanks. I've made a few calls to Minot AFB for further information about this location code. Hopefully they can point me to the AFI that has more information about it. They only other thing I can think to add is the map coordinates thingy - maybe either inline with the rest of the information or put it up to like it is now (as a separate function instead of being built into this template though). Just a suggestion.... And, again, thanks for incorporating the "code" into the infobox! - NDCompuGeek 19:34, 15 March 2007 (UTC)

Okay, given the lack of objections, I've gone ahead and added a |coordinates= field. Kirill Lokshin 23:25, 25 March 2007 (UTC)

[edit] microformat

I'd like to add the hCard microformat (see WP:UF for background) to this template, To do this, I need to add class="vcard" to the top level container; but in this case, that's in another template, which also applies to other infoboxes, where it wouldn't be relevant. How can I add that class to this infobox only? Andy Mabbett 13:28, 12 May 2007 (UTC)

See {{Infobox Military Person}}. ;-)
(I've added the vcard class, but I have no idea what others may be necessary; so you'll need to figure that out.) Kirill Lokshin 17:52, 12 May 2007 (UTC)
Thank you. I've added the rest. Andy Mabbett 18:30, 12 May 2007 (UTC)

[edit] Open to public

Added an "open to the public" field following a discussion at Wikipedia:WikiProject Scottish castles. Thanks, Edward Waverley 12:15, 22 May 2007 (UTC)

Looks good. I've changed the parameter name to use underscores rather than dashes, as that's the more common convention for such things; hopefully that didn't break anything. Kirill Lokshin 14:15, 22 May 2007 (UTC)
Thanks Kirill, I'm always nervous about editing templates but it seems to work OK. Edward Waverley

[edit] Location map?

Would it be possible to add the option of a location map into this template? Template:Infobox Historic building has this function, using the Template:Location map set up (example here), and I think this would be really helpful for military buildings too. Presumably the relevant bits can be copied from that template to this, but I've no idea how to do it. Can anyone help? Thanks, Jonathan Oldenbuck (talk) 08:44, 21 July 2008 (UTC)

OK, I think I worked it out. I hope I didn't break anything, feel free to post rude messages on my talk page if I did :) Jonathan Oldenbuck (talk) 12:21, 21 July 2008 (UTC)

Could someone have a look at Moorish Castle please? I can't get the latitude and longitude parameters to get the pointer within the map. Thanks, --Gibmetal 77talk 23:43, 28 September 2008 (UTC)

[edit] Alternative name field

Would anyone object to the addition of a "native name" field, so that, in articles like Frankopan Castle, the second version of the name can be in a separate table row, marked up in the appropriate language, rather than in the table header? See, for example, the native_name and native_name_lang fields in {{Infobox settlement}}. Andy Mabbett (User:Pigsonthewing); Andy's talk; Andy's edits 10:01, 19 July 2009 (UTC)

Well, I have no problem with adding a separate field in principle, but I'm not quite sure where you wanted to position it. Are you thinking of a labeled row (i.e. one below the image fields), or just a secondary "header" row at the top (either with or without actual table-header markup). Kirill [talk] [pf] 12:05, 19 July 2009 (UTC)
I have no preference, and am open to suggestions. Andy Mabbett (User:Pigsonthewing); Andy's talk; Andy's edits 15:37, 19 July 2009 (UTC)

[edit] Coordinate duplication

Please note This Bot request. Thank you. Andy Mabbett (User:Pigsonthewing); Andy's talk; Andy's edits 10:27, 19 July 2009 (UTC)

[edit] Merger

Any reason why Template:Infobox building couldn't be updated to include the parameters of this template? Its just confusing. A lot of castles use Template:Infobox Historic building. I would rather castles consistently used one infobox not many different ones. ♦ Dr. Blofeld 21:28, 19 March 2011 (UTC)

Further discussion is taking place at WT:MILHIST#Infobox military structure. Kirill [talk] [prof] 00:03, 20 March 2011 (UTC)
The discussion at Wikipedia_talk:WikiProject_Military_history/Archive_100#Infobox_military_structure did not lead to any steps to make a merge, so I request an admin to remove the merge template. Debresser (talk) 08:58, 22 November 2011 (UTC)
Yes check.svg Done Anomie 05:14, 24 November 2011 (UTC)

[edit] Coordinates

The use of the |coordinates= parameter allows a custom {{coord}} template to be used, but won't produce a pushpin map. Use of separate |latitude= and |longitude= produces a pushpin map, but won't allow {{coord}} to be customised for e.g. the coordinates region. If |latitude= and |longitude= are used in conjunction with |coordinates= containing a {{coord}}, this puts the page into the error report Wikipedia:Database reports/Articles containing overlapping coordinates.

My proposal is to amend the existing {{#if:{{{coordinates|}}}|{{{coordinates}}}|{{coord|{{{latitude}}}|{{{longitude}}}|type:landmark|display=inline,title}}}} to become {{#if:{{{coordinates|}}}|{{{coordinates}}}|{{coord|{{{latitude}}}|{{{longitude}}}|type:landmark{{#if:{{{coord_region|}}}|_region:{{{coord_region}}}}}|display=inline,title}}}} which will add a parameter |coord_region=, which would be used in conjunction with |latitude= and |longitude=. The pushpin map will be generated, and the coordinates link will incorporate the region code. --Redrose64 (talk) 15:44, 29 December 2011 (UTC)

Personal tools
Namespaces
Variants
Actions
Navigation
Interaction
Toolbox