Minnesota MapRaid ended on 24 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
Connectivity (basemap) - Rural areas especially
Road Normalization (especially CR/CH segments)
Township Cleanup (removing "Greater XXX Area"'s)
SLs
Complete Places to Region minimums
PLAs
Twin Cities Group
PURs/MPs - Cities and tourist destinations
Complete Places to Region minimums
SLs
PLAs
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.
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.
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:
The u-turn is explicitly allowed by signage or is otherwise legal and safe.
The turn can be completed in one continuous movement.
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).
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:
Divided roads with box and partial-box intersections where the median segment is 15 m (49 feet) or longer.
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:
65mph or 70mph for interstates (depending on whether the road is, respectively, within or outside an urbanized area of at least 50,000)
65mph on divided highways with controlled access
25 miles per hour in residential roadways if adopted by the road authority having jurisdiction over the residential roadway
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
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
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 Ranks
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.
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.Error creating thumbnail: Unable to save thumbnail to destination
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 namesError creating thumbnail: Unable to save thumbnail to destination
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.
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 to address after the MapRaid
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.
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.
There is no major Army, Navy, Air Force, or Marine base 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
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.
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.
