Required. The full name for this state route. Almost all have the name and format State Trunk Highway ###. A few exceptions to this exist, such as that for the 32nd Division Memorial Highway, route 32.
Required. Most in this list will have the route identifier US:WI. State Trunk Highways that have route modifiers (Spur, Alternate, etc.) should have that included. Applicable examples include US:WI:Spur (for 794 Spur), and US:WI:Business (for Business 57).
Required. The route number. Examples: 13, 441, 54. If a route modifier exists (Spur, Truck, Alternate, etc.) it should not be present in this key. Instead, it should be incorporated into the 'modifier' key, and the 'network' key.
Required. The text of the Wikipedia page title discussing this route, such as Wisconsin Highway 114. If a route with a modifier exists but does not have a page of its own, link to the parent route (e.g., 794 Spur's relation can link to Wisconsin Highway 794 if an article does not exist for the spur). Nominatim uses the wikipedia key to weight/rank returned search results, so it's a good idea to include this.
If applicable. Some routes have a "tab" (officially a "banner") attached to the route number that distinguishes it from other, related routes. Usually the text of the attached tab should be used; common examples as per taginfo include "Alternate", "Business", "Bypass", "Spur", "Scenic", "Toll", "Truck". Note that these values are capitalized! If the modifier tag exists, it should also be incorporated into the network tag.
If applicable. This tag is used on Wisconsin State Trunk Highways that are divided on the map along their entire length (as divided highways / dual carriageways, such as Highway 24) These highways must have two separate route relations, one for each direction of travel. In such cases, the direction key should have a value of the the cardinal direction on the tab of the sign, and it should also be used in the relation's name; for example, the route relation for eastbound Wisconsin 24 should be named State Trunk Highway 24 east and should have the key and value direction=east. Note the signed direction may not directly match the compass direction of travel; the signed direction should be tagged.
Shield generation for Wisconsin State Trunk Highways (which rely on the above values being set properly) can be verified at the following link, as of September 2014: [1]
Individual ways
At a minimum, all Wisconsin State Trunk Highway ways should contain the following tags and associated values:
Required. Any way that is part of a Wisconsin state highway should have the reference WI ### as part of this field. In the case of route concurrencies, separate each with a semicolon, without spaces between the references. When two State highways share a way, it's suggested ordering them numerically, e.g. WI 29;WI 32. When there is a modifier for the highway (Business, Truck, Spur, etc.) this should be appended to the end of the field, e.g. WI 32 Business. Doing this allows mapping tools that do not yet understand route relations (above) to print something using the older per-way reference standard.
Required. The common name for this portion of the state route as indicated by signs. When a local name does not exist for the way, the US Postal Service recognizes the format State Highway ###. When a local name does exist, this field should be that name, e.g. Main Street.
Required. Each state route that this way is a part of should be a member of its respective route relation. If the way handles traffic in both directions, a role need not be assigned. If the way is handling traffic in only one direction (typical on divided highways or on highway links), then this way should be assigned the relation role north, south, east, or west, whichever signed direction of traffic the way handles for the route.
If applicable. If a local name exists for the way, you may wish to add State Highway ### as an alt_name in cases where postal addressing allows both. This should be checked on a per-way basis for validity.
See Wisconsin Scenic Byways program for more information on this program, established in 1999. Distinct from Rustic Roads, below. Sign banner exists and is posted on roads, but no Commons SVG symbol exists as of yet.
910786
