Wisconsin/County Highway Relations

From OpenStreetMap Wiki
Jump to: navigation, search

Tagging information

WIS County blank.svg

County highways in Wisconsin have one-, two-, or three-letter designations preceded by CTH (for "County Trunk Highway"). Thus, an example of a reference for a county highway might be ref=CTH OSM.

Raw TIGER data generally does not include this designation as a reference (ref=*) tag, and often gives the letter designation in the main name tag (name=*). When this is encountered, first check the TIGER tags on the way to see if a local name exists in addition to the letter designation. If so, it is suggested to replace the main name value with the way's actual name, and add a ref=* tag in the standard form above. For instance, here is an example how a street named Western Road (part of Ozaukee County Highway T) appeared with raw TIGER tags, and how to correct it:

Example correction of TIGER tags for county highways
Raw tags Corrected tags
highway=tertiary
name=County Highway T
name_1=Western Rd
Symbol Arrow right white green.svg highway=tertiary
name=Western Road
ref=CTH T

The tiger namespace tags (keys beginning with "tiger:") are not shown since they can be ignored. However, they sometimes can be useful to look at for additional information such as what the street's actual name is, when one exists.

Be aware that not all Wisconsin letter designated county roads have a road name drastically different from their designation. For example,"County Road O" is the postal street address name associated with this portion of County Trunk Highway O in Outagamie County. If you cannot find an alternate name, research to see if one exists, or in fact none exists, and tag accordingly.

Relations

At a minimum, all Wisconsin County Trunk Highway relations should contain the following tags and associated values:

Key Value Discussion
type=* route Required. This is a "route" relation (as opposed to other types of relations)
route=* road Required. This route is part of the roadway network for automobiles (as opposed to a bus route, hiking route, cycling route, etc.)
name=* common name Required. The full name for this county route. Almost all have the name/ format CountyName County Trunk Highway AAA. If a county has spaces, use them: Fond du Lac County Trunk Highway RP
network=* US:WI:CountyName or

US:WI:CountyName:Modifier

Required. Most in this list will have the route identifier US:WI:CountyName. Again if a county has a space, that's used here: US:WI:Fond du Lac

County Trunk Highways that have route modifiers (Spur, Alternate, etc.) should have that included. Applicable examples include US:WI:CountyName:Spur, and US:WI:CountyName:Business.

is_in:state=* WI Required. All Wisconsin County Trunk Highways should be tagged with this value.
ref=* reference letter or letters Required. The route number. Examples: A, RP, ZZZ. 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.
wikipedia=* Wikipedia Page Title Required if article exists. Nominatim uses the wikipedia key to weight/rank returned search results, so it's a good idea to include this. This being said as of this writing, no specific County Trunk Highway Wikipedia articles exist for Wisconsin, so in practice this tag will not be used.
symbol=* url Required if SVG file exists. The URL of a graphical representation of the route's symbol, in SVG format. See Wikimedia Commons: Wisconsin County Highway Shields for the list of available SVG files.
modifier=* type 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.
direction=* northsoutheastwest If applicable. This tag is used on Wisconsin County Trunk Highways that are divided on the map along their entire length. 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 Brown County Highway G should be named Brown County Trunk Highway G 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.

Individual ways

At a minimum, all Wisconsin County Trunk Highway ways should contain the following tags and associated values:

Key Value Discussion
highway=* type Required. Depending on the functional classification of the road, this will be one of motorway, trunk, primary, secondary, tertiary, or unclassified.
ref=* road Required. Any way that is part of a Wisconsin county highway should have the reference CTH AAA as part of this field. In the case of route concurrencies, separate each with a semicolon, without spaces between the references. When two county highways share a way, it's suggested ordering them alphabetically, e.g. CTH A;CTH GG. When there is a modifier for the highway (Business, Truck, Spur, etc.) this should be appended to the end of the field, e.g. CTH F Business. Doing this allows mapping tools that do not yet understand route relations (above) to print something using the older per-way reference standard.
name=* common name Required. The common name for this portion of the county route as indicated by signs. When a local name does not exist for the way, the US Postal Service generally recognizes County Highway AAA or County Road AAA; check which is applicable. When a local name does exist, this field should be that name, e.g. Main Street.
Route relation County route relation Required. Each county 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.
alt_name=* County Highway AAA or County Road AAA If applicable. If a local name exists for the way, you may wish to add County Highway AAA or County Road AAA as an alt_name in cases where postal addressing allows both. This should be checked on a per-way basis for validity.

Relations

County Letter(s) Relation Progress and notes
Brown U Relation 4010084 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
Z Relation 4012031 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX) Continues into Outagamie as Relation 4012032 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
Dane AB Relation 4497581 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
BB Relation 4497613 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
BW Relation 4497648 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
M Relation 4500214 (iD, /full JOSM, Potlatch2, history, analyze, manage, XML, GPX)
MC Relation 4497656 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
Q Relation 4497725 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
Dodge D Relation 5179708 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX) Mostly in Washington as Relation 5179657 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
Fond du Lac B Relation 148310 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
G Relation 148311 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
RP Relation 4037595 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX) Not complete.
Grant V Relation 121132 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
Langlade M Relation 4018919 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
P Relation 4018916 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
Lincoln X Relation 116322 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
Milwaukee S Relation 1663031 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
Outagamie A Relation 4009382 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
AA Relation 4012060 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
B Relation 4012399 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
BB Relation 4012052 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX) Lies on the Outagamie-Winnebago county line.
C Relation 4010059 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
CA Relation 4012036 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
CB Relation 4012037 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX) Continues into Winnebago as Relation 4012038 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
CC Relation 4012072 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
CE Relation 4012035 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX) Small part extends into Brown county.
D Relation 4009480 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX) Largely on the Outagamie-Waupaca county line.
DD Relation 4009490 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
E Relation 4009349 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
EE Relation 4009341 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
F Relation 4010154 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
FF Relation 4010155 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
G Relation 4010075 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
GG Relation 4012012 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
GV Relation 1077642 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
H Relation 4011991 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
HH Relation 4012033 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
I Relation 4011443 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX) Labeled Waupaca (mostly in that co.)
J Relation 4012068 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
JJ Relation 4009384 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
K Relation 4012034 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
KK Relation 3854061 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
M Relation 4009440 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
MM Relation 4012053 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
N Relation 4012056 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
NC Relation 4015584 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
O Relation 4009387 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
OO Relation 4012064 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
P Relation 4012488 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
PP Relation 4012042 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
Q Relation 4012078 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
S Relation 4009524 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
T Relation 3837964 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
TT Relation 3855513 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
U Relation 4011993 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
UU Relation 4012080 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
VV Relation 4010060 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
W Relation 4009489 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
WW Relation 4009483 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
X Relation 4010081 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
XX Relation 4010125 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
Y Relation 4010061 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
Z Relation 4012032 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX) Continues into Brown as Relation 4012031 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
ZZ Relation 4012004 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
Ozaukee NN Relation 5179559 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX) Continues into Washington as Relation 5179557 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
Saint Croix A Relation 3126079 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
B Relation 6330860 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
BB Relation 6330861 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
C Relation 6330868 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
CC Relation 6330869 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
D Relation 6330882 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
DD Relation 6333184 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
E Relation 6330793 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
F Relation 6330879 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
FF Relation 6330880 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
G Relation 6330795 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
GG Relation 6333218 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
H Relation 6330887 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
I Relation 6330794 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
J Relation 6333171 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
JJ Relation 6333259 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
K Relation 6333172 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
KK Relation 6333173 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
M Relation 6333260 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
MM Relation 6333274 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
N Relation 6333492 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
NN Relation 6333493 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
O Relation 6333494 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
P Relation 6333499 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
Q Relation 6333580 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
S Relation 6333581 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
SS Relation 6333582 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
T Relation 6333662 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
TT Relation 6333663 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
U Relation 6333670 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
UU Relation 6333672 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
V Relation 6336289 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
VV Relation 6336306 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
W Relation 6336300 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
X Relation 6336309 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
Y Relation 6336336 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
YY Relation 6336341 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
Z Relation 6336342 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
Sauk B Relation 4004720 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX) Not finished past Plain, WI. Continues to Sauk County/Richland County line.
C Relation 4004284 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
D Relation 4004285 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
DD Relation 4004998 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
E Relation 4004995 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
I Relation 4004287 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
O Relation 4004719 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
PF Relation 4004283 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
W Relation 4004286 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
Sheboygan A Relation 148317 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
CC Relation 1345821 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
F Relation 148313 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
I Relation 1345820 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
V Relation 148299 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
W Relation 148315 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
Walworth O Relation 116345 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
Washington C Relation 5179569 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
D Relation 5179657 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX) Small part extends into Dodge County as Relation 5179708 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
G Relation 5179625 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
I Relation 5179599 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
MY Relation 5179835 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
NN Relation 5179557 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX) Continues into Ozaukee as Relation 5179559 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
P Relation 5179585 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
PV Relation 5179634 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
W Relation 5179723 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
WW Relation 5179715 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
Z Relation 5179568 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
Waupaca BH Relation 4015876 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
D Relation 4009480 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX) Largely on the Outagamie-Waupaca county line.
H Relation 3855546 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
I Relation 4011443 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX) Small part extends into Outagamie county.
W Relation 3855488 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
Winnebago AP Relation 1082752 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)
BB Relation 4012052 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX) Lies on the Outagamie-Winnebago county line.
CB Relation 4012038 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX) Continues into Outagamie as Relation 4012037 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX)