Template:Routemap

Related pages
Template (talk) Template sandbox Template testcases Template doc Template subpages Module Module sandbox Module testcases Module doc Module subpages

This template uses Lua: Module:Routemap (sandbox)

This template uses TemplateStyles: Template:Routemap/styles.css

This template is used for constructing route diagram templates. It is the Lua-based successor of the {{BS-map}} templates, which have been superseded by {{Routemap}} on the English Wikipedia but are still used on other wikis.

• 1 Usage
• 2 Markup for map parameter
  • 2.1 Basic
    • 2.1.1 Sidebar text
    • 2.1.2 Text cells in icon rows
  • 2.2 Icon overlay, icon link, background color and colspan
  • 2.3 Other formatting options
    • 2.3.1 Rows
    • 2.3.2 Individual cells/icons
  • 2.4 Collapsible
    • 2.4.1 Collapsible replacement
  • 2.5 Dual text sidebar
    • 2.5.1 Dual text sidebar collapsible
  • 2.6 Filler rows
  • 2.7 Syntax overview
• 3 Transition from legacy BS row template to Routemap markup
  • 3.1 Conversion policies
  • 3.2 Technical options
    • 3.2.1 Function convertbs
• 4 Embedding into infobox
• 5 Template data

{{Routemap
|navbar  = 
|navbar pos = 
|navbar mini = 
|title  = 
|title color = 
|title bg = 
|bg= 
|inline  = 
|collapsible = 
|collapse = 
|legend  = 
|legend alt = 
|float  = 
|style  = 
|top  = 
|footnote = 
|text-width = 
|map  =
}}

The markup for composing the diagram in the |map= parameter is different to the {{BSrow}}-based templates. The major differences are the separators in each row. Subtemplates are not necessary, since a new row in the table is simply created by a carriage return (newline).

{{Routemap
Add other parameters like |title= here.
|map=
Map markup goes here!
}}

icon ID\icon ID\icon ID

• Icons are separated by the backslash \.
• Each group of icons is centered in its row. The nameless icon (at the start of row 5 in the diagram) can be used as a spacer.
• The ID of each icon can be seen in its tooltip. Move your cursor over the icons to see them.

icon ID\icon ID\icon ID~~dist./time~~main text~~remark~~right remark

or

icon ID\icon ID\icon ID~~main text

{{Routemap
|title=Example 1.2
|map=
KBHFa~~terminus
WASSERq\hKRZWae\WASSERq~~ ~~ ~~ ~~Bridge
LDER\INT\~~1 km~~station~~transfer for HSR
\KBHFe\BUS~~2 km~~terminus~~bus terminal
}}

• The third and fourth pairs of tildes can be omitted if there is no content following either of them.
• After the last icon ID, if there is only one set of "tilde-tilde" (~~), the following text will be displayed in the main text cell instead of dist./time.
• Separating text cells requires at least one empty space; otherwise the tildes will be treated as a signature.

*text\d*text\cd*text~~main text

{{Routemap
|title=Example 1.3
|map=
ENDEa~~ ~~ ~~Reversing siding
SPLa
cPLT\vSTR\cPLT~~Station
d*1\cPLT\vSTR\cPLT\d*2~~ ~~ ~~Platform numbers
cPLT\vSTR\cPLT
vCONTfge~~ ~~ ~~''to City''
}}

The asterisk indicating a text cell can be preceded by one of the BSicons' width prefixes. (Normal BSicons are square.)

{{Routemap |title=Example 2.1 |map= -colspan-1 Icon overlay uSTRq!~STR2!~BHF!~lHUB\\dSTR!~uSTRq\dSTR!~dNULf -colspan-2-style=border-bottom:5px solid red; ---- icon link utBHF!@Superhub -colspan ---- background color -colspan-end utSTR~~ ~~ ~~ ~~ ~~bg=#7af }}

Example 2.1 Icon overlay icon link background color

• Overlay separator "exclamation mark-tilde" (!~) must follow the icon ID which is to be overlaid.
• Overlay is practically unlimited, but legibility should be taken into account.
• The width of the underlying icon determines the width of the combination, even if less than the overlay. The icons are aligned with their left edges together, so that they will not be centered on each other if they differ in width. If the overlay extends past the underlying icon, it will overlay the following icon (but not the following icon's overlay).
• When using icon overlay and icon link for the same icon cell, the icon link separator (!@) must follow the last (top) overlaying icon ID.
• The background color parameter (bg=) requires 5 sets of preceding text separators to be recognizable even if there is no text on that row whatsoever.

{{Routemap
|title=Example 2.2
|map=
utSTR~~ ~~ ~~{{mono|1=bg=<abbr title="This is the normal BSicon color for watercourses.">#007CC3</abbr>}}~~ ~~bg=#007CC3
*1\*2\*3~~ ~~ ~~{{mono|1=color=red,bold=yes}}~~ ~~color=red,bold=yes
*A\*C\*E~~ ~~ ~~{{mono|1=align=l,b=1,fontsize=cmt}}~~ ~~align=left,b=1,fontsize=cmt
*B\*D\*F~~ ~~ ~~{{mono|1=colour=orange, align=b, i=y}}~~ ~~colour=orange, align=b, i=y
}}

Aside from bg=, there are several other parameters, separated by commas (,), which can be used to customize the display of a row. Only bg= can be used to change the display of icons; all others only affect text cells.

icon!_bg=purple\*text__align=l!~*more text__align=r,b=yes

• Parameters for a single icon or text cell (e.g. BHF, *Text) are preceded by two underscores (__).
• Parameters for the contents of a table cell (a stack of overlaid objects, or a single icon or text box with no overlays) are preceded by an exclamation mark and an underscore (!_). This must follow the link (if any).
• For the last overlaid item in a stack, the individual item parameters (if any) must precede the stack parameters.
• Most of the parameters are the same as those for rows, but there are a few additional ones. Additionally, the values for align=, bg= and color= will override the row parameter values.

{{Routemap
|title=Example 3.1: Basic collapsible
|text-width=80|map=
-startCollapsible-collapsed
\KBHFa\~~terminus
hSTRa@g
WASSERq\hKRZW\WASSERq~~ ~~ ~~ ~~bridge
hSTRe@f
-endCollapsible-
LDER\INT\~~ ~~station~~transfer for HSR
\KBHFe\BUS~~ ~~terminus~~bus terminal
}}

{{Routemap
|title=Example 3.2:<br/>Mixed odd and even rows
|tw=70|map=
-startCollapsible-collapsed
d\KBHFa\d~~terminus
hKRZWae~~ ~~ ~~bridge
-endCollapsible-
BS2+l\BS2+r~~junction
}}

• Adjust |text-width= (or|tw=) parameter until there is no break.
  • Unit is "px" by default, but other units such as "em" are acceptable.
  • Check the map in different browser and in mobile view, and increase text-width if it breaks.
• The icon number of the first row of collapsible section must be equal to or greater than the icon number of the widest non-collapsible row.
  • As in example 3.2, use half-width empty icon  (d) as filler when you are mixing both odd and even rows in the same map.
• Changing "collapsed" to "nil" will change the default state of the collapible section to uncollapsed.

{{Routemap
|title=Example 4.1
|text-width=150
|map=
KBHFa~~terminus
-startCollapsible-collapsed-replace
\LSTR\~~hidden section
\hSTRa@g\
WASSERq\hKRZW\WASSERq~~ ~~ ~~viaduct
hSTRe@f
-endCollapsible-
LDER\INT\~~ ~~station~~transfer for HSR
\KBHFe\BUS~~ ~~terminus~~bus terminal
}}

{{Routemap
|title=Example 4.2: Empty filler
|text-width=150
|map=
-startCollapsible-collapsed-replace
exCONTg~~under construction
leer
exKBHFa~~future terminus
exBHF~~future station
-endCollapsible
KBHFxa~~terminus
KBHFe~~terminus
}}

• Both replacement and replaced rows must be as wide as the widest non-collapsible row in the diagram.
• If you want to hide the replaced row after expanding the collapsible, use icon  (leer) as empty filler as in example 4.2.
• In any case, mind to provide a sufficient text-width. Here, using text-width=120 would break the alignment of the icons.
• Collapsible elements are intentionally disabled in mobile view, so the replaced row will never be visible. Keep this in mind while creating a diagram.

For larger and more complicated diagrams, it often helps to have a text sidebar on the left as well as the right.

left-left remark~~left remark~~left main text~~left dist./time! !icon ID~~right dist./time~~right main text~~right remark~~right-right remark

or

left main text! !icon ID~~right main text

{{Routemap
|title=Example 5
|map=
~~km! !~~km~~
commuter terminus~~0! !uKBHFa\\KBHFa~~0~~regional terminus
River Boris~~ ~~! !uhKRZWae\WASSERq\hKRZWae~~ ~~ ~~bridge
transfer for HSR~~station~~1! !uINT\LDER\LSTR
commuter terminus~~2! !uKBHFe\\KBHFe~~2~~regional terminus
}}

• Left text cells require "exclamation mark-space-exclamation mark" (! !) separating them from icon cells.
• If there is no "tilde-tilde" (~~) separator to the left of "exclamation mark-space-exclamation mark", the text to the left of the separator will be displayed in the left main text cell.

{{Routemap
|title=Example 6.1: All text cells applied
|text-width=,130,,,110,
|map=
~~km! !\\~~km~~
-startCollapsible
commuter terminus~~0{{0|00}}! !uKBHFa\leer\KBHFa~~{{0|00}}0~~regional terminus
River Boris~~ ~~! !uhKRZWae\WASSERq\hKRZWae~~~~ ~~bridge
-endCollapsible
transfer for HSR~~station~~1! !uINT\LDER\LSTR
commuter terminus~~2{{0|00}}! !uKBHFe\\KBHFe~~{{0|00}}2~~regional terminus
}}

{{Routemap
|title=Example 6.2: Only main text cell applied
|style=width:380px
|text-width=,120,,,120,
|map=
-startCollapsible
commuter terminus! !uKBHFa\\KBHFa~~regional terminus
River Boris! !uhKRZWae\WASSERq\hKRZWae~~bridge
-endCollapsible
station! !uINT\LDER\LSTR
commuter terminus! !uKBHFe\\KBHFe~~regional terminus
}}

• Apply |text-width= to eliminate the break:
  • Only 1 value: right main text+right remark
  • 3 values, separated by commas: right dist./time,right main text+right remark,right-right remark
  • 6 values: Left-left remark,left remark+left main text,left dist./time,right dist./time,right main text+right remark,right-right remark
  • If the number of values is not equal to 1, 3 or 6, the entire parameter will be ignored.
• If the text width of right-right remark is smaller than needed, its width definition can be omitted, as in example 6.1.
• If a specific text cell is not used anywhere on the map, that width definition can be omitted, as in example 6.2.
• Define the general table width with the {{{style}}} parameter if {{{text-width}}} alone cannot prevent a break.
• If the empty icon cell of the collapsible row is being squashed, use empty icon  (leer) to correct the icon columns.

Code	Result
{{Routemap |title=Example 7 |map= uKBHFa!~HUBaq\HUBq\KBHFa orange!~HUBeq -filler--#003399\\#FF6600 uBHF!~HUBaq\KBHFa!~HUBq\BHF orange!~HUBeq -filler--u\-\orange uKBHFe!~HUBaq\KBHFxe!~HUBq\KBHFxe orange!~HUBeq -filler-80px-\ex\ex_orange~~ ~~ ~~Sample<br>text~~ ~~bg=#007CC3 \exKBHFe!~HUBaq\exKBHFe orange!~HUBeq }}	Example 7 Legend Sample text

Many contributors of the English Route Diagram Template project during the implementation of Routemap have conflicting opinions about the justification of replacing all maps of legacy BS row templates by the Lua-based Routemap. Opponents deem the map markups of Routemap to be too esoteric for editors unfamiliar with Routemap markup to modify. While proponents support a complete conversion for better performance. There is no consensus reached at the moment so any transition without massively updating the map appearance for reflecting service and/or structural change in reality should only be done with the following considerations:

• The map of the legacy BS row template design has exceeded template size limit in the transcluding page, which means the template does not expand into its intended appearance but only the link to the template page is shown, so there is an imminent need to translate the map into Routemap design to reduce post-expand include size.
• If there is no template size issue, respect the preference of the initial contributor of the first completed version of the diagram. If that contributor contests the change to Routemap, retain the BS row template design.

All BS row templates have had substitutable counterparts created; hence conversion can be easily done by prepending subst: and appending /safesubst to every BS row template name in the map. For example, change {{BS2|STR|BHF|0|1|2|3|O1=uSTRq}} in the map to {{subst:BS2/safesubst|STR|BHF|0|1|2|3|O1=uSTRq}}, then publish changes; it will produce STR!~uSTRq\BHF~~0~~1~~2~~3. The process can be sped up by using the "replace all" function of advanced edit tool or separate text editor such as NotepadorNotepad++, but the search rule for the BS row templates should ideally be a regular expression, like \{\{(BS\d*(\-2)?)\| → {{subst:$1/safesubst|, in order to avoid templates with similar names such as BSto and BSsplit in case they are present in the map.

"Column mode editing" can avoid the trouble of find and replace to add safesubst: on all rows efficiently. This function is common in advanced text editors like Geany,^[1] Notepad++^[2] and Sublime Text^[3].

You can also use the "convertbs" function of Module:Routemap.

Copy and paste the following code to any edit area of this wiki, maybe the map page you are working on:

{{#invoke:Routemap|convertbs|<nowiki>

</nowiki>}}

Then copy and paste the original BS-map or BS-table map code between the <nowiki> tags (alternatively paste the invoke convertbs header before the original map code and the </nowiki>}} ending after the map code) and show preview. It will generate the safesubst version and show the original versions (for comparison) of the map code. You copy the safesubst code from the preview area back to the edit area, and you should remove everything of #invoke:Routemap|convertbs if the preview of the new code works properly.

On the English Wikipedia, the template {{subst:convertbs}} can be used as a shortcut:

{{subst:convertbs|1=

}}

If it doesn't work, it's possible that you haven't copied some of the relevant code, such as table markup for BS-table diagrams, or that you've copied code which actually belongs to something else.

{{#invoke:Routemap|convertbs|<nowiki>
{{BS-map
|title=Demonstration
|map=
{{BS|KBHFa|0 km|A station|Shuttle bus}}
{{BS3|WASSERq|hKRZWae|WASSERq||||{{BSsplit|Suburb|Capital}}}}
{{BS|KINTe|10 km|B station|City hub}}
{{BS-colspan}}
----
Not to scale
}}
</nowiki>}}

{{Routemap
|title=Demonstration
|map=
{{safesubst:BS/safesubst|KBHFa|0 km|A station|Shuttle bus}}
{{safesubst:BS3/safesubst|WASSERq|hKRZWae|WASSERq||||{{BSsplit|Suburb|Capital}}}}
{{safesubst:BS/safesubst|KINTe|10 km|B station|City hub}}
-colspan-2
----
Not to scale
}}

{{BS-map
|title=Demonstration
|map=
{{BS|KBHFa|0 km|A station|Shuttle bus}}
{{BS3|WASSERq|hKRZWae|WASSERq||||{{BSsplit|Suburb|Capital}}}}
{{BS|KINTe|10 km|B station|City hub}}
{{BS-colspan}}
----
Not to scale
}}

• Use {{{inline}}} to remove title bar and table border. If creating a separate template which will be embedded into an infobox, wrap inline=1 in <includeonly>...</includeonly> tags. Also {{{navbar pos}}} is helpful to locate the {{Navbar}} better.

{{Infobox station | name = {{color box|orange}} Station layout | image = Placeholder.png | image_upright = 0.5 | image_caption = Platform level | opened = {{Start date|1935|05|15|df=y}} | tracks =2| route_map = {{routemap|inline=1|navbar=asd|navbar pos=2| KBHFa~~terminus WASSERq\hKRZWae\WASSERq~~ ~~ ~~ ~~Bridge LDER\INT\~~1 km~~station~~transfer for HSR \KBHFe\BUS~~2 km~~terminus~~bus terminal }} }}

Station layout Platform level General information Tracks 2 History Opened 15 May 1935 (1935-05-15) Route map Legend terminus Bridge 1 km station transfer for HSR 2 km terminus bus terminal This diagram: view talk edit

Languages