The KS-MO MapRaid will be 09 August 2019 at 00:00 UTC through 23 August 2019 23:59 UTC.
Welcome to the American Great Plains! Thank you for your assistance big and small in improving the map throughout Kansas and Missouri. 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 urban groups: Your primary goals are to bring our places up to regional standards and tackle any place update requests you find. For the rural groups: Your primary goals are to match the basemap to the Kansas and Missouri state guidelines and assign segments proper speed limits.
Priorities
These may vary additionally by the needs of individual raid group areas.
Metro (KS - Wichita; MO - Kansas City; MO - Springfield/Branson; MO - St. Louis)
Place Update Requests and Map Problems - Cities and tourist destinations
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 zones
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.
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 Kansas and Missouri should frequently be mapped (as Private 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.
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 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.
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.
U-turns
Kansas - Allowed except where prohibited by sign.
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
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
Regardless of editor rank, do not alter any toll road segments without consulting your group leader who will escalate to raid leadership.
Cameras
Do not add any cameras.
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)
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.
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
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.
Roads may be locked higher for protection and special situations (areas with construction, tricky design, frequent mistakes, incorrect images, etc.).
Do not decrease a rank just to decrease a rank, talk to your group leader before you do.
Plains region segment locking standards
Segment Type
Lock level
Freeway
4
Ramp
Highest rank of connected segments
Major Highway
3
Minor Highway
3
Primary Street
2
Street
1
• • • • Ferry • • • •
5
|-|-|-|-|-|-|-|-|-| Railroad |-|-|-|-|-|-|-|-|-|
2
Note: All Toll Roads are to be locked at a minimum of 5.
Places
Place lock level and style standards
Place type
Lock level
Special instructions
Military installation / Airport
4
Hospitals / Urgent Care / Police & Fire Dept
4
Map non-24/7 urgent care as a place point even if a standalone building
National & State Parks and Monuments
4
Gas Stations / Charging Stations
3
Map charging stations as place points
Schools / Universities / Colleges
3
Government Buildings / Consulates
3
City and Local Parks
3
Malls
3
Map to the building outline not the fence line
All other places with complete information
3
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.
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.
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.
