# வார்ப்புரு:Route diagram template



The **route diagram templates** encompass a main container, named or , and its auxiliary templates, most of them having BS (German: BahnStrecke) at the root of their name. This system provides a uniform layout for route-map es, mainly for railway lines but also for other modes of transport such as . Such a map is built as a stack of rows, whose most significant part is a cell lining up one or several square icons. There are more than 3,000 of these elementary pictograms. Several methods are provided to add text to each row and comments to individual graphic cells.  

## Structure used before 2011

Before the creation of (in June 2011), the construction of a stand-alone map required several templates:  
- 
- and
- ,

as shown in the diagram to the . Currently (2016), this format is still used in many maps. However, this format is deprecated and only the template, which employs identical syntax, should be used as global container. The more efficient template should be considered when creating new diagrams.  

## Standalone map container
<dl>  
<dt></dt>  
<dd><pre>  

</pre></dd>  
<dt></dt>  
<dd><pre>  

</pre></dd>  
</dl>  

Template acts as a container for a stack of BSn, BSn-2 templates (described below), each of them describing a row of the resulting structure. This stack is given to the template as the value of the parameter. Beside this stack of row describers, various parameters can be given to describe the global behavior of the resulting map. They are:  

Note re **width**: No default value because it will void the tw parameter in the BSn row template which is applied to override the text column width of BSn row collapsible section.  

### Differences between and
| cellspacing="0" cellpadding="0" |  |  |  |  |  |  |  |  |
| --- | --- | --- | --- | --- | --- | --- | --- | --- |
| &#124; | Margin | &#124; | Right Text | &#124; | Right Text2 | &#124; | Comment | }} |

| &#124; | Left Text | &#124; | Right Text | &#124; | Left Text2 | &#124; | Right Text2 | &#124; | Comment |
| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
|<div>  
| **~~** | **~~** | **~~** | **~~** | **~~** | **~~** | } |
| --- | --- | --- | --- | --- | --- | --- |
---
</div>  
|-  
! scope="row" | Icon separator  
| <code></code>  
| <code>\</code>  
|-  
! scope="row" | Overlays  
| <code>&#124;O=</code>*icon*  
| <code></code>*icon*  
|-  
! scope="row" | Text column separator  
| <code></code>  
| <code>~~</code>  
|}  

- **See the template documentation for more information.**
- If you are creating table from scratch rather than by using templates, the vertical bar <code style=color:red></code> – which is heavily used in Wiki table syntax – must be replaced by <code style=color:red></code>. For example, <code style=color:red>&#123;&#124;</code> is coded as <code style=color:red></code>, and <code style=color:red>&#124;-</code> as <code style=color:red></code>. Otherwise, the presence of the bar will corrupt the structure of the template and following article content. This is because when processing a template, the bar functions as a parameter separating entries, which overrides other functions.
- When a visual separator is desired in text fields, the Unicode Box Drawing character <code style=color:red>┃</code> should be used. (It is visually identical to the vertical bar, but ignored by Wiki markup.) This character can be coded in HTML by <code style=color:red>&amp;#2503;</code>. In Microsoft Windows it can be input directly from the keyboard by holding down , followed by on the numeric keypad; or the sequence .

### Diagrams inside Infobox rail line templates
If an editor wishes to place an RDT inside an instead of having it stand alone, it is recommended that the template be used instead of direct transclusion in order to prevent the diagram from "breaking apart". A complete explanation is at Template:Infobox rdt/doc.  

### Transcluding map in other infoboxes
Besides standalone BS-map, row templates can be transcluded in other infobox templates such as or . The map syntax by BS row templates needs to be written in a separate template page and then transcluded in the said infobox and usually requires the help of other templates.  

## rows with icons and text
The real meat of designing the map are the templates BS and BS-2. Here **BS** is the German abbreviation of **B**ahn**s**trecke for *stretch of track*, and the number indicate how many horizontal icons are put side by side to form the required picture. Templates BS and BS-2 differ by the number of text parameters that are given after the icon names. We have:  
| &#124; | Margin | &#124; | Right Text | &#124; | Right Text2 | &#124; | Comment | }} |
| --- | --- | --- | --- | --- | --- | --- | --- | --- |
| and&nbsp;  
| &#124; | Left Text | &#124; | Right Text | &#124; | Left Text2 | &#124; | Right Text2 | &#124; | Comment |
| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
|}  

Both kind of templates result in a row made of four cells (and, at the end, in a <code></code> structure containing four <code></code> structures). However, these structures are not the same for the BS and the BS-2 templates: they cannot be mixed in the same map.  

### BS row templates
When >1, the unnamed parameters describing the text areas are shifted to make way for extra icon grids sequentially. Therefore, the unnamed (sequential) parameters of , , are as follows:  

| Icon ID | &#124; | Margin | &#124; | Right Text | &#124; | Right Text2 | &#124; | Comment | }} |
| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |

| Icon 1 ID | &#124; | Icon 2 ID | &#124; | Margin | &#124; | Right Text | &#124; | Right Text2 | &#124; | Comment | }} |
| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |

| Icon 1 ID | &#124; | Icon 2 ID | &#124; | Icon 3 ID | &#124; | Margin | &#124; | Right Text | &#124; | Right Text2 | &#124; | Comment | }} |
| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |

These parameters are used to build four columns as follows:  

| **1..** | **Icon ID** the name of the icons that will be put side by side to form the first column of the map. The result is centered, allowing to mix BSn with various values of . For no icon to be shown leave blank (or use ). |  |
| --- | --- | --- |
| **+1** | **Margin**. Left aligned column. Can be used to give the distance along track or traveling **time** from the starting point (displayed in small size). |  |
| **+2** | **Right Text**. Left aligned column. Can be used to give the name of a station or other feature (displayed in usual size). |  |
| **+3** | **Right Text2**. Displayed in small size, just after *Right Text* (with a leading space when Right_Text is not empty). In other words, Right_Text and Right_Text2 are in the same column, aligned. |  |
| **+4** | **Comment**. Right aligned self standing column. Displayed in small size. Can be used to display as another *Dist./Time* case. | } |

When adding special styling in the text columns, be careful because the equals sign = will generate unexpected result because it functions exclusively as part of the **named** parameter syntax in the template (as text columns apply **unnamed** parameters). This can be bypassed by replacing the equals sign with <code></code> as in the case with vertical bar (pipe) that must be coded as .  

<pre></pre>  

### Cosmetic remark

Sometimes applying both main text and Comment in the same row may cause the whole map to stretch too wide because there is some very long Comment text in another row regardless whether the main text and note 1 cells of that row are applied or not. This can be fixed by moving the Comment to note 1. If aligning to is still highly desired, nest the note 1 text with .  

Remark: at present, this doesn't always work well with some web browsers. Some further research has to be done before this feature can be reused safely.  

### BS-2 row templates

BS-2 templates place text on both sides of the diagram, without the **Distance/Time** column, as opposed to the previously-introduced BS row templates which only has text displayed to the of the icon column(s). All named parameters of the BS row templates are also applicable here. These templates should not be used with other "-Text only" BS row templates in the same diagram. An example is the demonstration at the top of this project page.  

The unnamed parameters are:  

| Icon ID | &#124; | Left Text | &#124; | Right Text | &#124; | Left Text2 | &#124; | Right Text2 | &#124; | Comment |
| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |

| Icon 1 ID | &#124; | … | &#124; | Icon ID | &#124; | Left Text | &#124; | Right Text | &#124; | Left Text2 | &#124; | Right Text2 | &#124; | Comment |
| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |

These parameters are used to build four columns, in the following order:  

| **+1** | **Left Text**. Right aligned column. Can be used to give the name of a station or other feature (displayed in usual size). |  |
| --- | --- | --- |
| **+3** | **Left Text2**. Displayed in small size, just before *Left Text* (with a trailing space when Left_Text is not empty). In other words, Left_Text2 and Left_Text are in the same **first** column, aligned. |  |
| **1..** | **Icon ID** the name of the **n** icons that will be put side by side to form the **second** column of the map. The result is centered, allowing to mix BSn-2 with various values of n. For no icon to be shown leave blank (or use leer). |  |
| **+2** | **Right Text**. Left aligned column. Can be used to give the name of a station or other feature (displayed in usual size). |  |
| **+4** | **Right Text2**. Displayed in small size, just after *Right Text* (with a leading space when Right_Text is not empty). In other words, Right_Text and Right_Text2 are in the same **third** column, aligned. |  |
| **+5** | **Comment**. Right aligned self standing **fourth** column. Displayed in small size. Can be used to display *Dist./Time* (or anything else). | } |

<pre></pre>  

### Named parameters

All BS row templates have named (designated) parameters, providing advanced functions (beware of the uppercase/lowercase alphabets of the parameter names). They are the same for the BS and the BS-2 templates (except for tw-). For a given ***', letter ***' designs a non greater integer, i.e. 1≤≤. Most of the time, =1 is coded by nothing, rather than by "1".  
- **bg**: Use color name or HTML RGB hex code (with prefix <span>#</span>) as background to "highlight" or to emphasize certain sections, transparent by default
- **tw**: Width of the Right Text column. This is especially required for joining the icons cohesively when the text length in the "normal" BS row template text column is not wide enough to override the BS row collapsible sections.
- **tw-**: Width of the Left Text column. This is especially required for joining the icons cohesively when the text length in the "normal" BS row template text column is not wide enough to override the BS row collapsible sections.
- **PX**, **PX2**,... **PX**: size of the icon (e.g. PX=). Parameter PX is the default value of the PX2...PX, while is the default value of PX (actually, this amounts to x20px, coding for high. This parameter acts only on its row.
- **O** (Oh,p,q, not zero,p,q). These parameters are user to describe the icons overlay. For more details, see the overlay section.
- **alt1**, **alt2**,... **alt**: User-defined alt attribute for the icon image to override the alt text generated by . See also . Note that this parameter has been deprecated and is no longer in use.
- **L1**, **L2**,... **L**, etc.: User-defined internal link for the icon image to override the default link to file description page of the icon.

<div><div>  

</div></div>  

### Lining up BS row templates

Except for and , all BS row templates will join the icons in the same row cohesively, unless separated by an empty entry. To join the icons vertically, just open the same new BS row template and continue. (Example 1)  

Editor can also line up different BS row templates, because their icon column is set to align to . This is usually done by joining odd number row template by odd number row template, even number row template by even number row template, in order to omit the need of empty entry to stack up grid space. In examples 2 and 3, the only icon of joins the 2nd icon of vertically; and the 2nd and 3rd icons of join the 1st and 2nd icons of respectively.  

When joining odd and even number row templates (example 4), specialized icons such as and (supplementary corner) are required to patch the seam smoothly. (See .)  

The same rules applies for BS-2 templates, where the icon columns also align to . However, mixing BS and BS-2 rows should be avoided because it will ruin the layout of the whole map.  

## About Pictograms

### Icons repositories

These two pages describe the pictograms which are currently available. Page lists separately the icons to be used for watercourses. Another directory of icons can be found at Wikimedia Commons.  

The conventional file name format for image of this project is as follow: **BSicon_(pictogram ID).svg**. In BS*n* row templates, editor only needs to type the ID for the desired icon. The name of a pictogram, or ID, is constructed by prefix, ROOT and suffix jointly (e.g. forming by *u-STR-lg*). Prefix and suffix are always lowercase but ROOT is all caps to distinguish from the affixes. All icons contain at least one ROOT, but may combine two or more to form some complex icons. Affixes mostly variate the "base" icon in color, directionality, structure, etc and may not apply to simple icons.  

Because of the number of projects using these icons, additional codes have been created for special uses, including parallel routes and type changes.  

### Overlay

If a required icon does not exist it may be produced from *two to six* existing icons using the overlay parameter to superimpose one icon over another. Add the overlay parameters in the BS*n* or BS*n*-2 row template. O1 corresponds to the first (leftmost) place in the cell (icon grid), O2 to the second place in the cell, etc. More precisely, for a cell comprising *n* icons side by side, we have:  

- **O1** (Letter O one, not zero one), **O12**, **O13**, **O14**, **O15**: ID of an icon to overlay on the leftmost (p=1) icon of the cell, with five overlapping layers in maximum. The greater index of the parameter indicates the upper layer which is over the smaller (the base icon, described by being at the bottom of the pile).
- **O2**, **O22**, **O23**, **O24**, **O25**: ID of an icon to overlay on the 2<sup>nd</sup> leftmost (p=2) icon of the cell (the base icon, described by being at the bottom of the pile).
- **O*p***, **O*p*2**, **O*p*3**, **O*p*4**, **O*p*5**: ID of an icon to overlay on the *p<sup>th</sup>* icon of the cell, etc.
- **For rows of 11 or more icons (, , , , etc)**: use two digits to reference *p*, the icon number. In other words, use **O*01***, **O*01*2**, **O*01*3**, **O*01*4**, **O*01*5** for 1<sup>st</sup> icon, together with **O*12***, **O*12*2**, **O*12*3**, **O*12*4**, **O*12*5** for 12<sup>th</sup> icon, etc. In fact this is not logically required when n=11, but the doc was written that way. So we have &#123;&#123;BS11-2|O03= |O032=| already in use, and this can not be changed.
- **Overlay parameters** require a valid entry for the corresponding base icon cell. Otherwise the overlay icons will not be loaded, and the page will be categorized in .</span>

<div><div>  

</div></div>  

In order to allow the other editors to edit the diagram code more easily, it is a good practice to list the overlay icons immediately following the corresponding “base” icon entry. That way we humans do not need to look back and forth at the codes.  

The following examples A and B give the same result, but example B is recommended:  
<div><div>  

</div></div>  

## Collapsible sections

### StartCollapsible

It is possible to make sections of BS*n* rows collapsible as if it were in a NavFrame. The collapsible section begins with a **BS*n*-startCollapsible** row template (lacking the parameters **Right Text2**, **Comment** and **tw**), then include other "ordinary" BS*n* row templates which are set to be collapsible in the map, finally a table closing syntax <tt></tt> to end the collapsible section.  
Parameter definitions are as follows:  
| <>1 | <>2 | <>3 | } |
| --- | --- | --- | --- |
| <>1 | <>2 | <>3 | <>4 | } |
| --- | --- | --- | --- | --- |

<source lang="xml">  

</source>  

If the map has a combined use of different BS# row templates, the editor should choose the startCollapsible template which provides the same icon grids quantity as the greatest BS# row template used in the map (e.g., use when is the largest row template used in the map).  

In the startCollapsible template the color parameter **bg** colors the background of the entire collapsible section rather than its effect in ordinary BS*n* row templates which is confined to a single row. This clearly distinguishes between the non-collapsible and expanded collapsible sections.  

### Row replacement for Start-Collapsible

<pre></pre>  

BS-replace templates are supplementary to the BS-startCollapsible (BS-sc) row template that they replace, or more accurately, overlap over, the original BS-sc row template after expansion. The design aim is to make maps correct, both when collapsed and expanded. Because most maps use or to indicate the section being collapsed, but these icons might not make sense when expanded. It works simply by placing the BS-replace (child) template under the BS-sc (parent) template to be replaced. The available parameters are same as the BS-sc templates. These templates are experimental and still require testing in various browsers. It might not work properly in IE7 or older browsers because they might shift BS-replace templates incorrectly after expansion.  

Since BS-replace does not actually hide its parent BS-sc, if you have changed the background color of the BS-sc template with parameter <code>bg</code>, you should do the same for the child BS-replace template. If you want to hide the text in BS-sc (which is unnecessary in most case), you can use in the text cell of BS-replace and adjust the width that completely cover the text. Since the April 2013 update, if you want to cover the base icon with empty entry, you still need to use the icon to fill in the BS-replace icon cell manually, otherwise the BS-sc icon will still show up after expansion.  

### StartCollapsible and Row replacement for BS*n*-2
StartCollapsible and its replacement row templates are available for BS*n*-2 maps. When using these templates, entries for new parameter **tw-** (width of text cell) are required. It should be applied at any conventional BS*n*-2 template outside of the collapsible section, *every* startcollapsible and replace (if any) templates with exact same value otherwise the icon cells will be unable to align themselves correctly.  

<span>Caveat: Older versions of Google Chrome cannot line up the BS*n*-2sc and BS*n*-2replace templates correctly.</span>  

### Lining up Collapsible sections

This requires parameter (and ) to fix the width of the Right_Text column (and Left_Text column). They are naturally present in the collapsible templates. The way they are used in the ordinary bBSn, BSn-2 templates is to be rewritten.  

## Rows with text only
There are a number of templates that assist and simplify the display of text in route diagrams.  

### Navbar

The **** template can be used to place <span>view • talk • edit</span> links in a route diagram that does not automatically insert them (for example, when formatted for use in an ). See Template:Navbar/doc for usage and options.  

|}  
The parameter of and the second parameter of perform the same function. These should be given the name of the RDT, omitting the <code>Template:</code> prefix.  

### BSntext

The **** template is used to place a centered row of text in the area where icons are normally displayed. In all cases, the last three fields are the same as regular BS# templates, providing for <tt>Right Text</tt>, <tt>Right Text2</tt> and <tt>Comment</tt> (but no <tt>Margin</tt> column).  

### BS-colspan

The **** template is used to place text across the entire width of the table. All standard formatting can be used.  

## Fractional text display templates

### BScvt

This template displays a distance as two lines of text in a text field. The default input is miles, and the template calculates the kilometre equivalent.  
- Inserting the optional second parameter (any character) reverses the units.
- Decimal values are supported.
- The template automatically adds the units "mi" and "km" after the values.
- Yards, chains and metres are also supported.

The text is -aligned, but can be changed to - by applying the parameter "<code>align=</code>".  

### BSsplit

**BSsplit** displays two lines of text in a single row table.  
- The first two parameters are the two lines.
- The third parameter (alternatively ) defines a shared wikilink for both lines of text (no <code></code> or <code></code> are needed).
- The fourth parameter (alternatively *anything*) will change both lines to *italic* text. Any character or text can be used.
- The fifth parameter (alternatively *anything*) will change both lines to **bold** text. Any character or text can be used.
- Named parameter *anything* forces a separating line to appear. Any character or text can be used.
- Named parameter <code>align=</code> or <code>align=</code> overrides the alignment inherited from the parent cell
- Named parameters (top line) and (bottom line) are used to specify the background colors of the two displayed lines. They can be specified by providing a valid html color or a hex triplet.

The template also adjusts the text height so that it will not cause spaces to appear between the rows of icons.  

### BSto

The **BSto** template is intended for labeling connecting routes or adding other secondary information, as the second line is smaller and italicized. It also lacks a separating line. The optional <code>align</code> parameter will - or -justify text; if omitted it will default to “inherit”. The optional <code>it</code> parameter controls italicization.  

### BSsrws
**BSsrws** displays a railway station name split over two lines of text in a single table row. The first and second parameters are the two lines, which are combined to form the station name. The words <code>railway station</code> are not needed. All the formatting options of also apply to this template.  

<div><code></code>displays</div><div></div><div>and links to [[Stratford International railway station|]].</div>  

- *Do not* use BSsplit, BSto or BSsrws inside the &#123;&#123;BS-collapsible}} row template. Due to their table-based design they will absorb the entire collapsible section and become completely invisible.

## Element Formatting
### Stnlnk

**Stnlnk** (shortcut: ****) expands its parameter to link to the appropriate railway station article, without displaying the text "railway station". It is generally preferred to use the station, unless there is a specific reason to link to the place itself.  

### RouteBox

The ***' (shortcut:***') template displays a borderless box with colorable wikilinked text, suitable for displaying a route or line name in its own color.  

### RoutemapRoute

The ***' (shortcut: ***') template can be used to indicate routes and connecting lines. It places directional arrow(s) and one or two text fields in a map row, optionally enclosed by parentheses. A complete explanation is at Template:RoutemapRoute/doc.  

### Enlarge

The **** template displays a magnifying glass icon that links to another RDT to illustrate a small area in greater detail.  

## Icon display templates

### RoutemapRouteIcon

A single arrowhead can be displayed using the ***' (shortcut: ***') template.  

### Rail-interchange

The ***' (shortcut:***') template is used to indicate types of connections. It places the appropriate icon (in some cases with a link) in a map row. Some cities have additional arguments for individual services, and sometimes options for modifying the display. A complete list of icons is at Template:Rail-interchange/doc.  

### BSflag

The **** template displays a colored flag to indicate a “flag” or request stop, and links to &#91;&#91;request stop]].  

### UK road
| Code | Result | Links to |
| --- | --- | --- |
| <code></code> | &#91;&#91;A1 road (Great Britain)]] |  |
| <code></code> | &#91;&#91;B roads in Zone 1 of the Great Britain numbering scheme]] |  |
| <code></code> | &#91;&#91;M10 motorway (Great Britain)]] | } |

This template displays a small icon with an appropriate link for A and B roads and Motorways in Great Britain.  

## Examples
### Basic route diagram template using BS*n* only

Note: The code here produces the adjoining map. It does not mean to reflect the current situation.  

<pre></pre>  

### An example with collapsible sections

<source lang="moin">  

</source>  

## Tips

- If a station has a Wikipedia article, link to that rather than the town.
- Avoid overlinkage to a city or railway when its occurrences are close together on the route map.
- Connects lines should be linked to their own articles, particularly if there is a connection for passengers.
- For vee stations, show the lines as already joined in the station to show the connection or use the . The inclusion of a vee station shows that it has not been overlooked.
- At the ends of a line, show tracks which go further with a CONTinuation arrow: .
- For lines branching off, specify “to X”.
  - In general, other lines are shown *in italics*.
  - Template (shortcut: ) is an option to help describing in the text column with arrow icons ) .
- Crossing and connecting lines which are shown more than once can be connected with interruptions , but it should not normally be necessary to have more than two interruption icons in a row.
  - Note that WikiProject UK Waterways uses dotted lines to denote routes that are planned or under construction, in which case there is no restriction on the number needed.
- At intermodal interchanges, it is not desirable to list all the routes of the other modes, just the mode(s). For example, at a central railway station it is enough to show , rather than , etc.
- In order to comply with the and Wikipedia is not a crystal ball policies, information regarding planned and proposed features need to be with .
- When a map grows too large (such as *this*), it is recommended to not transclude the map inside an infobox or table which floats or aligns to the or , otherwise it would compress the adjacent main text into too narrow a space. This problem is exaggerated for user with low screen resolution. It is a good idea to align the standalone table (as explained in BS-map). If a - or -aligned table is desired, adjust the map width for a minimum of display width in Monobook or Vector Wiki style. Setting the table to “collapsed” by default (by applying the parameter **<code>collapse=yes</code>** in BS-map) also helps.
- In rapid transit/light rail diagrams that show both canals and non-navigable waterways, the similarly-coloured cerulean icons can be used to distinguish the former from the latter (.
- If an unusual situation requires using an icon in a non-standard manner, give an explanation either on the text row with the icon, or by a note at the top or bottom of the map—separated by an empty row or horizontal line—showing the “misused” icon and its meaning.

## Developer notes (Own icons)
In most case the icons available in Wikimedia Commons should be sufficient. However, if you think you need to create an icon of your own, please take note of the following points:  

- Check the or :Commons:category:BSicon and its subcategories to see if such icon already exists.
- Think if the icon you need can be displayed by overlaying two to six existing icons.
- Use SVG file format **only**. This can be done by using CORELDraw, Inkscape, Adobe Illustrator or an html/xml (text) editor.
  - Graphic size is not restricted, but it should be in square shape, usually 500 by (half-width icons rectangular 250 by ; double-width icons 1000 by ). Keep in mind how the image will look like when resized in the diagram to the default height of 20 pixels.
  - The SVG file should not contain any raster graphic and all of its shapes should be done by vector tools.
  - The image should be licensed as .
    - **Never** use copyrighted materials such as per the policy. The copyright status of an image can be checked on the file's description page. If you think a logo should be reclassified as copyright-ineligible due to being solely composed of typeface and/or simple geometry (to allow the logo to be used in a diagram), you may post a request or comment at .
- Follow the colour scheme and naming conventions listed in the and .
  - Names should be of the form: "BSicon_prefixROOTsuffix.svg"
    - ROOT defines a general function/shape,
    - prefix specifies a color/style/usage, and
    - suffix is a shape modifier
  - must be made for files containing diacritics from their dediacriticized name on Commons. For example redirects to .
- Tompw's Icon Generator may be used to easily create some types of new SVG icons.
- Preview your SVG image using SVG Check. Your SVG image may not look the same in Wikimedia from your SVG application or browser due to different font library and SVG rendering engine.
- Upload files to Wikimedia Commons into Icons for railway descriptions or one of its sub-categories. The more specific the category the better. If you are uncertain, just apply the general category BSicon and wait for another editor to change it.
- If you are incapable or having trouble creating icon, post your question at :Commons:Talk:BSicon/New icons and icon requests.