Wisconsin

From Wazeopedia
Update this page
USA Wisconsin.png

This page serves as the primary resource for editors of Wisconsin. Review all the sections to better understand how the guidelines for this state might deviate from the overall USA or worldwide guidelines. If you have any comments or questions about this page or state refer to the community links below.

We are now including GHO avatars and displayed names in the editor tables below, please add your details (instructions are here) or ask someone to do it for you.

Please contact Lonewolf147, poweruser10, or ojlaw before making any other changes to this Wiki.


Introduction

Wisconsin is a part of the Great Lakes region, which includes the states and/or territories of:

Illinois / Indiana / Michigan / Ohio / Wisconsin.


Mapping resources

Media-book-and-disc.png

Before editing the maps in Wisconsin, be sure to fully review and understand the editing manual.

The Waze user community follows the Waze etiquette guidelines discussed in the Wiki. Be sure to familiarize yourself with these guiding principals while editing the maps and this Wiki, as well as when communicating with other Waze users.

New editors should be sure to check out the following pages before editing the maps.
Best Map Editing Practice
Common Editing Mistakes
Waze Map Editor

  • The Wisconsin DOT provides various state, county, and Functional Classification maps.
  • GIS maps are maintained by the counties they serve.
  • See Wisconsin/Resources for lists of these maps.

The Statewide Parcel Map Initiative is an effort to create a digital parcel map for the State of Wisconsin by combining GIS data from city and county datasets into a single platform. You can access using this link, or by using the script. The WME WI GIS script is linked to Waze and will move when you pan around in WME.


Editing Scripts

There are many scripts available to assist in editing. Waze User Scripts

To display the county borders and zip code boundaries install this script WME US Government Boundaries

The following scripts are also highly recommended (and is not all-inclusive of available scripts):

WME Magic (this replaces the older Validator script)
WME Place Harmonizer
WME Place Interface Enhancements
Toolbox
WME Junction Angle Info
WME Chat Addon
WME UR Comments
WME HN Tool
WME Color Highlights
UROverview Plus
WME Speeds
WME Road Selector
WME Clicksaver

These scripts are more for advanced editing and monitoring:

WME Route Speeds
WME Route Checker
WME UR-MP Tracking
WME GIS Layers
WME GIS Buttons

Wisconsin Google Drive Resources
We have a Google Drive that we use for documents and spreadsheets to help with many areas of editing in our state. The link is: Wisconsin Google Drive



Community

People-in-forum.png

The Waze forum is a great place to find answers to previously asked questions and also a place to ask new ones. Below are links to the forums specific to Wisconsin.

Area Managers for Wisconsin can be found in the table below.

New editors should consider checking into the formal mentoring program available at no charge.


Wisconsin is part of the Great Lakes Region, that has its own wiki as well: Great Lakes Region Wiki

Our standard Welcome message to new editors can be found here: Welcome On that page (which can be freely modified to be personalized when copying and sending to new editors) you will also find a link to the form to gain access to the GLR Discord server. Discord is now our primary means of chat (this does not replace the Waze Forum). All editors are highly encouraged to join!

Wisconsin Editor Discord Channel

The Wisconsin editor community as part of the Great Lakes Region uses Discord to gather and communicate. This is where you can interact and chat with fellow editors along with your Area and State Managers. It will give you good insight into the best practices and policies in regard to map editing plus give an easy, convenient way for editors to stay in touch, ask questions, request downlocks or review of your work and get peer-to-peer mentoring.

By clicking the following link to join a Waze editor Discord Server, you are acknowledging that you have read, understood, and agree to the Waze Etiquette rules in their entirety. Click here to join.


Cities and towns

House.png

One of the most common errors when editing the maps is when an editor creates a road and does not confirm the road by setting the city and road name (or stating it has none).

Duplicate cities can be caused by incorrectly named segments and should be corrected following the guidelines in the duplicate cities article.

Towns in Wisconsin are in the process of being renamed. In order to help prevent duplicate names, Towns will have Twp added to the end of their names. This will help distinguish them from villages and cities and make navigation to Town addresses easier.

In the event there is a duplicate Town name, the County name in which the Town resides will be appended to the Town name.

This is a work in progress for the LAM's, SM's, and RC. Please DO NOT manually change any of the Town names at this time.

Towns will be named to have the Twp suffix. When there are duplicate town names, the County name will be appended in parenthesis. eg: Maple Grove Twp (Shawano)

See Wisconsin/Cities and towns for a list of all Towns in Wisconsin.

Military Bases

Wisconsin has one military base. Army base Fort McCoy, located in Monroe County.

Wisconsin follows the national guidelines for mapping military bases. National Wiki on Military Bases.

More specific details in regards to Fort McCoy can be found on this site: Link to be added soon


Major roads

4lane road icon.png

Wisconsin follows the general road naming and road type guidelines of the USA.

Functional Classifications

Wisconsin follows the Functional Classification (FC) system for the USA.

To help update the current Wisconsin roadways to the new functional classifications, go to the Wisconsin Functional Classification Inventory.
Links to the FC maps for the state of Wisconsin can be found on the Wisconsin/Resources page.


Minimum Road Lock Standard

Minimum Road Lock Standard
Segment Type Direction Level
 Freeway  5
 Ramp  HCS*
 Major Highway  3
 Minor Highway  3
 Primary Street  One-way 3
Two-way 2
 Street  One-way 2
Two-way 1
 Private Road  2
 |-|-|-|-|-|-|-|-|-| Railroad |-|-|-|-|-|-|-|-|-|  2
 • • • • Ferry • • • •   2
 ⁃        ⁃        ⁃        ⁃ Runway ⁃        ⁃        ⁃        ⁃  5
Other Named Types 1
Cones.png Construction Areas Cones.png
(changes without aerial images)
3

Terms

  • HCS - Highest Connecting Segment
Additional Info
Expectations

We understand that higher locks mean there is less available to lower rank and beginning editors. We would like to emphasize that Waze Map Editing is a community activity and, within the US, it is not possible to increase to rank 3 or above without community involvement. It is the responsibility of all members of the editing community to actively reach out, recruit, and mentor new editors.

It is OK to temporarily lock segments below standards for more junior editors. Area Managers are encouraged to monitor their areas for non-standard locks and follow up with other editors on any discrepancies. As a courtesy, any down-locks made outside your area should be brought to the attention of the local area manager.

One-Way Streets

The +1 locks on one-way segments originated as guidance from GLR RC GizmoGuy411 based on trends found while performing Area Manager Reviews: He would encourage editors to +1-lock one-way street/PS in order to explicitly signal, "Yes, the legwork has been done in order to confirm this segment really is one-way, and it's not a soft-directional issue."


Name Normalization

Wisconsin uses the following standards for road naming:

Freeways - I-###
US Highways - US-###
State Highways - WIS-###
County Highways - CH-XXX
Forest Roads - FR-###

There are no Township (Town) Roads in the state. All Town Roads are named, and those names will be used. The only exceptions would be if the road signage states differently.

Bridge and Overpass Segmentation Elevation (BOSE)

Please note that there are regional and national discussions ongoing for establishing standards beyond state level. If those changes come in opposition to what we are doing here, then we will be changing to follow suit.

Wisconsin has decided on a state standard for the segmentation of bridges and overpasses.

The National Wiki contains the standard information regarding proper elevation of segments. What we are doing in Wisconsin is expanding on those standards to create a more accurate representation of the segments.

Basic elevation is determined using the following rules:

  • All roads start at Ground elevation
  • If a segment is above another segment, it should be set to +1 relative to the lower segment's elevation (to account for multiple segments overlapping)
  • If a segment is a tunnel (not just an underpass), it should be set at -1, and Tunnel should be checked.

Bridges
Definition:

  • If a segment travels over a river or body of water, it is considered a bridge
  • If a segment travels over another segment, it is considered it a bridge (aka: overpass).
  • If a segment is artificially elevated to pass over ground level objects and natural features, it is considered a bridge.

Junctioning:
Place a junction at the start/end of the bridge where the land falls away.

  • If there is already a junction within 500 feet of the bridge, do not add a new junction.
  • Do not junction a bridge if it is less than 75 feet in length. If you believe you need to do so, contact an SM or LAM for approval.

Ramps
Ramps should always be set to Ground. The only time a ramp segment is set above or below ground is when it travels above or below another segment as a bridge or a tunnel. This is most often the case in large interchanges, like the Marquette interchange in Milwaukee. When a ramp traverses over or under another segment, you should follow the elevation guidelines listed above.

Do not segment (cut) a ramp like you would for a bridge, unless it takes on several different elevations.

Because of the complexity of interchanges, please contact your State Manager before making adjustments.

Special Note

This process was derived from the Seagull Effect created by the Australians. The process has been unofficially called ‘seagulling’. Please note that this word is a misuse of the Seagull Effect. Using it may have unintended connotations.


Additional Notes For Wisconsin

New Roads

It is important to remember to add House Numbers (HNs) when adding new roads to Waze. Waze will not be doing any future imports or merges of external data for house numbers. This ensures that Waze will provide accurate routing to those new addresses. If you come across a new road that is part of a new residential development but HNs are not yet available, please add the road to the Wisconsin New Development Tracking Sheet. Add any relevant information to the project that you may have. This sheet is used to keep track of new developments to ensure roads and HNs get added to the map as quick as possible.

Dirt Roads

All drivable unpaved (Dirt/Gravel) roads should be classified as per Functional Classification. The Unpaved checkbox should then be selected, as this will allow the "Avoid Dirt Roads" feature in Waze to behave properly.

Trails and non-standard roads that may require special equipment to drive on, should either not be mapped, or be classified as an "Off Road / Not Maintained" road with the Unpaved checkbox ticked.

Toll Roads

There are currently no toll roads in Wisconsin. No segments within the State of Wisconsin should be marked as 'Toll Road'.

Pedestrian Boardwalk, Walking Trail, Stairway

These should not be mapped without approval from a State Manager for Wisconsin or the Regional Coordinator. These segment types can cause routing issues even when not connected to a drivable segment.

Solid White Lines

It is not illegal to cross a solid white line in the State of Wisconsin, unless posted Wisconsin Statute 346.13(3).

Solid White Line Statute.png

Some examples are: road edge lines, lane divider lines, or on/off ramp lane lines. Even though it is not illegal, it is a safe driving practice to not cross these lines. When mapping on/off ramps, please follow national guidelines in the Junction Style Guide/Interchange page.
Off Ramp Example

On Ramp Example

There may be times when this is impractical, in such instances, contact a State Manager for further guidance.

Roundabouts at Freeway Interchanges

When there are roundabouts at freeway interchanges, leave the connecting overpass/underpass roads un-named. Waze will read forward to the next roundabout and provide proper TTS and visual prompts for the user to aid in proper lane selection at multi-lane roundabouts.
Here is an example of when not to name the segment(s): Do Not Name

U-Turns

U-turns in Wisconsin are permitted when:[1]

  1. The u-turn can be made in safety and without interfering with other traffic.
  2. Not upon any curve, or upon the approach to or near the crest of a grade, where the vehicle cannot be seen by the driver of any other vehicle approaching from either direction within five hundred (500) feet.
  3. Not explicitly prohibited by signage or local municipal law.
  4. You are not required to back up during the course of the u-turn in order to complete it.

For Waze routing, u-turns should only be enabled where they provide the potential for improved routing, which includes recovering from missed turns. A common example is a median-divided primary street that has homes/businesses with their driveways/entrances directly on it, where reaching them would otherwise require lengthy, multi-turn deviations through side roads in order to end up on the correct side of the median.

U-Turns are not allowed on any Freeway or Expressway.

^1 Wisconsin Statute 346.33

Construction Zones

If a construction zone is expected to last one week or longer, the following options are allowed to be made to the area:

  • Change speed limit to lower posted limit
  • Add crossovers for traffic changes and make one-way Freeway segments two-way.

If any or all of these changes are made, add the construction zone to the following spreadsheet for easy reference and followup by other editors. WI Construction Zones


Special roads

Drivable roads

Wisconsin follows the standard USA guidelines for all of the following special road types.

Non-drivable roads

Review the Wiki guidelines for non-drivable roads to ensure compliance with the general guidelines.


As of April 23, 2018 (2018-04-23), the new road type  Passageway  is available in the WME. The routing, display, and restriction details of  Passageway  are not finalized, and it is not functional on the routing servers (it acts like a  Local Street ). At this time, DO NOT use the  Passageway  road type in the USA without explicit champ approval for each instance.
alley


Alleys

Generally alleys are not mapped in Wisconsin. Alleys are drivable roads passing between or behind buildings and are not intended for thru-traffic. They can be an important component in routing when primary access is not on a local street or drivers start or end a route on an alley. However, their existence also presents many routing problems. Please avoid mapping alleys unless they meet the criteria set below:

Alleys should only be considered for mapping when one of the following criteria is met:

a) the main access to a business entrance is on an alley,
b) a parking lot entrance is in an alley,
c) current GPS tracks support a residential alley that is frequently used and would benefit from being added to the map, or
d) a UR indicates an alley should be added.

Please do not add every alley in a residential neighborhood.

All alleys should have their road type set to  Parking Lot Road , should be named "Alley", and speed limit should be set to 15mph unless otherwise posted.

Please consult with an LAM or SM before adding or removing alleys to verify whether a certain alley would meet the criteria to be mapped.

Left-turn lane

Should the left turn lane be mapped?

Left-turn lanes (LTL) should only be mapped in very limited circumstances-

  • When there is a raised curb or median between the left turn lane and the through lanes for a long distance before the intersection that the driver might overshoot while waiting for a delayed "turn" audible. Wisconsin DOT calls these slotted left-turn lanes [1] [2]. The main reason to map these in Wisconsin is the DOT has built many slotted left-turn lanes.

-or-

  • When the turn lane physically separates from the main road well in advance of the intersection
  • When there are user complaints (Update Requests) that the audible was too late, or that the map should have shown a left-turn lane

The routing server does not play nice with LTLs and will often create unnecessary right-turn/ U-turn or U-turn/ right-turn to route a left through these intersections. Often a junction box is required to help with routing when LTLs are created.

When in doubt, leave it out. Each left-turn lane complicates the map and adds to your workload when the time comes to check connectivity, direction, name, etc.

Road type

Left turn Lane 1.PNG
Essentially these left-turn lanes are the same road as the through road, we are just adding a segment for better turn instruction timing, so they should be mapped using the same road type as the through road.
  • Ex: Street to Minor Highway should be Street type.
  • Ex: Minor Highway to Primary Street should be Minor Highway type.
  • Ex: Primary Street to Primary Street should be Primary Street type.

Road name

In most cases, checking None for the Street name will be sufficient. Navigation instructions will simply use the name of the next segment to which the left-turn lane segment connects.

If there are specific signs at the intersection which are confusing or contrary to the destination road segment name, then a name can be applied to the left-turn lane.

Geometry and Turn restrictions

In general using geometry is sufficient for the desired turn instructions- keep left instruction entering the turn lane and turn left instruction at the turn. When geometry won't work use TIOs for these instructions.

Divided road

Left turn lane2.PNG
Add turn restrictions to the left turn lane segment to prevent U-turn(if applicable) and right turns.
Left turn lane3.PNG
Add turn restrictions to the adjacent through lane segment left turn(to force use of the left turn lane).

Non-divided road

Left turn lane4.PNG
Add turn restrictions to the left turn lane segment to prevent right turns.
Left turn lane5.PNG
Add turn restrictions to the adjacent through lane segment left turn(to force use of the left turn lane) and prohibit U-turns.

Speed Limit 

Left-turn lanes should be mapped using the speed limit of the segment feeding into the left-turn lane(unless signed otherwise).

Speed Limits

Wisconsin has no variances from the USA Speed Limits wiki: USA Speed Limits Wiki

Speed Limit Effective-Location for Wisconsin

Speed Limits in Wisconsin change at the sign. This is important when determining where speed limit changes should be marked on the Waze map. USA guidance for states that "change at the sign" is given here.

Where speed limits change is an important decision for clear guidance to drivers. There are many considerations for appropriately marking speed limit changes on the map. Editors, especially new editors, should be familiar with the USA Speed Limits wiki, a link to which is shown above.

For example, if there is an intersection within 200 feet of the speed limit sign, then the speed-change location should be made at that intersection. If the speed-change location is within 200 feet of an existing junction node, not an intersection, then we don't add a new junction node.

Alleys in Wisconsin - max speed is 15 mph unless posted otherwise.

Always refer to the USA Speed Limits wiki for guidance, and check with your Area or State Managers for clarification if needed.


Wisconsin Legislature: 346.57

Update Requests

Wisconsin is using the Great Lakes region Update Requests Response System:

Overview

NOTE: all day values are relative to the date the FIRST editor response is sent to the reporter.

Response Timeline

  • Day 0: the first editor who is able to respond to UR should attempt to resolve the UR. If they are successful, they should comment as such in the UR and mark it closed. If more information from the reporter is required to make progress towards closure, a response should be sent to the reporter containing the information needed for resolution
  • Day 4+: polite reminders should be sent to reporters who have not responded to the initial request for information at any time, provided at least four full days have elapsed since the initial response was sent.
  • Day 8+: URs may be noted as closed due to lack of reporter response at any time, provided at least four full days have elapsed since the followup message was sent

Shared Ownership:

  • All editors are considered to have equal ownership of and responsibility for all URs in the Great Lakes Region.
  • All editors, regardless if they have worked the UR previously, may send any of the responses described above, provided they adhere to the minimum time spacing guidance between responses.
  • All editors are explicitly encouraged to attempt resolving URs at any point during their lifecycle, even if others happen to be actively working it at the same time

Notes:

  • The ideal timeline for UR response is when responses are sent as early as the minimum required time spacing between messages permits; experience has reliably shown that UR response rates are much higher when editors are able to send responses promptly
  • While strongly recommended, it is not required to send the followup message.

Process Chart

GLR - UR Process 20150606.png


Closures

When managing a section of roadway under construction or being closed for a major event, follow the Wiki guidelines on construction zones and Real time closures.

Closure information for the state of Wisconsin can be found on the Wisconsin 511 Construction Projects web page.

Because the WiDOT has partnered with Waze via the Connected Citizens Program (CCP), the Large Area Managers and State Managers have extra resources for aiding in state road closures. If you have any questions regarding a closure, or a MP closure request, please contact your LAM, Lonewolf147, poweruser10, or ojlaw.


Places

Wisconsin follows the USA standard for Places. Do not deviate from the guidelines without first obtaining consensus to do so via the state forum linked on this page.

Locking Standards

Places should be completed as fully as possible any time they are created or updated. At a minimum, editors should:

  • verify correct spelling of the name, using the guidelines below
  • complete the address, to help when choosing among search results in the app, and
  • ensure the correct location of the Point or Stop Point, to guide drivers to the correct location. Note that this may not always be on the street side of the location.

Phone numbers and opening hours are also particularly helpful to Wazers. Complete them whenever possible, using an online search, if necessary. Photos should help Wazers recognize the destination when they arrive.

Recommended phone number formats: (414) 123-4567 or 715-123-4567 Others may not auto-dial properly in some phones. If you are running WMEPH, the script will automatically add the parentheses.

When completed, places should be locked, to prevent inadvertent damage. Please don't lock places to their highest level until most of their information is completed, but do lock to a level higher than 1, once you have verified any information, to help protect from accidental damage through client submissions. The following are recommended levels:

Airport : 5
Hospital : 4
Fire Station : 4
Police Station : 4
Large areas - (State Parks, if mapped, etc.) : 4
Gas Station : 3

Most other places should be locked at 3, once completed.

If a place is locked higher than its recommended lock level, please contact the last editor or an SM before making any edits.

Naming Standards

PLACE NAMING STANDARDS/HARMONIZATION IS CURRENTLY UNDER NATIONAL REVIEW. USE THE CURRENT INFORMATION UNTIL THE REVIEW IS COMPLETE. UPDATES WILL BE POSTED ON STATE AND NATIONAL WIKI

We are standardizing the naming of most public facilities and businesses. This makes search results more consistent and useful, and gives Wazers a more professional and uniform experience. The names have been designed to work well with instant search, regular search, and to be clear and concise in the map display. Please follow these guidelines when naming the places described below.

Places which are part of a larger area place (e.g. place points for parking lots in a university area, separate ER entrances in a hospital area, etc.) should be named with their unique name followed by a hyphen and the name of the larger area they belong to. For example "Student Parking Lot C - StudyHard University"

Government Agencies (selected)

All places for the following agencies should be named according to the standards as follows:

City and County Offices: City or County Name followed by City Hall or department or agency as appropriate, for example:

"Milwaukee City Hall"
"Kenosha County Probation"
"Door County Administration Center"

Police and Sheriff Department: City, Agency or Division Name followed by "Police Dept" or "Sheriff Dept", for example:

"Wausau Police Dept"
"Kenosha County Sheriff Dept"


Fire Department: Agency Name or abbreviation followed by “Fire Dept – “ and the station number. For example:

"North Shore Fire Dept - Station 5"
"Wauwatosa Fire Dept"
"Milwaukee Fire Dept - Engine 9"


United States Postal Service: Start the name with CDP or Station name, then append “Post Office”. Place the City name and the ZIP code of the Post Office in the Description box, so it will be viewable in the app GO page. Alternate name should be “USPS”. For example:

"Fort McCoy Post Office"
"General Mitchel Airport Post Office"
"Madison Post Office"


US VA Hospitals/Centers/Clinics: Should be named with their official name as the primary name. For VA hospitals/medical centers "(US Veterans Only)" should be added to the end of the primary name, and as the first line of the description. In the primary name, "VA" should be expanded as "Veterans Affairs", so as not to cause a TTS conflict with Virginia. Names can be shortened to remove extraneous words; for example, replace "Campus of the" from the official name with a hyphen (-). Any colloquial names should be added as alt names, so they are returned in search results, and also at the beginning of the description, so they are visible on the place preview page in the client. Some examples:

"Veterans Affairs - Tomah (US Veterans Only)"
"Beaver Dam Veterans Medical Clinic"
"Veterans Affairs - Clement J. Zablocki Medical Center (US Veterans Only)"

Place Name Harmonization

Name spellings, formatting, and websites are standardized for chain or franchise businesses across the United States so that Wazers will receive consistent results when searching in the client, no matter their location. We recommend you install WMEPH to help keep places standardized.

Misc Notes

Boat Launches

Boat Launches can be mapped as a PLR to the parking area and a Point Place. Do not map the actual ramp to the waters edge. If there is no off street parking for the launch, only map the Point Place. The Wisconsin Department of Natural Resources (DNR) created a statewide inventory containing over 2,000 identified public boat access sites and over 100 developed shore fishing sites. It can be accessed here http://dnr.wi.gov/topic/Lands/boataccess/ There is another site that has launch names and other details here http://wisconsinslakes.com/

Naming of boat launches should be Boat Launch - {water name} (location if needed). For example, Boat Launch - Lake Superior (Hot Pond Overlook). They should be categorized as Outdoors.

If a launch has a fee to use, or any restrictions, put the details in the description of the Place.

Area and Point places for Interchanges, Exits and Junctions

Area and Point places for Interchanges, Exits and Junctions are NOT used in Wisconsin for normal mapping.

Use a comment point or a comment area when special information needs to be noted about a location.


House Numbers with Letters

Currently, Waze does not support alphanumeric house numbers, with the only exception a single letter at the end of a number (123x). This is a current known issue and is being worked on by the programmers. In the mean time, Wisconsin has a work around for this.

Create a Place point for the location and put the full street address, with house number, as the Name. Leave the category as Other.

Add a PL to the Place in the following spreadsheet so that it can be tracked.

Wisconsin Alphanumeric House Number Spreadsheet

Once alphanumeric numbers are finally fixed, the spreadsheet can be used to locate all the Places and properly convert them. If an address is “W1234”, do NOT change it to “1234W”. These two addresses are different. Alphanumeric addresses are determined based on their area’s street grid system.


See Wisconsin/Places for guidance in Wisconsin that may not be universal to all other states and territories.


Cameras

Not every camera-looking device at an intersection is a speed or red light camera. Generally speaking:

  • Camera2true.png
    Rlc truvelo speed cam.jpeg
    a speed camera takes a photograph of a vehicle when it passes by the camera at too high a speed.
  • Camera4true.png
    Rlc white.jpeg
    a red light camera takes a photograph of a vehicle that enters an intersection after the light is red. In some areas, it takes the photograph when a vehicle is not clear of the intersection some period after the light turns red.

Be sure to know your cameras before accepting new camera reports.

When adding a camera, be sure to review the camera placement recommendations.

Laws regarding speed and red light cameras vary between the states and territories, so be sure to understand the details of camera legality in Wisconsin.

Wisconsin legislature has not approved the use of red-light or speed cameras anywhere in the state. These camera types should not be mapped in Waze. Please delete any of these cameras that get posted to the map!



Based on information researched at the time this page was created, red light and speed cameras are prohibited statewide in Wisconsin.

No other camera types should be mapped in Waze.


To do list

To do list.png

Many states and territories keep an active list of pending or closed actions that need to be done in the state by the editors. All editors are welcome to contribute to the list of activities.

This will be used for links to Google docs that provide areas of To-Do for SM's, AM's and active Editors in the state.

Ongoing To-Do:

  • Remove House Numbers from freeways (ongoing project). Be sure to re-add the numbers to the proper frontage road (or other access road), and to add the name of the freeway as an alternate name to that access road. See here as an example [3]

Special State Programs: See Wisconsin/Special Programs to access the Temporary AM Areas program page.

Wisconsin Large Area Manager (LAM) Program: The state of Wisconsin has initiated a program called Large Area Manager (LAM), which is an accepted program in the Great Lakes Region (GLR). Please see this page for details on the role: Wisconsin LAM Role



Area Managers

The table below identifies the editors also designated as Area Managers or higher who are editing in Wisconsin. If you have any questions, please consider contacting them directly as needed. If you are an Area Manager that covers Wisconsin, or a USA Country Manager that does a lot of work in Wisconsin, please add yourself to this list (alphabetical by username) in the correct rank section.

The editor who also serves as the Regional Coordinator for Wisconsin is automatically listed at the top of the table. That editor may not be highly active in this state and therefore may not be listed separately in the table.

Wisconsin — Area, State, Country Managers, and Regional Coordinators
Regional Coordinator(s):
[RC] GizmoGuy411 (PM)  Profile L6.png
[ARC1] Roadtechie (PM)  Profile L6.png
[ARC2] SkiDooGuy (PM)  Profile L6.png
Username
"
  GHO Display Name
Area Managed Comments
Country Managers (Great Lakes region)
(Add to or edit Country and State sections of table)
Bigbear3764(5) [PM] Profile L5.png
Avatar bigbear3764.jpg
  bigbear3764
Countrywide Badge CountryManager.pngBadge StateManager.pngBadge Mentor.png
Illinois State Manager
JustinS83(6) [PM] Profile L6.png
JustinS83.png
  JustinS83
Countrywide Badge LocalChamp.pngBadge StateManager.pngBadge Mentor.png
USA LC & OH

SM

TheChrisK(5) [PM] Profile L5.png Countrywide Badge CountryManager.pngBadge StateManager.pngBadge Mentor.png
Resident of Nebraska
State Managers (Great Lakes region)
Lonewolf147(5) [PM] Profile L5.png
Avatar lonewolf147.jpg
  Scott Falk
Statewide Badge StateManager.png
Wisconsin State Manager
ojlaw(5) [PM] Profile L5.png
Avatar ojlaw.jpg
  ojlaw
Statewide Badge StateManager.pngBadge AreaManager.pngBadge Mentor.png
WI SM / IL, MN & ND AM
poweruser10(5) [PM] Profile L5.png
Avatar poweruser10.png
  Glenn poweruser10
Statewide Badge StateManager.pngBadge Mentor.png
Wisconsin State Manager
Area Managers
(Add to or edit this section)
doryphore_6(5) [PM] Profile L5.png Statewide Badge StateManager.png
Michigan State Manager
davenh(5) [PM] Profile L5.png Primarily Milwaukee/SE Wisconsin, also southern half of WI
tango259(5) [PM] Profile L5.png
R
  Ryan
Large Area Manager - SouthEast Region Badge AreaManager.pngBadge Mentor.png
Resides in Milwaukee
JaazzBoo(4) [PM] Profile L4.png
Avatar JaazzBoo.jpg
  Jaazz
Large Area Manager - NorthCentral Region Badge AreaManager.pngBadge Mentor.png
Based in Waunakee
tinfoilhattie(4) [PM] Profile L4.png
C
  Casse Langford
Milwaukee Badge StateManager.png
Minnesota State Manager
dmee92(3) [PM] Profile L3.png Area Manager - Racine/Kenosha Badge AreaManager.png
Based in Minnesota
kb7qdi(3) [PM] Profile L3.png Large Area Manager - NorthWest Region, Ashland County area SE Wisconsin
WarhawkTrombone(3) [PM] Profile L3.png
Avatar warhawktrombone.jpg
  Geoff WarhawkTrombone
Large Area Manager - SouthWest Region, Kenosha Badge AreaManager.png
Based in Kenosha


Other states and territories

USA CommonState.png
The other states and territories of the USA can be found in the navigation box below. Press the "show" button to open the box.

purge

About this page