Template:Infobox dual roller coaster/doc

This template is for roller coasters with two tracks. For single-tracked coasters, use Infobox roller coaster.

Additional locations
See the guidelines for the extend parameter for information on how to add information for additional locations.

name
The coaster's full, official name. Should not be linked.

image
The primary picture of the coaster. Use a full tag.

caption
The caption for the picture.

location
The park in which the coaster is located. Use the full, properly capitalized name of the park, and DO NOT link it. It will be linked automatically.

section
The section of the park in which the coaster is located. Should not be linked, a section link will be automatically generated using the location parameter. For example, a location of Six Flags Great Adventure and a section of Golden Kingdom will make this link: Golden Kingdom.

coordinates
Use coord, with display=inline,title.

type
The primary type, Steel or Wood. This should not be ANYTHING else and should NOT be linked. It will be linked automatically, and the coaster will be added to the appropriate category: Category:Steel roller coasters or Category:Wooden roller coasters.

type2
The secondary type. It can be any one of the following, or another type, if appropriate: This parameter should NOT be linked. It will be linked automatically and add the coaster to a category for that type. For example, "Inverted" will link to Inverted roller coaster and add the coaster to Category:Inverted roller coasters.
 * 4th Dimension
 * Bobsled
 * Duelling
 * Enclosed
 * Floorless
 * Flying
 * Indoor
 * Inverted
 * Launched
 * Racing
 * Shuttle
 * Side friction
 * Spinning
 * Stand-up
 * Suspended
 * Virginia Reel
 * Wild Mouse

Note: This is NOT the track layout. Out and Back, Twister, Moebius Loop, Terrain etc. do not belong in this parameter, they have their own. Also, the height category (Megacoaster, Gigacoaster, Stratacoaster) doesn't belong here, it will be calculated from the height.

type3
This is exactly the same as type2. It should be used when more than one secondary type applies. For example, Dueling Dragons would be a Steel (type) Dueling (type2) Inverted (type3) coaster.

status
The current status of the coaster. Could be Under Construction (with expected opening date), Under Refurbishment (AKA being fixed), SBNO (Standing But Not Operating), Testing, Closed, or, of course, Operating.

opened
The first day on which the coaster was open to the public. Many coasters have a "soft opening" before their media day and official opening, in this case the date of the soft opening should be used. Use start date.

closed
The last day of operation. Do not use this if it is just closed for seasonal maintenance. Use end date.

extend
This parameter allows information about the same roller coaster (either relocation or mirror copy) to be added within the same infobox. It relies on Template:Infobox roller coaster/extend which contains all of the "Primary location" parameters described above. Full syntax is shown in the Additional locations section above. One or more of these templates can be concatenated together.

manufacturer
The full, official name of the coaster's primary manufacturer. This should NOT be linked, it will be automatically linked and it will add the coaster to a category for that manufacturer.

designer
The coaster's designer, if RCDB lists one. This will not be automatically linked or add the coaster to a category.

model
The coaster's model, as listed on RCDB. This will often, but not always, be the same as the secondary type. It will not be automatically linked, it should only be linked if it differs from the secondary type.

track
The track layout based on RCDB. This could be something like Out and Back, Twister, Moebius Loop, Terrain etc. Because track layouts can vary greatly from the standard ones, this parameter will not be automatically linked and will not automatically add the coaster to a category.

lift
The type of lift or launch system that this coaster uses. The most common will be a chain lift hill, but other common ones are linear motor launch track, cable lift hill, hydraulic launch track, etc. There is no automatic linking or categorizing for this parameter, please link as appropriate.

name1, name2
The names of the coaster's left and right tracks. If they don't have names, use "Left" and "Right".

height1_ft, height2_ft, drop1_ft, drop2_ft, length1_ft, length2_ft
All of the 1's are for the left track, all the 2's are for the right. Based on RCDB. All of these parameters must use values that are entirely numeric, and must be expressed in feet (if feet and inches are given, use decimals instead). The SI values of these parameters (meters and km/h, respectively) will automatically be calculated and included – this is why these parameters must be entirely numeric. For example, a height value of "230" must be used instead of "230 ft" or anything similar. Additionally, the height parameter will be used to automatically place the coaster in the appropriate height category: Megacoaster, Gigacoaster, or Stratacoaster.

speed1_mph, speed2_mph
All of the 1's are for the left track, all the 2's are for the right. All of these parameters must use values that are entirely numeric, and must be expressed in miles per hour. Based on RCDB.

inversions1, inversions2
1 for left track and 2 for right track. The number of times riders are turned upside down during the ride. Based on RCDB.

duration1, duration2
1 for left track and 2 for right track. Based on RCDB.

angle1, angle2
1 for left track and 2 for right track. The maximum vertical angle, in degrees, attained by the track. This will usually, but not always, be the angle of the first drop. Inversions are not counted – if they were, for example, any coaster with a loop would have an angle of 90 degrees, as the track attains this angle twice as part of the loop. Based on RCDB.

acceleration1, acceleration2
1 for left track and 2 for right track. The rates of acceleration of each track. Should be expressed in the form "X – Y mph in Z sec". This will normally only be used for launched coasters. Based on RCDB.

gforce1, gforce2
1 for left track and 2 for right track. The maximum G force that riders experience during the ride. Based on RCDB.

capacity
The maximum number of guests that the entire coaster (both tracks) can accommodate in one hour. Based on RCDB.

cost
The amount of money the coaster cost to build, expressed in the currency of the country where the coaster is located.

restriction_ft, restriction_in, restriction_cm
Height restriction, i.e. "You must be this tall to ride." Either All values must be entirely numeric. The template will automatically convert the values and display them in feet and inches and in centimeters.
 * 1) give the height in feet and (or) inches using,  or
 * 2) give the height in centimeters using

trains, carspertrain, rowspercar and ridersperrow
Must be used together. If one of the fields is missing none of the information entered will be displayed. Must contain only numeric characters. Most of these statistics can be found near the bottom of an RCDB page.

custom_label_1, custom_value_1, custom_label_2, custom_value_2, etc
If there is a general statistic that is missing from the above categories, include it here. The label fields will appear in bold on the left while the values will appear normally on the right.

virtual_queue_name, virtual_queue_image, virtual_queue_status
Use these fields if there is a virtual queuing system available. The name parameter is used to describe what it is (e.g. Disney's Fastpass, Universal Express, Dreamworld's Q4U). The status field should read "available" if the virtual queuing system is available. The image parameter should contain the name without the or  tag. Examples include:
 * Universal express availability icon.JPG
 * Fastpass availability icon.svg
 * Dreamworld Q4U logo.png

single_rider, accessible, transfer_accessible
Include this field followed by the word "available" if any of these apply to the attraction. "accessible" refers to Wheelchair Accessibility. "transfer_accessible" means riders must transfer from wheelchair.

rcdb_number
The number in the URL (not the full URL) of the coaster's entry at the Roller Coaster Database. For example, Kingda Ka's RCDB page is http://rcdb.com/2832.htm so the RCDB Number for Kingda Ka is 2832.

year, manufacturer-category
These two parameters are not displayed, they are only used for adding categories to the article, as described below.

Article categories (visible)
Any article containing this template is automatically added to additional categories based on the following parameters:
 * status
 * if "announced" add Category:Proposed roller coasters
 * if "under construction" add Category:Proposed roller coasters


 * year
 * if defined add, such as Category:Roller coasters introduced in 2001


 * location
 * if "Portable" add Category:Portable roller coasters


 * type
 * if "Steel" add Category:Steel roller coasters
 * if "Wood" add Category:Wooden roller coasters
 * if "Hybrid" add Category:Hybrid roller coasters


 * type2
 * if defined add, such as Category:Inverted roller coasters
 * if equal to "dueling" or "racing", the article won't be added to Category:Dual-tracked roller coasters, as that category would be redundant


 * type3
 * if defined add, such as Category:Dueling roller coasters
 * if equal to "dueling" or "racing", the article won't be added to Category:Dual-tracked roller coasters, as that category would be redundant


 * manufacturer
 * manufacturer-category
 * if defined add, such as Category:Roller coasters manufactured by Bolliger & Mabillard


 * height1
 * height2
 * if 200-299 add Category:Hypercoasters
 * if 300-399 add Category:Gigacoasters
 * if 400-499 add Category:Stratacoasters

Tracking categories
Hidden maintenance/tracking categories which may be added to articles using this infobox:
 * – if the coordinates parameter is empty or missing
 * – if any of the following parameters are defined:
 * height1 – deprecated, use height1_ft or height1_m
 * drop1 – deprecated, use drop1_ft or drop1_m
 * length1 – deprecated, use length1_ft or length1_m
 * speed1 – deprecated, use speed1_mph or speed1_km/h
 * height2 – deprecated, use height2_ft or height2_m
 * drop2 – deprecated, use drop2_ft or drop2_m
 * length2 – deprecated, use length2_ft or length2_m
 * speed2 – deprecated, use speed2_mph or speed2_km/h
 * sitearea – removed, use sitearea_sqft or sitearea_sqm
 * restriction – removed, use restriction_ft / restriction_in or restriction_cm