Module:Road data/strings/CHN
This module is used to store type data for use with several road templates, including {{jct}} and {{routelist row}}. Background information and a summary of the syntax are listed below.
Exported types
This module exports the following types:
AH, Ex, Expwy, G, Guodao, S and X
Syntax
Hierarchy and fields
At its most basic level, this module is a nested table of strings. At the top is the root table, named for the abbreviation of a country, state, or province. This table stores the type data for a particular place, which is named in the comment in the first line, and is returned at the end of the module. The table is composed of further tables, one per type. The basic syntax for a type table is:
place.type = {
shield = "",
name = "",
link = "",
abbr = ""
}
The four main fields in a type table are shield, name, link, and abbr. Currently, these are the types used by all countries. By convention, they are always specified, using an empty string "", if there is no value.
shielddetermines the shield that is displayed, if anynamespecifies the name of the route displayed by an infoboxlinkspecifies the target of a link generated, if anyabbrdetermines the displayed abbreviation.
Other common fields in road data tables
shieldmainis used when a different shield is desired at the top of an infobox, such as for county roads.
USA.CR = {
shield = "CR %route% jct.svg",
shieldmain = "[county||%county% |]County %route%.svg",
name = "County Road %route%",
link = "",
abbr = "CR %route%"
}
shieldlistis used when a different shield is desired in lists that utilize the {{Routelist row}} series of templates.
basecan be used for aliasing different types that have a similar base structure, such as U.S. Highway special routes.
bannerstores the name of the special route plate, such asBusiness plate.svg. Can be omitted when unused.widthstores a code representing the width of the shield. It is most often helpful when used withbanner. Can be omitted entirely when unused; common values aresquareandexpand.
sectionstores the specific section number for those routes that are defined by law.
translationspecifies the native language name of the route displayed by an infoboxlangis the ISO 639-2 code of the native language; this code is used by {{Lang}} and Lang-xx templates.
PER.RN = {
shield = "PE-%route% route sign.svg",
name = "National Route %route%",
link = "Peru Highway %route%",
abbr = "PE-%route%",
translation = "Ruta nacional %route%",
lang = "es-pe"
}
Once a type is defined, it can be referenced later in the code. As seen here, it is common to define all parameters for main types like US and then to use aliases for subtypes such as US-Alt.
MO.US = {
shield = "US %route%.svg",
base = "U.S. Route %route%",
link = "U.S. Route %route% in Missouri",
abbr = "US %route%",
width = "expand"
}
MO["US-Alt"] = {
shield = MO.US.shield,
link = MO.US.base .. " Alternate ([dab||%dab%, |]Missouri)",
abbr = MO.US.abbr .. " Alt.",
banner = "Alternate plate.svg",
width = "expand"
}
Parser arguments
When the parser function of Module:Road data/parser is called, it is passed up to three parameters. The second one is the field to parse, and the last one is a rarely-used option designed for multiple-shield types. The first and most important parameter is a table of arguments collected by the calling module, which generally includes the state, country, or both; the type and number of the route; and a few miscellaneous arguments. This table of arguments forms the basis of the parser's format string syntax.
The table accessible by the strings includes the following entries by default:
state: The state or province the route is located in.country: The country the route is located in. If the country is not passed by the calling module, the parser will attempt to include it.
The above entries are primarily used to find the string module itself, so they should not be a concern for module writers.
type: The type of the route. This determines the entry of the root table that is used by the parser.route: The route "number". This is easily the most important argument for module writers.
The following entries are used less often:
county: The county the route is located in. This is usually used for county routes in the United States.township: This entry is similar in function and utility to thecountyentry.dab: A tag used to disambiguate the link target. This is mostly used for bannered routes in the United States.denom: This rare entry is used exclusively for West Virginia county routes.
Parser hooks, which will be described later, can add entries to this table that may be used by strings.
Basic string syntax
The most basic value that can be used for most type table fields is a specially formatted string, which will be referred to in this documentation as a format string. This is the string that will ultimately be parsed and returned by the parser. A format string is an ordinary string object. The power of these strings comes in the form of two special instructions that are recognized by the parser.
The first is anything in %argument% form. The parser will replace such a statement with the value of the argument entry in the arguments table described earlier. This is what allows the route number to be spliced into a shield or link name.
The second special string is in the form of [arg|equals|then|else]. This functions as a rudimentary if-then-else statement. The parser tests the value of arg to see if it is equal to the value specified in equals. equals may be empty, in which case the parser tests the existence of the arg argument. If the result of the test is true, the statement is replaced with the value of the then block. Otherwise, it is replaced with the value of the else block.
The two statements may be combined. The parser will parse the if-then-else statement first, and then perform the argument inclusion. This combination is commonly used with bannered routes in the United States, where the dab argument is tested and the link disambiguation is adjusted accordingly, as follows:
AL["US-Bus"] = {
shield = "US %route%.svg",
link = "U.S. Route %route% Business ([dab||%dab%, |]Alabama)",
abbr = "US-%route% Bus.",
banner = "Business plate.svg",
width = "expand"
}
When parsing the link field, the parser first checks to see if the dab argument was provided. If so, it replaces the statement with %dab%, . If not, the statement is replaced with the empty string placed in the else block. Then, the parser replaces %route% with the route number and, if the dab argument was provided, %dab% with the value of that argument.
Switching
Some logic is too complicated to represent with only format strings. This framework provides several methods to express complex data. All of these involve storing a nested table as the value of a field.
The most straightforward functionality provided by nested tables is switching. In its most basic form, the table consists of a series of key-value pairs, with the keys being route numbers and the values being the format strings used by those routes. Usually, the format string returned does not need parsing, but the option is there. A default entry should be provided to handle any route numbers not explicitly stated. The following is a representative example of route-based switching (from Module:Road data/strings/USA/AR):
AR.AR = {
shield = {
default = "Arkansas %route%.svg",
["917"] = "Arkansas 917-1.svg",
["980"] = "Arkansas 980(Airport).svg"
},
link = "Arkansas Highway %route% [dab||(%dab%)|]",
abbr = "Hwy. %route%",
width = "expand"
}
In this example, Highways 917 and 980 have non-standard shield names, which are explicitly provided. Other route numbers use the default format.
Switching on other arguments is also allowed. The name of the argument to be used for switching is stated in the arg field of the table. Nesting switches on different arguments is also allowed. A good example that uses both forms of switching can be found in Ontario:
local regionalShields = {
arg = "county",
["Essex"] = "Essex County Road %route%.png",
["York"] = "York Regional Road %route%.svg",
["Durham"] = "Durham Regional Road %route%.svg",
["Niagara"] = "Niagara Regional Road %route%.svg",
["Simcoe"] = {
["52"] = "Simcoe county road 52.png",
default = "Simcoe County Road %route%.JPG"
}
}
In this example, which is a shield table that is reused by several types in Ontario, the county argument is used for the primary switch. If the route is in Simcoe County, a second switch is performed, this time on the route number.
Existence testing
Another use for tables is existence testing. If a table has the ifexists field set to true, the parser will perform existence testing on the result of parsing the default field. If the test fails, the result of parsing the otherwise field is returned. Existence testing may be chained by using a second ifexists table as the value of the first table's otherwise field, and so on. Here's an example of nested existence testing (from Module:Road data/strings/GBR):
GBR.B = {
shield = {
ifexists = true,
default = "UK road B%route%.svg",
otherwise = {
ifexists = true,
default = "UK road B%route%.png"
}
},
link = "",
abbr = "B%route%"
}
Hooks
Due to technical limitations, these string modules cannot contain functions. Rather than force functionality into the string framework, the parser can call functions in a separate hooks module. The functions in this module, Module:Road data/parser/hooks, are more-or-less fully functional functions. The exact functionalities of these hooks are beyond the scope of this documentation. Descriptions of these hooks may be found on their documentation page.
Generally speaking, a hook is called by setting the hook field in a table as equal to the name of a hook. Hooks receive two arguments, both tables: parameters, which is the table in the definition; and args, which is simply the table of arguments normally passed to the parser. The hook returns a string, which is then parsed as usual. A powerful feature of hooks is that they can add arbitrary values to the argument table, which may be referenced in the string returned by the hook. Generally, the format string returned by the hook is specified in some form by the default field of the table, though there are exceptions. Here is an example of a hook (from Module:Road data/strings/MEX):
MEX.SH = {
shield = {
ifexists = true,
arg = "state",
SON = "HIGHWAYSON %route%.jpg",
NLE = "Nuevo Leon State Highway %route%.PNG",
default = ""
},
link = {
hook = "mask",
mask = "Road data/masks/MEX",
base = "state",
masked = "fullstate",
default = "%fullstate% State Highway %route%"
},
abbr = "SH %route%"
}
In this example, the parser will process the link by calling the mask hook. In short, this hook takes the argument referenced in base, passes it through the mask module specified in mask, and stores it in the field in the arguments noted in masked. The hook returns the string given in default, which has access to the fullstate argument added by the hook.
Other functionality
Functionality exists to display multiple shields for one route, which is used to display tolled and free shields for routes where they differ. This is done by supplying a table with two values, which are listed without indices. The parser is called twice by the calling module, and it returns one shield per call. An example may be found in Texas:
TX.Both = {
shield = {"Texas %route%.svg", "Toll Texas %route% new.svg"},
link = "Texas State Highway %route%",
abbr = "SH %route%",
width = 40
}
Structure
Each country has its own module. In the United States and Canada, each state/territory/province also has its own module. Each module begins with a comment stating the name of the country or state, followed by the root table declaration, as follows (from Module:Road data/strings/USA/AS):
-- American Samoa
local AS = {}
The root table is named based on the established abbreviation for the country or state, which is the same as the abbreviation used in the module title. This table stores the various types used in that particular place. Most of the remaining code in the module defines these various types. The module ends by returning the root table:
return AS
Aliasing
There are two ways to define a type as an alias. If the type is defined within the module, simply set the new type as equal to the type being aliased, as shown above (from Module:Road data/strings/HKG):
HKG.Route = {
shield = "HK Route%route%.svg",
link = "Route %route% (Hong Kong)",
abbr = "Route %route%"
}
HKG.route = HKG.Route
If the type is defined in a separate module, such as a state highway type being used in another state's module, a special syntax may be used to refer to that module (from Module:Road data/strings/USA/NJ):
NJ.NY = {alias = {module = "USA/NY", type = "NY"}}
This code sets the NY type as a link to the NY type in Module:Road data/strings/USA/NY. The parser will import that module and process the type as if the original module had declared it itself. The alias declaration may not add or override any data in the type table it points to.
Inheriting types
It is possible to predefine several types for a location by inheriting them from another module. In this example, the module for Albania inherits all of the specified types from the Europe module.
-- Albania
local ALB = {}
local util = require("Module:Road data/util")
util.addAll(ALB, require("Module:Road data/strings/EUR"))
Only one module may be inherited at this time.
Advanced uses
It is possible to create multiple types based on a specified pattern using ipairs. In this example from Module:Road data/strings/USA/WA, the US 1926, US 1948, and US 1961 types are all created from the same code. At the bottom that is an override for US 1961's shieldmain.
for _,year in ipairs({"1926", "1948", "1961"}) do
WA["US " .. year] = {
shield = format("US %%route%% (%s).svg", year),
shieldmain = format("US %%route%% Washington %s.svg", year),
base = WA.US.base,
name = WA.US.name,
link = WA.US.link,
abbr = WA.US.abbr,
width = "square",
}
end
WA["US 1961"].shieldmain = "US %route% (1961).svg"
Similarly, subtypes can be created in the same manner. This example creates 9 subtypes each for WA and SR. The aux is inherited from Module:Road data/strings/USA. That, in turn, modifies auxType and spec accordingly.
for _,type in ipairs({'WA', 'SR'}) do
for _,auxType in ipairs({"Alt", "Bus", "Byp", "Conn", "Opt", "Scenic", "Spur", "Temp", "Truck"}) do
local spec = WA[" aux "][auxType]
WA[type .. "-" .. auxType] = {
shield = WA[type].shield,
shieldmain = WA[type].shieldmain,
name = WA[type].name .. " " .. spec.name,
link = WA[type].link .. " " .. spec.name .. suffix,
abbr = WA[type].abbr .. " " .. spec.abbrsuffix,
banner = spec.bannerprefix .. " plate.svg",
aux = spec.aux,
width = WA[type].width
}
end
end
Style
There are a few style guidelines that should be followed:
- Align table fields using tabs. All tables should be aligned so that fields line up with each other, as shown in the above examples.
- Each table field should be on its own line.
- Add spaces to either side of an assignment operator (equals sign).
- Leave a blank line between types. Type aliases should be set off from their base type by a blank line, but no blank lines should be placed between the aliases themselves.
--[==[
To inspect the content of this data module, use [[Special:ExpandTemplates]]
and enter the following input text:
{{#invoke:Road data/dump|dump|module=Module:<name-of-this-module>}}
To inspect the content of this data module when editing, enter the following
into the Debug console:
local util = require("Module:Road data/util")
print(util.arrayToString(p))
To inspect a particular route type, change `p` above to include the route type,
e.g., `p.I` and `p["US-Hist"]`.
]==]
-- China
local CHN = {}
local util = require("Module:Road data/util")
util.addAll(CHN, require("Module:Road data/strings/ASIA"))
CHN.G = {
shield = "Kokudou %route%(China).svg",
name = "National Highway %route%",
link = "China National Highway %route%",
abbr = "G%route%",
translation = "%route%国道",
lang = "zh"
}
CHN.Guodao = CHN.G
CHN.X = {
shield = "China County Road X%route%.svg",
abbr = "X%route%",
link = "",
abbr = "X%route%"
}
CHN.Expwy = {
shield = "China Expwy G%route% sign no name.svg",
shieldmain = "China Expwy G%route% sign with name.svg",
name = {
hook = "mask",
mask = "Road data/masks/CHN/Expwy",
base = "route",
masked = "names",
default = "%names%"
},
link = {
hook = "mask",
mask = "Road data/masks/CHN/Expwy",
base = "route",
masked = "names",
default = "G%route% %names%"
},
abbr = "G%route%",
translation = {
hook = "mask",
mask = "Road data/masks/CHN/Expwy translations",
base = "route",
masked = "translation",
default = "%translation%"
},
lang = {
arg = "route",
default = "zh",
["3012"] = "ug",
["3013"] = "ug",
["3014"] = "ug",
["3015"] = "ug",
["3016"] = "ug",
}
}
CHN.Ex = CHN.Expwy
CHN.S = {
shield = {
hook = "mask",
mask = "Road data/masks/CHN",
base = "state",
masked = "province",
default = {
ifexists = true,
default = "[province||%province% Expwy S%route% sign no name.svg|Shoudou %route%(China).svg]",
otherwise = {
ifexists = true,
default = "Shoudou %route%(China).svg"
}
}
},
link = {
arg = "province",
["BJ"] = {
arg = "route",
["11"] = "Beijing–Chengde Expressway",
["12"] = "Airport Expressway (Beijing)",
["28"] = "Northern Airport Expressway",
["51"] = "2nd Airport Expressway",
["50"] = "5th Ring Road"
},
["SH"] = {
arg = "route",
["1"] = "S1 Yingbin Expressway",
["2"] = "S2 Shanghai–Luchaogang Expressway",
["3"] = "S3 Shanghai–Fengxian Highway",
["4"] = "S4 Shanghai–Jinshan Expressway",
["5"] = "S5 Shanghai–Jiading Expressway",
["6"] = "S6 Shanghai–Nanxiang Expressway",
["12"] = "S12 Chongming–Haimen Expressway",
["16"] = "Shanghai–Yixing Expressway",
["19"] = "S19 Xinnong–Jinshanwei Expressway",
["20"] = "S20 Outer Ring Expressway",
["22"] = "S22 Jiading–Anting Expressway",
["26"] = "Shanghai–Changzhou Expressway",
["32"] = "Shanghai–Jiaxing–Huzhou Expressway",
["36"] = "S36 Tinglin–Fengjing Expressway"
},
["JS"] = {
arg = "route",
["5"] = "S5 Changshu–Jiashan Expressway",
["9"] = "S9 Suzhou–Shaoxing Expressway",
["19"] = "S19 Nantong–Wuxi Expressway",
["29"] = "S29 Yancheng–Jingjiang Expressway",
["35"] = "S35 Taizhou–Zhenjiang Expressway",
["39"] = "S39 Jiangdu–Yixing Expressway",
["45"] = "S45 Yixing–Hangzhou Expressway",
["49"] = "S49 Xinyi–Yangzhou Expressway",
["51"] = "S51 Liyang–Huangshan Expressway",
["55"] = "S55 Nanjing–Xuancheng Expressway",
["59"] = "S59 Nanjing–Hexian Expressway",
["65"] = "S65 Xuzhou–Mingguang Expressway",
["69"] = "S69 Jinan–Xuzhou Expressway",
["8"] = "S8 Siyang–Suzhou Expressway",
["18"] = "S18 Yancheng–Huai'an Expressway",
["22"] = "S22 Yizheng–Nanjing Expressway",
["28"] = "S28 Qidong–Yangzhou Expressway",
["32"] = "S32 Chongming–Haimen Expressway",
["38"] = "S38 Changshu–Hefei Expressway",
["48"] = "Shanghai–Yixing Expressway",
["58"] = "Shanghai–Changzhou Expressway",
["68"] = "S68 Liyang–Wuhu Expressway",
["72"] = "S72 Port of Lianyungang North Port Expressway",
["73"] = "S73 Port of Lianyungang East Port Expressway",
["75"] = "S75 Funing–Xinghua–Taizhou Branch Expressway",
["79"] = "S79 Nantong Branch Expressway",
["80"] = "S80 Port of Taicang North Port Expressway",
["81"] = "S81 Port of Taicang South Port Expressway",
["82"] = "S82 Port of Zhangjiagang Port Expressway",
["83"] = "S83 Wuxi Branch Expressway",
["85"] = "S85 Liyang Branch Expressway",
["86"] = "S86 Zhenjiang Branch Expressway",
["87"] = "S87 Nanjing Branch Expressway",
["88"] = "S88 Nanjing Lukou International Airport Expressway",
["92"] = "S92 Jinhu Branch Expressway",
["96"] = "S96 Suqian Branch Expressway"
},
["GD"] = {
arg = "route",
["1"] = "S1 Guangzhou–Lechang Expressway",
["2"] = "S2 Guangzhou–Heyuan Expressway",
["3"] = "S3 Guangzhou–Shenzhen Riverbank Expressway",
["4"] = "Huanan Expressway",
["4W"] = "S4W Guangzhou–Macau Expressway Zhuhai Branch Line",
["5"] = "S5 Guangzhou–Gaoming Expressway",
["6"] = "S6 Guangzhou–Zhongshan–Jiangmen Expressway",
["8"] = "S8 Guangzhou–Foshan–Zhaoqing Expressway",
["10"] = "S10 Shaoguan–Ganzhou Expressway",
["12"] = "S12 Meizhou–Longyan Expressway",
["13"] = "S13 Jieyang–Huilai Expressway",
["14"] = "S14 Shantou–Zhanjiang Expressway",
["15"] = "S15 Shenyang–Haikou Expressway Guangzhou Branch Line",
["16"] = "S16 Paitan–Jiekou Expressway",
["17"] = "S17 Chaozhou–Huilai Expressway",
["20"] = "S20 Chaozhou–Dongguan Expressway",
["21"] = "S21 Guangzhou–Huidong Expressway",
["22"] = "S22 Longbeiling–Lincun Expressway",
["23"] = "S23 Huizhou–Aotou Expressway",
["25"] = "S25 Changchun–Shenzhen Expressway Huizhou Branch Line",
["26"] = "S26 Shenzhen–Luoding Expressway",
["27"] = "S27 Renhua–Shenzhen Expressway",
["28"] = "S28 Shuijing–Guanjingtou Expressway",
["29"] = "S29 Conghua–Dongguan–Shenzhen Expressway",
["30"] = "S30 Huizhou–Shenzhen Coastal Expressway",
["31"] = "S31 Longhua–Dalingshan Expressway",
["32"] = "S32 Western Coastal Expressway",
["3211"] = "S3211 Zhuhai Airport Expressway",
["3213"] = "S3213 Gaolan Port Expressway",
["33"] = "S33 Nanshan–Guangming Expressway",
["39"] = "S39 Dongsha–Xingang Expressway",
["41"] = "S41 Guangzhou Airport Expressway",
["43"] = "S43 Guangzhou–Zhuhai West Expressway",
["45"] = "S45 Fosha–Jiangmen Expressway",
["47"] = "S47 Jiangman–Zhuhai Expressway",
["49"] = "S49 Xinhui–Taishan Expressway",
["51"] = "S51 Luoding–Yangjiang Expressway",
["55"] = "S55 Erenhot–Guangzhou Expressway Guangzhou Branch Line",
["75"] = "S75 Lanzhou–Haikou Expressway Zhanjiang Branch Line",
["81"] = "S81 Guangzhou Ring Expressway",
["82"] = "S82 Foshan First Ring Expressway",
["83"] = "S83 Meizhou Ring Expressway",
["84"] = "S84 Shaoguan Ring Expressway",
["86"] = "S86 Shenzhen Ring Expressway",
["105"] = "S105 Nansha Port Expressway",
["110"] = "S110 Guangzhou–Qingyuan Expressway",
["202"] = "S202 Huizhou–Yantian Expressway",
["209"] = "S209 Qingshuihe–Pinghu Expressway",
["301"] = "S301 Nanshan–Pingshan Expressway",
["302"] = "S302 Nansha Port Expressway Yuhuang Branch Line",
["303"] = "Huanan Expressway",
["304"] = "S304 Humen-Xiegang Expressway Humen Port Branch Line"},
["HA"] = {
arg = "route",
["1"] = "S1 Zhengzhou Airport Expressway",
["21"] = "S21 Puyang–Shangqiu Expressway",
["22"] = "S22 Nanle–Anyang Expressway",
["23"] = "S23 Gushi–Shangcheng Expressway",
["25"] = "S25 Anyang–Xinxiang Expressway",
["26"] = "S26 Taiqian–Huixian Expressway",
["28"] = "S28 Changyuan–Jiyuan Expressway",
["29"] = "S29 Xuchang–Xinyang Expressway",
["32"] = "S32 Alone the Yellow River Expressway",
["33"] = "S33 Alone the Taihang Mountain Expressway",
["37"] = "S37 Lankao–Xuchang Expressway",
["38"] = "S38 Xincai–Biyang Expressway",
["39"] = "S39 Jiaozuo–Xuchang Expressway",
["42"] = "S42 Yongcheng–Lingbao Expressway",
["46"] = "S46 Zhoukou–Pingdingshan Expressway",
["48"] = "S48 Shenqiu–Lushi Expressway",
["49"] = "S49 Jiaozuo–Tanghe Expressway",
["57"] = "S57 Mianchi–Xichuan Expressway",
["59"] = "S59 Sanmenxia–Xichuan Expressway",
["60"] = "S60 Shangqiu–Dengfeng Expressway",
["61"] = "S61 Yucheng–Yongcheng Expressway",
["62"] = "S62 Huaibin–Neixiang Expressway",
["63"] = "S63 Shangcai–Xin County Expressway",
["64"] = "S64 Neihuang–Linzhou Expressway",
["65"] = "S65 Lankao–Shenqiu Expressway",
["66"] = "S66 Neihuang–Hebi Expressway",
["67"] = "S67 Qi County–Yanjin Expressway",
["68"] = "S68 Changyuan–Xiuwu Expressway",
["69"] = "S69 Weishi–Linying Expressway",
["70"] = "S70 Shenqiu–Wuyang Expressway",
["71"] = "S71 Anyang Ring Expressway",
["72"] = "S72 Puyang–Huixian Expressway",
["73"] = "S73 Nanyang–Dengzhou Expressway",
["74"] = "S74 Lingbao Ring Expressway",
["75"] = "S75 Sanmenxia–Luoning Expressway",
["76"] = "S76 Luanchuan–Lushi Expressway",
["77"] = "S77 Zhengzhou–Nanyang Expressway",
["78"] = "S78 Xincai Queshan Expressway",
["79"] = "S79 Ye County–Lushan Expressway",
["80"] = "S80 Along the Huai River Expressway",
["81"] = "S81 Shangqiu–Nanyang Expressway",
["82"] = "S82 Zhengzhou–Shangqiu Expressway",
["83"] = "S83 Zhengzhou–Luoyang Expressway",
["8311"] = "S8311 Nanyang North Ring Expressway",
["84"] = "S84 Zhengzhou–Huixian Expressway",
["85"] = "S85 Zhengzhou–Shaolinsi Expressway",
["86"] = "S86 Zhengzhou–Jiaozuo Expressway",
["87"] = "S87 Zhengzhou–Yuntaishan Expressway",
["88"] = "S88 Zhengzhou–Luanchuan Expressway",
["89"] = "S89 Zhengzhou–Xinxiang Expressway",
["92"] = "S92 Luoyang–Lushi Expressway",
["94"] = "S94 Luanchuan–Lushi Expressway",
["95"] = "S95 Qinyang–Yichuan Expressway",
["96"] = "S96 Song County–Luanchuan Expressway",
["97"] = "S97 Jiyuan–Yichuan Expressway",
["98"] = "S98 Neixiang–Dengzhou Expressway",
["99"] = "S99 Dengzhou–Laohekou Expressway"
}
},
abbr = {
hook = "mask",
mask = "Road data/masks/CHN",
base = "state",
masked = "province",
default = "[province||%province%|] S%route%"
},
translation = {
arg = "province",
["BJ"] = {
arg = "route",
["11"] = "北京－承德高速公路",
["12"] = "机场高速公路",
["28"] = "机场北线高速公路",
["50"] = "五环路",
["51"] = "机场第二高速公路",
},
["SH"] = {
arg = "route",
["1"] = "迎宾高速公路",
["2"] = "上海－芦潮港高速公路",
["3"] = "上海－奉贤公路",
["4"] = "上海－金山高速公路",
["5"] = "上海－嘉定高速公路",
["6"] = "上海－南翔高速公路",
["7"] = "上海－崇明高速公路",
["12"] = "崇明－海门高速公路",
["16"] = "上海－宜兴高速公路",
["19"] = "新农－金山卫高速公路",
["20"] = "上海外环高速公路",
["22"] = "嘉定－安亭高速公路",
["26"] = "上海－常州高速公路",
["32"] = "上海－嘉兴－湖州高速公路",
["36"] = "亭林－枫泾高速公路"
},
["JS"] = {
arg = "route",
["5"] = "常熟－嘉善高速公路",
["9"] = "苏州－绍兴高速公路",
["19"] = "南通－无锡高速公路",
["29"] = "盐城－靖江高速公路",
["35"] = "泰州－镇江高速公路",
["39"] = "江都－宜兴高速公路",
["45"] = "宜兴－杭州高速公路",
["49"] = "新沂－扬州高速公路",
["51"] = "溧阳－黄山高速公路",
["55"] = "南京－宣城高速公路",
["59"] = "南京－和县高速公路",
["65"] = "徐州－明光高速公路",
["69"] = "济南－徐州高速公路",
["8"] = "泗阳－宿州高速公路",
["18"] = "盐城－淮安高速公路",
["22"] = "仪征－南京高速公路",
["28"] = "启东－ 扬州高速公路",
["32"] = "崇明－海门高速公路",
["38"] = "常熟－合肥高速公路",
["48"] = "上海－宜兴高速公路",
["58"] = "上海－常州高速公路",
["68"] = "溧阳－芜湖高速公路",
["72"] = "连云港港北疏港高速公路",
["73"] = "连云港港东疏港高速公路",
["75"] = "盐城－淮安高速公路阜宁－兴化－泰州支线",
["79"] = "上海－西安高速公路南通支线",
["80"] = "太仓港北疏港高速公路",
["81"] = "太仓港南疏港高速公路",
["82"] = "张家港港疏港高速公路",
["83"] = "苏州－绍兴高速公路无锡支线",
["85"] = "常熟－合肥高速公路溧阳支线",
["86"] = "上海－成都高速公路镇江支线",
["87"] = "长春－深圳高速公路南京支线",
["88"] = "南京禄口国际机场高速公路",
["92"] = "长春－深圳高速公路金湖支线",
["96"] = "新沂－扬州高速公路宿迁支线",
},
["GD"] = {
arg = "route",
["21"] = "广惠高速公路",
["105"] = "南沙港快速路",
},
["HA"] = {
arg = "route",
["1"] = "郑州机场高速公路",
["21"] = "濮阳－商丘高速公路",
["22"] = "南乐－安阳高速公路",
["23"] = "固始－商城高速公路",
["25"] = "安阳－新乡高速公路",
["26"] = "台前－辉县高速公路",
["28"] = "长垣－济源高速公路",
["29"] = "许昌－信阳高速公路",
["32"] = "沿黄高速公路",
["33"] = "沿太行高速公路",
["37"] = "兰考－许昌高速公路",
["38"] = "新蔡－泌阳高速公路",
["39"] = "焦作－许昌高速公路",
["42"] = "永城－灵宝高速公路",
["46"] = "周口－平顶山高速公路",
["48"] = "沈丘－卢氏高速公路",
["49"] = "焦作－唐河高速公路",
["57"] = "渑池－淅川高速公路",
["59"] = "三门峡－淅川高速公路",
["60"] = "商丘－登封高速公路",
["61"] = "虞城－永城高速公路",
["62"] = "淮滨－内乡高速公路",
["63"] = "上蔡－新县高速公路",
["64"] = "内黄－林州高速公路",
["65"] = "兰考－沈丘高速公路",
["66"] = "内黄－鹤壁高速公路",
["67"] = "淇县－延津高速公路",
["68"] = "长垣－修武高速公路",
["69"] = "尉氏－临颍高速公路",
["70"] = "沈丘－舞阳高速公路",
["71"] = "安阳绕城高速公路",
["72"] = "濮阳－辉县高速公路",
["73"] = "南阳－邓州高速公路",
["74"] = "灵宝绕城高速公路",
["75"] = "三门峡－洛宁高速公路",
["76"] = "栾川－卢氏高速公路",
["77"] = "郑州－南阳高速公路",
["78"] = "新蔡－确山高速公路",
["79"] = "叶县－鲁山高速公路",
["80"] = "沿淮高速公路",
["81"] = "商丘－南阳高速公路",
["82"] = "郑州－商丘高速公路",
["83"] = "郑州－洛阳高速公路",
["8311"] = "南阳北绕城高速公路",
["84"] = "郑州－辉县高速公路",
["85"] = "郑州－少林寺高速公路",
["86"] = "郑州－焦作高速公路",
["87"] = "郑州－云台山高速公路",
["88"] = "郑州－栾川高速公路",
["89"] = "郑州－新乡高速公路",
["92"] = "洛阳－卢氏高速公路",
["94"] = "栾川－卢氏高速公路",
["95"] = "沁阳－伊川高速公路",
["96"] = "嵩县－栾川高速公路",
["97"] = "济源－伊川高速公路",
["98"] = "内乡－邓州高速公路",
["99"] = "邓州－老河口高速公路",
},
["HE"] = {
arg = "route",
["32"] = "宣化－大同高速公路",
["9902"] = "新乐－元氏高速公路",
},
},
lang = "zh"
}
return CHN
Content Disclaimer
Informasi ini disarikan dari Wikipedia dan disajikan kembali untuk tujuan edukasi. Konten tersedia di bawah lisensi CC BY-SA 3.0. Kami tidak bertanggung jawab atas ketidakakuratan data yang bersumber dari kontribusi publik tersebut.
- The information displayed on this website is sourced in part or in whole from Wikipedia and has been adapted for the purpose of restating it. We strive to provide accurate and relevant information, however:
- There is no guarantee of absolute accuracy. Wikipedia is an open, collaborative project that can be edited by anyone, so information is subject to change.
- It is not intended to constitute professional advice. The content displayed is for informational and educational purposes only. For important decisions (e.g., medical, legal, or financial), please consult a professional.
- Content copyright. Wikipedia is licensed under the Creative Commons Attribution-ShareAlike License (CC BY-SA). This means that content may be reused with appropriate attribution and shared under a similar license.
- Responsible use. Any risk arising from the use of information from this website is entirely the responsibility of the user.