User:Tango259/Minnesota MapRaid 2020 View history

Mapraid
VisualWikitext
(Created page with "<!-- XXX --> {{mbox|type=warning|text= {{Mapraid dates |raidname=Minnesota MapRaid |formlink=https://docs.google.com/forms/d/1A01RMpZuR0BdU7UcgO-vi0OtJ6gUX2I_vAfTGbMEOQQ/viewf...")
 
 
(27 intermediate revisions by the same user not shown)
Line 1: Line 1:
<!-- XXX -->
{{mbox|type=warning|text=
{{mbox|type=warning|text=
{{Mapraid dates
{{Mapraid dates
|raidname=Minnesota MapRaid
|raidname=Minnesota MapRaid
|formlink=https://docs.google.com/forms/d/1A01RMpZuR0BdU7UcgO-vi0OtJ6gUX2I_vAfTGbMEOQQ/viewform?edit_requested=true
|formlink=https://docs.google.com/forms/d/1A01RMpZuR0BdU7UcgO-vi0OtJ6gUX2I_vAfTGbMEOQQ/viewform?edit_requested=true
|endreg=2020-06-30T0000
|endreg=2020-06-30T0000  
|startraid=2020-07-12T1900
|startraid=2020-07-12T1900
|endraid=2020-07-24T2359}}
|endraid=2020-07-25T2359}}
}}
}}
<!--
<!--
Line 13: Line 12:
-->
-->


<!--
[[File:MNMR-Llama.png|frameless|500x500px|center|alt=]]<br />
  Put the mapraid meme here.  Something like:
<div style="width:550px;height:200px;  margin-left:auto; margin-right:auto;border: 1px solid black;">
  [[File:Mapraid JerseyShore meme3.jpg|frameless|550px|center]]
</div>
-->
<div style="width:580px;height:430px;  margin-left:auto; margin-right:auto;border: 1px solid black;">
  [[File:KSMO_MapRaid_meme1.jpg|frameless|580px|center]]  
</div>
 
==Welcome==
==Welcome==
The '''Minnesota MapRaid''' will be '''12 July 2020 at 19:00 UTC through 24 July 2020 23:59 UTC''' (approximately).  
The '''Minnesota MapRaid''' will be held '''12 July 2020 at 19:00 UTC through 25 July 2020 23:59 UTC''' (approximately).  


Welcome to the American Great Plains! Thank you for your assistance big and small in improving the map throughout Minnesota. A MapRaid is a gathering of editors from across the editing community to edit an area of the map in a burst of activity. While you as an editor will receive editing area for the entirety of both states for the raid duration (for administrative purposes), you will also receive a specific group assignment to focus on a subset of that area and a set of localized priorities. It will be your task to work with your group to help achieve them!
Welcome to the American Great Plains! Thank you for your assistance big and small in improving the map throughout Minnesota. A MapRaid is a gathering of editors from across the editing community to edit an area of the map in a burst of activity. While you as an editor will receive editing area for the entirety of both states for the raid duration (for administrative purposes), you will also receive a specific group assignment to focus on a subset of that area and a set of localized priorities. It will be your task to work with your group to help achieve them!


==Mission==
==Mission==
The primary goals for this raid vary by which group you have been assigned. For the urban groups: Your primary goals are to bring our places up to regional standards and tackle any [[Places#Place_updates_.28moderation.29|place update requests]] you find. For the rural areas, your primary goals will be to match the basemap to the Plains region guidelines and assign segments proper speed limits. See the appropriate Wazopedias in the resources section of this page to see how PLN handles road segments, places, etc.
The primary goals for this raid vary by which group you have been assigned. For the rural areas, your primary goals will be to correct the basemap so that it meets the Plains regional guidelines, ensure correct segment naming including city naming, and assign segments proper speed limits. For the urban groups: Your primary goals are to bring our places up to regional standards, add missing information to incomplete places, and tackle any [[Places#Place_updates_.28moderation.29|place update requests]] you find. You can find the appropriate Wazopedias in the resources section of this page for more detailed state and regional editing guidelines.


<br />


===Priorities===
====Priorities & Goals====
These may vary additionally by the needs of individual raid group areas.
These may vary additionally by the needs of individual raid group areas.


Line 38: Line 29:


#Connectivity (basemap) - Rural areas especially
#Connectivity (basemap) - Rural areas especially
#Road Normalization (especially CR/CH segments)
#Road Name Normalization (especially CR/CH segments)
#Township Cleanup (removing "Greater XXX Area"'s)
#SLs
#SLs
#Complete PP to Region minimums
#Complete Places to Region minimums
#PLAs
#PLAs


Line 46: Line 38:


#PURs/MPs - Cities and tourist destinations
#PURs/MPs - Cities and tourist destinations
#Complete PP to Region minimums
#Complete Places to Region minimums
#SLs
#SLs
#PLAs
#PLAs
#Basemap
#Basemap
<br />
====Priority Breakdown====
While Minnesota is the "Land of 1,000 Lakes", it is also the "Land of 100,000 basemap segments". While the Twin Cities group will on the tens of thousands of places in the urbanized center of the state, the Rural Groups will focus on basemap. As you all know, basemap is it's own beast, and we're sorry for the rabbit hole you will enter. Minnesota has never had a MapRaid, so there are segments you may edit that have never been touched by an editor since the original import. This includes correcting segment directionality, naming, and city naming. Minnesota uses both County Road (CR) and County Highway (CH), but not interchangeably. You can reference the [[Minnesota|Minnesota Wiki]] for details on which one should be used and when. Also, many of these rural segments also have city names such as "Greater XXX Area" or "XXX Township". One of the goals we hope to accomplish with this raid is the removal of these types of city names and bring these segments back in line with state and regional guidelines. You can find more details here in this wiki under [[User:Tango259/Minnesota MapRaid 2020#City Names|City Names]].


==Hosts==
==Hosts==
Line 60: Line 57:
|{{Username|tinfoilhattie}}||Planning Committee||Minnesota SM
|{{Username|tinfoilhattie}}||Planning Committee||Minnesota SM
|-
|-
|{{Username|HBiede}}||Planning Committee||Plains LAM
|{{Username|karrows}}||Planning Committee||Minnesota SM
|-
|{{Username|HBiede}}||Planning Committee||Nebraska SM
|-
|-
|{{Username|nimper2000}}||Planning Committee||Kansas SM
|{{Username|nimper2000}}||Planning Committee||Kansas SM
Line 68: Line 67:
|{{Username|ehepner1977}}||Regional Support||Plains ARC
|{{Username|ehepner1977}}||Regional Support||Plains ARC
|-
|-
|{{Username|SunnyRaynbows}}||Consultant||Plains ARC
|{{Username|SunnyRaynbows}}||Regional Support||Plains ARC
|}
|}


Line 75: Line 74:


==Raid group areas==
==Raid group areas==
Interactive map: '''[https://drive.google.com/open?id=161pMPB06KtVAAEGrfpWsv0HYS7TkCZWZ&usp=sharing Raid groups on Google Maps]'''
Interactive map: '''[https://drive.google.com/open?id=161pMPB06KtVAAEGrfpWsv0HYS7TkCZWZ&usp=sharing Raid groups on Google Maps] (FIX WITH UPDATED MYMAP FOR MINNESOTA)'''
[[File:KSMO_MapRaid_areas.png|800px|thumbnail|center]]<br />
[[File:Raid Groups.png|alt=|center|thumb|568x568px]]
<br />


==Important / Mapraid guidelines==
==Important / Mapraid guidelines==
Please read the entire MapRaid wiki. If you are uncertain what to do about something you see on the map, please ask your group leader.
Please read the entire MapRaid wiki. For questions you may have that are not covered here, please refer to the [[Minnesota|Minnesota State Wiki]] for more detailed editing guidelines. If you are uncertain what to do about something you see on the map, please ask your group leader.


When you are editing in the raid area, please [[Waze_Map_Editor/Chat#Visible.2FInvisible|set yourself visible]] and enable the [[Map_Editor_Interface_and_Controls#Live_users|Live users]] layer.
When you are editing in the raid area, please [[Waze_Map_Editor/Chat#Visible.2FInvisible|set yourself visible]] and enable the [[Map_Editor_Interface_and_Controls#Live_users|Live users]] layer.


===Edit quality and mass editing===
===Edit Quality and Mass Editing===


You are responsible for every edit you make, whether you make it by hand or use a script. Every edit you make should meet the goals of this MapRaid and make a noticeable improvement to the map. Do not make edits simply to gain points without improving the map. If a segment is "good enough" for the Waze map, do not edit it. If it looks like you are making unnecessary edits or hunting for points, you may be banned from this MapRaid and from future MapRaids.
You are responsible for every edit you make, whether you make it by hand or use a script. Every edit you make should meet the goals of this MapRaid and make a noticeable improvement to the map. Do not make edits simply to gain points without improving the map. If a segment is "good enough" for the Waze map, do not edit it. If it looks like you are making unnecessary edits or hunting for points, you may be banned from this MapRaid and from future MapRaids.


===Editor restrictions===
===Editor Restrictions===
Map [[Editing_restrictions#Rank_table|editing restrictions]] that affect level 1 and 2 editors remain during the raid.
Map [[Editing_restrictions#Rank_table|editing restrictions]] that affect level 1 and 2 editors remain during the raid.


===Time zones===
===Time Zone===
For relevant WME interfaces that display in the editor's browser time zone, both Kansas and Missouri are in Central Daylight Time (UTC -5) for this raid '''with the exception of 4 counties in western Kansas'''. Groups 1 and 2 (Northwest Kansas and Southwest Kansas) should be aware that Sherman, Wallace, Greeley, and Hamilton counties are on Mountain Daylight Time.
For relevant WME interfaces that display in the editor's browser time zone, Minnesota is in Central Standard Time (UTC -6) for this raid.


===Road Types and Functional Classification (FC)===
===Road Types and Functional Classification (FC)===
Line 103: Line 103:
Many '''rural driveways''' are mapped in the Plains region.
Many '''rural driveways''' are mapped in the Plains region.


'''Rural''' driveways in Kansas and Missouri should frequently be mapped (as Parking Lot Roads), even if shorter than the general [[Driveways]] recommendation of 50 meters. Drivers will often be travelling at a high speed, and an upcoming turn provides advanced warning of their destination. Driveways also serve as useful navigation landmarks on otherwise featureless rural roads, especially during night time navigation. If they are not mapped, a Wazer driving on one may be mistakenly snapped to a nearby road and interfere with the speed data or provide confusing directions.
'''Rural''' driveways in Minnesota should frequently be mapped (as Parking Lot Roads), even if shorter than the general [[Driveways]] recommendation of 50 meters. Drivers will often be travelling at a high speed, and an upcoming turn provides advanced warning of their destination. Driveways also serve as useful navigation landmarks on otherwise featureless rural roads, especially during nighttime navigation. If they are not mapped, a Wazer driving on one may be mistakenly snapped to a nearby road and interfere with the speed data or provide confusing directions.


If the addresses for properties on the driveway are known, delete the relevant House Numbers and add Residential Place Points (RPPs).
If the addresses for properties on the driveway are known, delete the relevant House Numbers and add Residential Place Points (RPPs).


*The RPP must be complete including the address number, street name, city name, '''and entry/exit point''' as noted in the [[House_Numbers_in_WME#Things_to_remember_.28caveats.2Fwarnings.29|Things to remember]] section of the HN page under the ''If the correct stop point for a house/business is on a different road than its address road'' bullet point.
*If the addresses for properties on the driveway are known, delete the relevant House Numbers and add Residential Place Points (RPPs). Make sure the RPP is complete with address number, street name, city name, and entry/exit point as noted in the [[House Numbers in WME|House Numbers]] page.
*Ensure the entry/exit point is placed clearly to one side of the road segment, ''not'' on top of the road segment.
*Ensure the entry/exit point is placed clearly to one side of the road segment, ''not'' on top of the road segment.


'''Urban''' driveways do not qualify for mapping in most circumstances unless they meet certain route-aiding criteria as defined in the national standards for [[Driveways]].
 
Urban driveways '''do not qualify''' for mapping in most circumstances, unless they meet certain route-aiding criteria as defined in the national standards for [[Driveways]]. Adding unnecessary driveways in urban areas can cause the map to become cluttered.


===U-turns===
===U-turns===
'''Kansas''' - Allowed except where prohibited by sign.
U-turns are generally permitted except where prohibited by state, local municipal law, or signs. U-turns are specifically prohibited on hilltops or curves when the turning vehicle can’t be seen by other motorists from a minimum of 1,000 feet. They are also prohibited on freeways or when a motorist would cross over a double yellow line.
 
'''Missouri''' - U-turns are generally permitted except where prohibited by state, local municipal law, or signs. U-turns are specifically prohibited at intersections controlled by a traffic signal.


'''Implementation'''
'''Implementation -''' 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.
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.


The u-turn must also meet the following criteria:
The u-turn must also meet the following criteria:
Line 132: Line 130:
#Divided roads with explicitly-mapped inside turn lanes unless the turn arrow in the u-turn direction is disabled.
#Divided roads with explicitly-mapped inside turn lanes unless the turn arrow in the u-turn direction is disabled.


===Toll roads===
===Toll Roads & Express Lanes===
{{mbox|type=critical|text= Regardless of editor rank, do not alter any toll road segments without consulting your group leader who will escalate to raid leadership.}}
{{mbox|type=critical|text= Regardless of editor rank, <b>do not</b> alter any toll road or express lane segments without consulting your group leader who will escalate to state leadership.}}


===Cameras===
===Cameras===
'''Do not add any cameras.'''
As of May 2020, Minnesota 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.
 
'''Kansas''' - As of July 2019, KS does not have any enforcement cameras.
 
'''Missouri'''
 
*Only allowed at select intersections in Hannibal city limits.
*Otherwise do not approve nor add any others.
*Existing cameras in WME may be left to deter future reports.


===Update Requests (URs)===
===Update Requests (URs)===
Line 154: Line 144:
*Bring Parking Lot Areas to regional standards before closing the Map Problem.
*Bring Parking Lot Areas to regional standards before closing the Map Problem.


===Speed limits===
===Speed Limits===
'''Kansas''' ([https://www.ksrevisor.org/statutes/chapters/ch08/008_015_0058.html § 8-1558])


*In any urban district, 30 miles per hour;
*'''Statutory speed limits.''' The default Minnesota speed limits are set by state statute, and they can be modified by a local road authority under various circumstances. The statutory speed limits are:
*on any separated multilane highway, as designated and posted by the secretary of transportation, 75 miles per hour;
*#65mph or 70mph for interstates (depending on whether the road is, respectively, within or outside an urbanized area of at least 50,000)
*on any county or township highway, 55 miles per hour; and
*#65mph on divided highways with controlled access
*on all other highways, 65 miles per hour
*#25 miles per hour in residential roadways if adopted by the road authority having jurisdiction over the residential roadway
*Local jurisdictions may alter these not to exceed above maximums.
*#30mph in an “urban district,” which is any segment of a city street or town road with structures spaced less than 100 feet apart for a minimum distance of a quarter-mile
*All speed limits are enforced as posted.
*#35 miles per hour in a rural residential district if adopted by the road authority having jurisdiction over the rural residential district
*#10mph for alleys, mobile home parks, and campgrounds
*#55mph default on other roads.


'''Missouri''' ([http://revisor.mo.gov/main/OneSection.aspx?section=304.010 § 304.010])
(Source: Minn. Stat. §§ [https://www.revisor.mn.gov/statutes/cite/169.011 <u>169.011</u>]; [https://www.revisor.mn.gov/statutes/cite/169.14 <u>169.14</u>], subd. 2; [https://www.revisor.mn.gov/statutes/cite/327.27 <u>327.27</u>].)


*70 mph: rural freeways and interstates
===Locking Standards===
*65 mph: rural expressways
*60 mph: urban interstate highways, freeways, and expressways
*60 mph: other numbered, state-maintained rural highways
*55 mph: state lettered highways, or as posted
*20-30 mph: cities, towns, and villages, or as posted
*15-25 mph: school zones, as posted


===Segment Locks===
In Minnesota, we observe a minimum standard for locking roads based on segment type. Any road of a certain segment type must be locked '''at least''' to the rank listed in the chart below. Roads may be locked higher for protection and special situations (construction, confusing design, frequent mistakes, image inaccuracies, etc.), but should not be locked lower.
{{Locking Standard
    |lede=All of the Plains region observes the below lock standards.


When you edit any segment during the MapRaid, please set the lock level correctly. If you are unable to lock it to the correct level, then lock it to the level of your rank and request your group leader raise the lock to the standard.
{| class="wikitable" style="text-align:center; margin: 1em auto 1em auto; width: 40%"
|+Minnesota Minimum Locking Standards
!Segment Type!!Rank
|-
|HOT & Express Lanes||5
|-
|{{Freeway}}||4
|-
|{{Ramp}}||Highest rank of connected segments
|-
|HOV Bypass Ramps||4
|-
|{{Major Highway}}||3
|-
|{{Minor Highway}}||3
|-
|{{Primary Street}}||2
|-
|{{Railroad}}||2
|-
|All Others||1
|}


Roads may be locked higher for protection and special situations (areas with construction, tricky design, frequent mistakes, incorrect images, etc.).
Although common practice is to limit editing freeways to rank 5 or higher, we have determined that the experience required to reach editing rank 4 is sufficient to gain the privilege of editing freeway segments.
'''Do not decrease a rank just to decrease a rank, talk to your group leader before you do.'''
 
    |caption=Plains region segment locking standards
Note: Before locking these roads to these standards, you must verify that the [[Road names#Road_naming|name of the road]], [[Road_direction#Road_Direction|direction of the road]], and [[Turn_arrow#Turn_restrictions_.28allowed_turns.29|turn functionality]] is correct.  If this information is not correct, it should not be locked unless we are having issues with editors in the area.  The only exception here is Freeways due to the routing priority. Refer to [[Minnesota#Unlock_Requests|Unlock Requests]] if you need a section of road altered or unlocked to correct an issue.
    |title=Lock level
    |Fwy=4
    |Ramp=Highest rank of connected segments
    |MH=3
    |mH=3
    |PS=2
    |Street=1
    |note=All '''Toll Roads''' are to be locked at a minimum of 5.
}}


===Places===
===Common Places===
{| class="wikitable" border="1" style="margin: 1em auto 1em auto;"
{| class="wikitable" border="1" style="margin: 1em auto 1em auto;"
|+Place lock level and style standards
|+Place Lock Level and Style Standards
|-
|-
!Place type
!Place type
!Lock level
!Lock level
!Special instructions
!AP / PP
!Building / Fence Line
|-
|-
|Military installation / Airport||4||
|Military installation / Airport||5
|AP/PP||Fence LIne
|-
|-
|Hospitals / Urgent Care / Police &amp; Fire Dept||4||Map '''non-24/7 urgent care''' as a place point even if a standalone building
|Hospitals / Urgent Care / Police &amp; Fire Dept||4
|-
|Non-24hr care - PP
|National &amp; State Parks and Monuments||4||
All Others - AP
|Hospital, FD, PD - Fence Line
Urgent Care (strip mall) - Building
 
Urgent Care (stand alone) - Fance Line
|-
|-
|Gas Stations / Charging Stations||3||Map charging stations as place points
|National &amp; State Parks / Monuments||4
|Parks - AP
Monuments - PP
|Fence Line
|-
|-
|Schools / Universities / Colleges||3||
|Gas Stations / Charging Stations||3
|Gas Station - AP
Charging - PP
|Fence Line
|-
|-
|Government Buildings / Consulates||3||
|Schools / Universities / Colleges||3
|AP||Fence LIne
|-
|-
|City and Local Parks||3||
|Government Buildings / Consulates||3
|PP||
|-
|-
|Malls||3||Map to the '''building outline''' not the fence line||
|City & Local Parks||3
|AP||Fence Line
|-
|-
|'''All''' other places with ''complete'' information||3||
|All other places with ''complete'' information||3
|Regional Standard||Regional Standard
|}
|}


'''Hours of operation''': For locations with different hours of operation for service types (i.e. lobby vs. drive-thru) use the set with the longest duration for the place's open hours and write the other hours into the description.
'''Hours of operation''': For locations with different hours of operation for service types (i.e. lobby vs. drive-thru) use the set with the longest duration for the place's open hours and write the other hours into the description.


===City names===
===City Names===
This is clarification for city name guidance done during this MapRaid. If you have any other questions or concerns please involve your group leader. Please ensure that you have the Recommended Tools installed as these will help with identifying City/CDP and USPS zip codes.
This is clarification for city name guidance done during this MapRaid. If you have any other questions or concerns please involve your group leader. Please ensure that you have the Recommended Tools installed as these will help with identifying City/CDP and USPS zip codes.


Line 232: Line 243:
#If segment falls outside of a city/CDP but borders two USPS zip code cities, the primary city name should be left blank and the <code>None</code> checkbox selected. All segment names should be entered as alternates using both city names.
#If segment falls outside of a city/CDP but borders two USPS zip code cities, the primary city name should be left blank and the <code>None</code> checkbox selected. All segment names should be entered as alternates using both city names.


===Major issues to address after the MapRaid===
===Proper Naming for Rural Routes===
Any major issues that need to be addressed will be followed up on by local editors after the MapRaid's conclusion. Issues such as city name merging, large scale renaming (primary or alt), etc., will be handled later. Please notify your group leader of any large issues you find.
A number of rural counties in the state have adopted new or additional names for emergency response / 911 (sometimes called "e911") purposes. This may include the introduction of cardinal directions to County Road names - "CR-42 NE" vs "CR-42" for example. It may also include the addition of numbered (Ordinal) street names or other alternates for signed CR/CH.
 
In a majority of cases, this update has not been applied to actual signage, GIS, FC maps or any other official source. In order to maintain consistency on the map display as well as an accurate experience for drivers, please maintain the following naming standard for rural CR/CH outside city limits:
 
*Primary segment: "CR-42, [no city]"
*Alt: "CR-42 NE, Mailing City"
*Alt: "360th St NE, Mailing City"
*Segments should be set to PS or higher, per the notes above.
 
Inside city limits, feel free to use the primary common name as signed (e.g. 360th St NE). If you have questions or feel a need to make an exception, please consult your AM/ SM before making any major updates.
 
As noted in Cities & Towns above, ''do not use 'Twp', 'Township,' or 'Greater xxx Area''' in any city names or alternates.
 
===Major Issues===
If you encounter any major issues, please notify your group leader. Any major issues that need to be addressed will be followed up on by local editors after the MapRaid's conclusion. Issues such as city name merging, large scale renaming (primary or alt), etc., will be handled later.


==Resources==
==Resources==
===Local===
===Local===


*Functional Classifications - [[Kansas#Functional_Classifications|Kansas]], [[Missouri#Functional_Classifications|Missouruh]]
*[[Minnesota|Minnesota State Wiki]]
*State DOTs - [https://www.ksdot.org Kansas], [https://www.modot.org Missouri]
*[https://docs.google.com/spreadsheets/d/1Q-1ueAx4KWv_4YKqbjmEfmXPreGHnH8TYsCJT0EyIJE/edit?usp=sharing Minnesota County GIS Spreadsheet]
*Kansas Rural Speed Limits - [https://www.ksdot.org/Assets/wwwksdotorg/bureaus/burTransPlan/maps/GISMaps/Speed_2011.pdf PDF]
**''Due to some counties using Beacon or other GIS platforms, GIS-Layers may not be useful in your county. This is a consolidation of all county GIS sites in the State of Minnesota.''
*Kansas Wiki - [[Kansas]]
*[https://wazeopedia.waze.com/wiki/USA/index.php?title=Minnesota&mobileaction=toggle_view_desktop#Functional_Class Functional Classifications]
*Missouri Wiki - [[Missouri]]
*[https://wazeopedia.waze.com/wiki/USA/index.php?title=Minnesota&mobileaction=toggle_view_desktop#Quick_reference_chart FC Quick Reference Chart]
*[http://www.dot.state.mn.us/ MnDOT]
*[https://www.house.leg.state.mn.us/hrd/pubs/ss/ssspdlt.pdf Minnesota Speed Limits]
*''PLN Regional Wiki (pending creation)''


===Military===
===Military===
There are no major Army, Navy, Air Force, or Marine bases in the state. The only significant military facility in Minnesota is Camp Ripley, a 53,000-acre base for the National Guard located in Morrison County, in north-central Minnesota


*Ft. Leavenworth (Kansas East Group)
*'''Camp Ripley'''
**[https://home.army.mil/leavenworth/index.php/my-fort/all-services/gate-information Gate Information]
**[https://minnesotanationalguard.ng.mil/documents/2018/10/camp-ripley-military-installation-map.pdf/ Installation Map]
**[https://home.army.mil/leavenworth/index.php/download_file/view/528/392 Post Map]
*McConnell AFB (Wichita Metro Group)
**[https://www.mcconnellhousing.com/gates Gate Information] (Zoom in and click on green flags)
*Ft. Leonard Wood (Central Missouri Group)
**[https://home.army.mil/wood/index.php/about/Garrison/DES/physical-security/access-control Gate Info]
*Whiteman AFB (Kansas City Metro Group)
**[https://www.whitemanafbhousing.com/gates Gate Information] (Zoom in and click on green flags)
*Ft. Riley (Kansas City Metro Group)
**[https://home.army.mil/riley/index.php/about/visitor-info Gate Information]


===Tools and scripts===
===Tools and Scripts===
There are many scripts and extensions that editors use to assist with editing that not only make some jobs easier, but verifies what we do is correct.  The use of these scripts is highly encouraged and those listed below are the ones you should install, at a minimum, to get started.  
There are many scripts and extensions that editors use to assist with editing that not only make some jobs easier, but verifies what we do is correct.  The use of these scripts is highly encouraged and those listed below are the ones you should install, at a minimum, to get started.  


Line 273: Line 293:
You will need to install a browser extension to manage the additional scripts. Some scripts do not work with the current version of GreaseMonkey so we recommend [[Scripts#General_installation_instructions|installation of TamperMonkey]].
You will need to install a browser extension to manage the additional scripts. Some scripts do not work with the current version of GreaseMonkey so we recommend [[Scripts#General_installation_instructions|installation of TamperMonkey]].


'''KS-MO raid-specific scripts'''
'''Minnesota Raid-Specific Script'''


*[https://greasyfork.org/en/scripts/382221-ks-mo-wme-mapraid-regions KS-MO Raid Overlay]
*[https://greasyfork.org/en/scripts/382221-ks-mo-wme-mapraid-regions KS-MO Raid Overlay]


'''Essential scripts'''
'''Essential Scripts'''


*[https://www.waze.com/forum/viewtopic.php?f=819&t=249027 GIS Layers]
*[https://www.waze.com/forum/viewtopic.php?f=819&t=249027 GIS Layers]
Line 285: Line 305:
*[https://waze.xpto.org/magic/magic.bundle.user.js WME Magic] (especially for working on Basemap)
*[https://waze.xpto.org/magic/magic.bundle.user.js WME Magic] (especially for working on Basemap)


===General wiki links===
===General Wiki Links===


;[[Waze Map Editor/Welcome|New editor welcome page]]
;[[Waze Map Editor/Welcome|New editor welcome page]]

Latest revision as of 21:14, 27 May 2020

 Minnesota MapRaid ended on 25 Jul 2020 23:59:00 UTC. Please check back here for results and check the Mapraid Forum for mapraid announcements.


Welcome

The Minnesota MapRaid will be held 12 July 2020 at 19:00 UTC through 25 July 2020 23:59 UTC (approximately).

Welcome to the American Great Plains! Thank you for your assistance big and small in improving the map throughout Minnesota. A MapRaid is a gathering of editors from across the editing community to edit an area of the map in a burst of activity. While you as an editor will receive editing area for the entirety of both states for the raid duration (for administrative purposes), you will also receive a specific group assignment to focus on a subset of that area and a set of localized priorities. It will be your task to work with your group to help achieve them!

Mission

The primary goals for this raid vary by which group you have been assigned. For the rural areas, your primary goals will be to correct the basemap so that it meets the Plains regional guidelines, ensure correct segment naming including city naming, and assign segments proper speed limits. For the urban groups: Your primary goals are to bring our places up to regional standards, add missing information to incomplete places, and tackle any place update requests you find. You can find the appropriate Wazopedias in the resources section of this page for more detailed state and regional editing guidelines.


Priorities & Goals

These may vary additionally by the needs of individual raid group areas.

Rural Groups

  1. Connectivity (basemap) - Rural areas especially
  2. Road Name Normalization (especially CR/CH segments)
  3. Township Cleanup (removing "Greater XXX Area"'s)
  4. SLs
  5. Complete Places to Region minimums
  6. PLAs

Twin Cities Group

  1. PURs/MPs - Cities and tourist destinations
  2. Complete Places to Region minimums
  3. SLs
  4. PLAs
  5. Basemap


Priority Breakdown

While Minnesota is the "Land of 1,000 Lakes", it is also the "Land of 100,000 basemap segments". While the Twin Cities group will on the tens of thousands of places in the urbanized center of the state, the Rural Groups will focus on basemap. As you all know, basemap is it's own beast, and we're sorry for the rabbit hole you will enter. Minnesota has never had a MapRaid, so there are segments you may edit that have never been touched by an editor since the original import. This includes correcting segment directionality, naming, and city naming. Minnesota uses both County Road (CR) and County Highway (CH), but not interchangeably. You can reference the Minnesota Wiki for details on which one should be used and when. Also, many of these rural segments also have city names such as "Greater XXX Area" or "XXX Township". One of the goals we hope to accomplish with this raid is the removal of these types of city names and bring these segments back in line with state and regional guidelines. You can find more details here in this wiki under City Names.

Hosts

Username Raid Role Waze Roles
tango259 (PM [Help])   Planning Committee Minnesota SM
tinfoilhattie (PM [Help])   Planning Committee Minnesota SM
karrows (PM [Help])   Planning Committee Minnesota SM
HBiede (PM [Help])   Planning Committee Nebraska SM
nimper2000 (PM [Help])   Planning Committee Kansas SM
bretmcvey (PM [Help])   Regional Support Plains RC
ehepner1977 (PM [Help])   Regional Support Plains ARC
SunnyRaynbows (PM [Help])   Regional Support Plains ARC

Communication

All raid communications will be in special raid channels on the Waze Plains Editors Discord server.

Raid group areas

Interactive map: Raid groups on Google Maps (FIX WITH UPDATED MYMAP FOR MINNESOTA)


Important / Mapraid guidelines

Please read the entire MapRaid wiki. For questions you may have that are not covered here, please refer to the Minnesota State Wiki for more detailed editing guidelines. If you are uncertain what to do about something you see on the map, please ask your group leader.

When you are editing in the raid area, please set yourself visible and enable the Live users layer.

Edit Quality and Mass Editing

You are responsible for every edit you make, whether you make it by hand or use a script. Every edit you make should meet the goals of this MapRaid and make a noticeable improvement to the map. Do not make edits simply to gain points without improving the map. If a segment is "good enough" for the Waze map, do not edit it. If it looks like you are making unnecessary edits or hunting for points, you may be banned from this MapRaid and from future MapRaids.

Editor Restrictions

Map editing restrictions that affect level 1 and 2 editors remain during the raid.

Time Zone

For relevant WME interfaces that display in the editor's browser time zone, Minnesota is in Central Standard Time (UTC -6) for this raid.

Road Types and Functional Classification (FC)

Road type classification is not a focus of this map raid. It has been addressed for every county in Kansas and Missouri. If you see a problem on the segments you are editing, please consult with your group leader before fixing it.

Micro-doglegs

Replace any micro-doglegs (mDLs) with turn instruction overrides (TIOs), and be sure to delete the geometry nodes that were used to create the micro-dogleg. If you find an intersection where you believe preserving the micro-dogleg is preferred, please escalate to your raid group leader.

Driveways

Many rural driveways are mapped in the Plains region.

Rural driveways in Minnesota should frequently be mapped (as Parking Lot Roads), even if shorter than the general Driveways recommendation of 50 meters. Drivers will often be travelling at a high speed, and an upcoming turn provides advanced warning of their destination. Driveways also serve as useful navigation landmarks on otherwise featureless rural roads, especially during nighttime navigation. If they are not mapped, a Wazer driving on one may be mistakenly snapped to a nearby road and interfere with the speed data or provide confusing directions.

If the addresses for properties on the driveway are known, delete the relevant House Numbers and add Residential Place Points (RPPs).

  • If the addresses for properties on the driveway are known, delete the relevant House Numbers and add Residential Place Points (RPPs). Make sure the RPP is complete with address number, street name, city name, and entry/exit point as noted in the House Numbers page.
  • Ensure the entry/exit point is placed clearly to one side of the road segment, not on top of the road segment.


Urban driveways do not qualify for mapping in most circumstances, unless they meet certain route-aiding criteria as defined in the national standards for Driveways. Adding unnecessary driveways in urban areas can cause the map to become cluttered.

U-turns

U-turns are generally permitted except where prohibited by state, local municipal law, or signs. U-turns are specifically prohibited on hilltops or curves when the turning vehicle can’t be seen by other motorists from a minimum of 1,000 feet. They are also prohibited on freeways or when a motorist would cross over a double yellow line.

Implementation - 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.

The u-turn must also meet the following criteria:

  1. The u-turn is explicitly allowed by signage or is otherwise legal and safe.
  2. The turn can be completed in one continuous movement.
  3. There is at least 15 meters (49 feet) from the right edge of the legal departure lane to the right edge of the "destination" curb (49 foot turning circle).
  4. There is no sign prohibiting a u-turn.

Note that when editing, a functional u-turn can arise from more than just the u-turn flag on a road segment, such as with these common scenarios:

  1. Divided roads with box and partial-box intersections where the median segment is 15 m (49 feet) or longer.
  2. Divided roads with explicitly-mapped inside turn lanes unless the turn arrow in the u-turn direction is disabled.

Toll Roads & Express Lanes

 Regardless of editor rank, do not alter any toll road or express lane segments without consulting your group leader who will escalate to state leadership.

Cameras

As of May 2020, Minnesota 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.

Update Requests (URs)

Leave responding to URs to local editors. They are not in scope for this raid.

Map Problems (MPs)

  • Do not auto-create parking lots from Map Problem suggestions. Map them manually per guidelines.
  • Bring Parking Lot Areas to regional standards before closing the Map Problem.

Speed Limits

  • Statutory speed limits. The default Minnesota speed limits are set by state statute, and they can be modified by a local road authority under various circumstances. The statutory speed limits are:
    1. 65mph or 70mph for interstates (depending on whether the road is, respectively, within or outside an urbanized area of at least 50,000)
    2. 65mph on divided highways with controlled access
    3. 25 miles per hour in residential roadways if adopted by the road authority having jurisdiction over the residential roadway
    4. 30mph in an “urban district,” which is any segment of a city street or town road with structures spaced less than 100 feet apart for a minimum distance of a quarter-mile
    5. 35 miles per hour in a rural residential district if adopted by the road authority having jurisdiction over the rural residential district
    6. 10mph for alleys, mobile home parks, and campgrounds
    7. 55mph default on other roads.

(Source: Minn. Stat. §§ 169.011; 169.14, subd. 2; 327.27.)

Locking Standards

In Minnesota, we observe a minimum standard for locking roads based on segment type. Any road of a certain segment type must be locked at least to the rank listed in the chart below. Roads may be locked higher for protection and special situations (construction, confusing design, frequent mistakes, image inaccuracies, etc.), but should not be locked lower.

Minnesota Minimum Locking Standards
Segment Type Rank
HOT & Express Lanes 5
 Freeway  4
 Ramp  Highest rank of connected segments
HOV Bypass Ramps 4
 Major Highway  3
 Minor Highway  3
 Primary Street  2
 |-|-|-|-|-|-|-|-|-| Railroad |-|-|-|-|-|-|-|-|-|  2
All Others 1

Although common practice is to limit editing freeways to rank 5 or higher, we have determined that the experience required to reach editing rank 4 is sufficient to gain the privilege of editing freeway segments.

Note: Before locking these roads to these standards, you must verify that the name of the road, direction of the road, and turn functionality is correct. If this information is not correct, it should not be locked unless we are having issues with editors in the area. The only exception here is Freeways due to the routing priority. Refer to Unlock Requests if you need a section of road altered or unlocked to correct an issue.

Common Places

Place Lock Level and Style Standards
Place type Lock level AP / PP Building / Fence Line
Military installation / Airport 5 AP/PP Fence LIne
Hospitals / Urgent Care / Police & Fire Dept 4 Non-24hr care - PP

All Others - AP

Hospital, FD, PD - Fence Line

Urgent Care (strip mall) - Building

Urgent Care (stand alone) - Fance Line

National & State Parks / Monuments 4 Parks - AP

Monuments - PP

Fence Line
Gas Stations / Charging Stations 3 Gas Station - AP

Charging - PP

Fence Line
Schools / Universities / Colleges 3 AP Fence LIne
Government Buildings / Consulates 3 PP
City & Local Parks 3 AP Fence Line
All other places with complete information 3 Regional Standard Regional Standard

Hours of operation: For locations with different hours of operation for service types (i.e. lobby vs. drive-thru) use the set with the longest duration for the place's open hours and write the other hours into the description.

City Names

This is clarification for city name guidance done during this MapRaid. If you have any other questions or concerns please involve your group leader. Please ensure that you have the Recommended Tools installed as these will help with identifying City/CDP and USPS zip codes.

The city name for the primary name is either the Census Designated Place (CDP) name, incorporated city name, or None.

  1. If the segment falls within a city or CDP, the primary segment name should include that city or CDP, and all alternate segment names should also include the same city or CDP. As needed, USPS zip code cities may be added as alternate city names.
  2. If the segment falls outside of a city or CDP, then the primary city name should be left blank and the None checkbox selected. The primary segment name should be duplicated in the alternates and all alternate names should use the USPS zip code city name. Do not check "None" for any of the alternate city names
  3. If the segment runs along the border between two cities or CDPs, the USPS may be able to provide a tiebreaker (be sure to manually check any result suggested by the US Government Boundaries script). If there is no USPS tiebreaker one city should be arbitrarily selected as the primary city name and used consistently for all similar segments for that area. The primary segment name should be duplicated in the alternate names section using the second city name, and all alternate segment names should be entered using both city names.
  4. If segment falls outside of a city/CDP but borders two USPS zip code cities, the primary city name should be left blank and the None checkbox selected. All segment names should be entered as alternates using both city names.

Proper Naming for Rural Routes

A number of rural counties in the state have adopted new or additional names for emergency response / 911 (sometimes called "e911") purposes. This may include the introduction of cardinal directions to County Road names - "CR-42 NE" vs "CR-42" for example. It may also include the addition of numbered (Ordinal) street names or other alternates for signed CR/CH.

In a majority of cases, this update has not been applied to actual signage, GIS, FC maps or any other official source. In order to maintain consistency on the map display as well as an accurate experience for drivers, please maintain the following naming standard for rural CR/CH outside city limits:

  • Primary segment: "CR-42, [no city]"
  • Alt: "CR-42 NE, Mailing City"
  • Alt: "360th St NE, Mailing City"
  • Segments should be set to PS or higher, per the notes above.

Inside city limits, feel free to use the primary common name as signed (e.g. 360th St NE). If you have questions or feel a need to make an exception, please consult your AM/ SM before making any major updates.

As noted in Cities & Towns above, do not use 'Twp', 'Township,' or 'Greater xxx Area' in any city names or alternates.

Major Issues

If you encounter any major issues, please notify your group leader. Any major issues that need to be addressed will be followed up on by local editors after the MapRaid's conclusion. Issues such as city name merging, large scale renaming (primary or alt), etc., will be handled later.

Resources

Local

Military

There are no major Army, Navy, Air Force, or Marine bases in the state. The only significant military facility in Minnesota is Camp Ripley, a 53,000-acre base for the National Guard located in Morrison County, in north-central Minnesota

Tools and Scripts

There are many scripts and extensions that editors use to assist with editing that not only make some jobs easier, but verifies what we do is correct. The use of these scripts is highly encouraged and those listed below are the ones you should install, at a minimum, to get started.

Toolbox

Once you have installed Toolbox, press the Toolbox Icon and select a minimum of the following options:

TamperMonkey

You will need to install a browser extension to manage the additional scripts. Some scripts do not work with the current version of GreaseMonkey so we recommend installation of TamperMonkey.

Minnesota Raid-Specific Script

Essential Scripts

General Wiki Links

New editor welcome page
Waze Map Editor
Best Map Editing Practice
Editing manual
Common editing mistakes
How to make a Permalink; YouTube
All about using the WME Chat
Community Plugins, Extensions and Tools

Raid Groups

Group 1 - Northwest Kansas
Group leader: ldriveskier (PM [Help])  
Assistant group leader: ramblinwreck_81 (PM [Help])  
Username (rank) Group Badges
ldriveskier(5) [PM [Help]]  Group 1
Northwest Kansas
ramblinwreck_81(5) [PM [Help]]  Group 1
Northwest Kansas
hiroaki27609(5) [PM [Help]]  Group 1
Northwest Kansas
juliansean(5) [PM [Help]]  Group 1
Northwest Kansas
dhschneider(5) [PM [Help]]  Group 1
Northwest Kansas
westjacksonfd(5) [PM [Help]]  Group 1
Northwest Kansas
wakirkpatrick(3) [PM [Help]]  Group 1
Northwest Kansas
daveacincy(3) [PM [Help]]  Group 1
Northwest Kansas
davis_312(3) [PM [Help]]  Group 1
Northwest Kansas
snowboardjoe(3) [PM [Help]]  Group 1
Northwest Kansas
dodgingcones(3) [PM [Help]]  Group 1
Northwest Kansas
darkchicken(2) [PM [Help]]  Group 1
Northwest Kansas
wayzlu(2) [PM [Help]]  Group 1
Northwest Kansas
hammy211(1) [PM [Help]]  Group 1
Northwest Kansas


Group 2 - Southwest Kansas
Group leader: SkiDooGuy (PM [Help])  
Assistant group leader: Johnsninja58 (PM [Help])  
Username (rank) Group Badges
SkiDooGuy(6) [PM [Help]]  Group 2
Southwest Kansas
Johnsninja58(5) [PM [Help]]  Group 2
Southwest Kansas
FastestBeef(5) [PM [Help]]  Group 2
Southwest Kansas
jm6087(6) [PM [Help]]  Group 2
Southwest Kansas
kjg53(5) [PM [Help]]  Group 2
Southwest Kansas
HBiede(4) [PM [Help]]  Group 2
Southwest Kansas
YourEvilTwinFTW(4) [PM [Help]]  Group 2
Southwest Kansas
AnorestesX(3) [PM [Help]]  Group 2
Southwest Kansas
tckma(3) [PM [Help]]  Group 2
Southwest Kansas
Mvan231(3) [PM [Help]]  Group 2
Southwest Kansas
RoadStache(3) [PM [Help]]  Group 2
Southwest Kansas
GT3Mike(2) [PM [Help]]  Group 2
Southwest Kansas
lilmamachris33(2) [PM [Help]]  Group 2
Southwest Kansas
mjraneri(1) [PM [Help]]  Group 2
Southwest Kansas


Group 3 - East Kansas
Group leader: Chronos74 (PM [Help])  
Assistant group leader: Dude495 (PM [Help])  
Username (rank) Group Badges
Dude495(5) [PM [Help]]  Group 3
East Kansas
Chronos74(3) [PM [Help]]  Group 3
East Kansas
bretmcvey(6) [PM [Help]]  Group 3
East Kansas
Huybee3(5) [PM [Help]]  Group 3
East Kansas
cotero2002(5) [PM [Help]]  Group 3
East Kansas
steveinark(5) [PM [Help]]  Group 3
East Kansas
G_W1Z(4) [PM [Help]]  Group 3
East Kansas
SNYOWL(4) [PM [Help]]  Group 3
East Kansas
DrHenryJonesSr(3) [PM [Help]]  Group 3
East Kansas
mdswbkq(3) [PM [Help]]  Group 3
East Kansas
TFD425(3) [PM [Help]]  Group 3
East Kansas
Mikepedia(2) [PM [Help]]  Group 3
East Kansas
SopranoMimi(1) [PM [Help]]  Group 3
East Kansas
thezz33(1) [PM [Help]]  Group 3
East Kansas
mustberice(1) [PM [Help]]  Group 3
East Kansas


Group 4 - Wichita Metro
Group leader: dfw_gis (PM [Help])  
Assistant group leader: MFCoolCool (PM [Help])  
Username (rank) Group Badges
dfw_gis(5) [PM [Help]]  Group 4
Wichita Metro
MFCoolCool(3) [PM [Help]]  Group 4
Wichita Metro
willdanneriv(5) [PM [Help]]  Group 4
Wichita Metro
sikemever(5) [PM [Help]]  Group 4
Wichita Metro
mhh60(4) [PM [Help]]  Group 4
Wichita Metro
dchary2418(4) [PM [Help]]  Group 4
Wichita Metro
RichardPyne(4) [PM [Help]]  Group 4
Wichita Metro
tigger13090(3) [PM [Help]]  Group 4
Wichita Metro
Mstrbooth(3) [PM [Help]]  Group 4
Wichita Metro
RoadWarriorTech850(3) [PM [Help]]  Group 4
Wichita Metro
Snow_Skier(2) [PM [Help]]  Group 4
Wichita Metro
derrydrivin(2) [PM [Help]]  Group 4
Wichita Metro
mchueby(2) [PM [Help]]  Group 4
Wichita Metro
NathanHirschWard(2) [PM [Help]]  Group 4
Wichita Metro


Group 5 - Northwest Missouri
Group leader: Machete808 (PM [Help])  
Assistant group leader: ct13 (PM [Help])  
Username (rank) Group Badges
Machete808(5) [PM [Help]]  Group 5
Northwest Missouri
ct13(6) [PM [Help]]  Group 5
Northwest Missouri
herrchin(5) [PM [Help]]  Group 5
Northwest Missouri
toolmanzwief(5) [PM [Help]]  Group 5
Northwest Missouri
ohiostmusicman(5) [PM [Help]]  Group 5
Northwest Missouri
AugieAStL(4) [PM [Help]]  Group 5
Northwest Missouri
tortured1(3) [PM [Help]]  Group 5
Northwest Missouri
jcipc2004(3) [PM [Help]]  Group 5
Northwest Missouri
Texasthered(3) [PM [Help]]  Group 5
Northwest Missouri
Fender_Bender42(3) [PM [Help]]  Group 5
Northwest Missouri
Drivingwithbill(2) [PM [Help]]  Group 5
Northwest Missouri
SCScouter316(2) [PM [Help]]  Group 5
Northwest Missouri
goddard244(2) [PM [Help]]  Group 5
Northwest Missouri
FreedAce(2) [PM [Help]]  Group 5
Northwest Missouri


Group 6 - Northeast Missouri
Group leader: ojlaw (PM [Help])  
Assistant group leader: dangottschalk (PM [Help])  
Username (rank) Group Badges
ojlaw(5) [PM [Help]]  Group 6
Northeast Missouri
dangottschalk(4) [PM [Help]]  Group 6
Northeast Missouri
dspille(5) [PM [Help]]  Group 6
Northeast Missouri
jaywazin(5) [PM [Help]]  Group 6
Northeast Missouri
jimbobaggins1966(5) [PM [Help]]  Group 6
Northeast Missouri
Luke6270(5) [PM [Help]]  Group 6
Northeast Missouri
buckeyemondo(4) [PM [Help]]  Group 6
Northeast Missouri
jimbobninja06(3) [PM [Help]]  Group 6
Northeast Missouri
NightReaper86(3) [PM [Help]]  Group 6
Northeast Missouri
TowerFire36(3) [PM [Help]]  Group 6
Northeast Missouri
QuebecRefugee(3) [PM [Help]]  Group 6
Northeast Missouri
Commissar0617(2) [PM [Help]]  Group 6
Northeast Missouri
fourLoop(2) [PM [Help]]  Group 6
Northeast Missouri
steviejaydriver(2) [PM [Help]]  Group 6
Northeast Missouri
Kurzov(2) [PM [Help]]  Group 6
Northeast Missouri


Group 7 - Kansas City Metro
Group leader: steelpanz (PM [Help])  
Assistant group leader: n4dog (PM [Help])  
Username (rank) Group Badges
steelpanz(5) [PM [Help]]  Group 7
KC Metro
n4dog(5) [PM [Help]]  Group 7
KC Metro
ehepner1977(6) [PM [Help]]  Group 7
KC Metro
Kartografer(5) [PM [Help]]  Group 7
KC Metro
Sdtahoe(5) [PM [Help]]  Group 7
KC Metro
Larryhayes7(4) [PM [Help]]  Group 7
KC Metro
DaveKS14(4) [PM [Help]]  Group 7
KC Metro
Airchair(4) [PM [Help]]  Group 7
KC Metro
Be8el0ve(4) [PM [Help]]  Group 7
KC Metro
bobc455(4) [PM [Help]]  Group 7
KC Metro
Awensome(2) [PM [Help]]  Group 7
KC Metro
KingCoast(2) [PM [Help]]  Group 7
KC Metro
fireguy52(2) [PM [Help]]  Group 7
KC Metro
varso(1) [PM [Help]]  Group 7
KC Metro


Group 8 - Central Missouri
Group leader: Falco_sparverius (PM [Help])  
Assistant group leader: Mythdraug (PM [Help])  
Username (rank) Group Badges
Falco_sparverius(5) [PM [Help]]  Group 8
Central Missouri
Mythdraug(3) [PM [Help]]  Group 8
Central Missouri
j-d-(5) [PM [Help]]  Group 8
Central Missouri
jwe252(5) [PM [Help]]  Group 8
Central Missouri
turnertr(5) [PM [Help]]  Group 8
Central Missouri
apeachypanda(4) [PM [Help]]  Group 8
Central Missouri
kndcajun(4) [PM [Help]]  Group 8
Central Missouri
SunDevil2213(3) [PM [Help]]  Group 8
Central Missouri
idontkerr(3) [PM [Help]]  Group 8
Central Missouri
Matt-L-75067(3) [PM [Help]]  Group 8
Central Missouri
Passingbyu(3) [PM [Help]]  Group 8
Central Missouri
s2k2vidguy(3) [PM [Help]]  Group 8
Central Missouri
ArnoldN51(2) [PM [Help]]  Group 8
Central Missouri
MsCookie695(1) [PM [Help]]  Group 8
Central Missouri


Group 9 - St. Louis Metro
Group leader: Joerodriguez12 (PM [Help])  
Assistant group leader: Umarth735 (PM [Help])  
Username (rank) Group Badges
Joerodriguez12(5) [PM [Help]]  Group 9
St. Louis Metro
Umarth735(3) [PM [Help]]  Group 9
St. Louis Metro
Rainman3699(5) [PM [Help]]  Group 9
St. Louis Metro
Doctorblah(5) [PM [Help]]  Group 9
St. Louis Metro
Benenmen(5) [PM [Help]]  Group 9
St. Louis Metro
uscwaller(5) [PM [Help]]  Group 9
St. Louis Metro
krzycholub(4) [PM [Help]]  Group 9
St. Louis Metro
pcbman(3) [PM [Help]]  Group 9
St. Louis Metro
phuz(3) [PM [Help]]  Group 9
St. Louis Metro
ControlNode(2) [PM [Help]]  Group 9
St. Louis Metro
Corydon76(2) [PM [Help]]  Group 9
St. Louis Metro
subtlename(2) [PM [Help]]  Group 9
St. Louis Metro
fweewayze94(2) [PM [Help]]  Group 9
St. Louis Metro


Group 10 - Southwest Missouri
Group leader: SanzClew (PM [Help])  
Assistant group leader: TLknows (PM [Help])  
Username (rank) Group Badges
SanzClew(5) [PM [Help]]  Group 10
Southwest Missouri
TLknows(3) [PM [Help]]  Group 10
Southwest Missouri
whathappened15(5) [PM [Help]]  Group 10
Southwest Missouri
Rfrsw101(5) [PM [Help]]  Group 10
Southwest Missouri
bz2012(5) [PM [Help]]  Group 10
Southwest Missouri
GeekDriverPeaceful(4) [PM [Help]]  Group 10
Southwest Missouri
chucksways(4) [PM [Help]]  Group 10
Southwest Missouri
coontex(3) [PM [Help]]  Group 10
Southwest Missouri
FTWMikeC(3) [PM [Help]]  Group 10
Southwest Missouri
FurryDaddy(3) [PM [Help]]  Group 10
Southwest Missouri
SGTBilkoBR(3) [PM [Help]]  Group 10
Southwest Missouri
W1QA(3) [PM [Help]]  Group 10
Southwest Missouri
TheLocalCaffeineDealer(1) [PM [Help]]  Group 10
Southwest Missouri
Strobn(1) [PM [Help]]  Group 10
Southwest Missouri


Group 11 - Springfield/Branson Metros
Group leader: megg2004 (PM [Help])  
Assistant group leader: sketch (PM [Help])  
Username (rank) Group Badges
megg2004(4) [PM [Help]]  Group 11
Springfield/Branson Metros
sketch(6) [PM [Help]]  Group 11
Springfield/Branson Metros
red-nax(5) [PM [Help]]  Group 11
Springfield/Branson Metros
enfcer74(5) [PM [Help]]  Group 11
Springfield/Branson Metros
LennyNRPD(5) [PM [Help]]  Group 11
Springfield/Branson Metros
Moogonk(5) [PM [Help]]  Group 11
Springfield/Branson Metros
EmilGz(4) [PM [Help]]  Group 11
Springfield/Branson Metros
Bassdan7403(4) [PM [Help]]  Group 11
Springfield/Branson Metros
todaresq(3) [PM [Help]]  Group 11
Springfield/Branson Metros
CaptBlackie(3) [PM [Help]]  Group 11
Springfield/Branson Metros
bwawsc(3) [PM [Help]]  Group 11
Springfield/Branson Metros
orangegator23(2) [PM [Help]]  Group 11
Springfield/Branson Metros
Squint588(2) [PM [Help]]  Group 11
Springfield/Branson Metros


Group 12 - Southeast Missouri
Group leader: Happy_Lyn (PM [Help])  
Assistant group leader: DCLemur (PM [Help])  
Username (rank) Group Badges
Happy_Lyn(4) [PM [Help]]  Group 12
Southeast Missouri
DCLemur(5) [PM [Help]]  Group 12
Southeast Missouri
russblau(5) [PM [Help]]  Group 12
Southeast Missouri
jushag(4) [PM [Help]]  Group 12
Southeast Missouri
jalondon628(4) [PM [Help]]  Group 12
Southeast Missouri
cparishjr(4) [PM [Help]]  Group 12
Southeast Missouri
EHcool68(4) [PM [Help]]  Group 12
Southeast Missouri
bummerdude69(4) [PM [Help]]  Group 12
Southeast Missouri
madcatvt(4) [PM [Help]]  Group 12
Southeast Missouri
TheRealOrdizzle(3) [PM [Help]]  Group 12
Southeast Missouri
taminas(3) [PM [Help]]  Group 12
Southeast Missouri
MatthewStarbuck(3) [PM [Help]]  Group 12
Southeast Missouri
yepperoni(3) [PM [Help]]  Group 12
Southeast Missouri
Taleen3mm(2) [PM [Help]]  Group 12
Southeast Missouri


Area 51 - Military Advisors
Username (rank) Group Badges
TheChrisK(6) [PM [Help]]  Group 51
Michelle-s(5) [PM [Help]]  Group 51

Acknowledgements

Hall of Fame

Group Photo

Retrieved from "https://beta.waze.com/wiki/Mauritius/index.php?title=User:Tango259/Minnesota_MapRaid_2020&oldid=172631"