 |
North Carolina Speed Limit Mapraid 2016 ended on 12 Jun 2016 21:00:00 UTC. Please check back here for results and check the Mapraid Forum for mapraid announcements. |
The North Carolina Speed Limit Mapraid will be 3 June through 12 June 2016. The participants will be divided into several groups, one for each section of the map. Each group will have both local and senior editors, one of which will be the "Group leader" - listed in blue below. Please direct all questions to your group leaders. The raid hosts will be available across all areas for added support.
Goal
Our goal is adding correct speed limits on segments in North Carolina, with emphasis on Major Highways, Minor Highways and Primary Streets.
- If there is a large area with speed limits already added that are incorrect, please bring it to your group leader's attention.
Please also make basic common-sense edits as you work on the mapraid goals -- fix bad turns and other obviously wrong information on the segments you are editing, but keep focused on the mapraid goals. If you see bigger problems that can be addressed later, contact your group leader or 
record it in this form.
Hosts
Communication
When you are editing in the raid area, please set yourself visible and enable the Live Users layer. We will use Slack Channels If you are not already part of the WazeUSA slack team, please look for your invitation to slack after mapraid registrations are processed. If you have trouble getting into the slack team or your group channel, please reach out to one of the MapRaid organizers.
You can also use WME chat. The WME Chat addon is recommended.
Groups
Important / Mapraid guidelines
Please read the entire MapRaid wiki. If you are still uncertain what to do about something you see on the map, please ask your group leader Thank You for your help with the map.
Speed Limit Guidelines
Use Waze Street View to find Speed Limit Signs. You may also get information from local drivers. You may use information from local ordinances posted on township, borough, or city websites. Do not rely on predicted speeds (with "verified" check box).
Please set your WME preferences to imperial and enter speed limits in miles per hour.
Some segments have unverified speed limits. These speed limits were predicted by waze. We must check each unverified speed limit. If it is correct, we can use the "Verified" check box. If it is not correct, we must replace the speed limit value.
North Carolina follows the US guideline for speed limits, with a few exceptions listed below.
North Carolina guidelines
Without Speed Limit
With Speed Limit
- If there is no SV, do not map SL.
- Do not guess. If there is no SV and there is no information from local drivers, we cannot know if there are signs. The only exclusion is if you have information from someone who has recently driven on the street or from local ordinances listing speed limits.
- If you do not know the speed limit for a segment leave it blank. It is safer to not set a speed limit then to get it wrong.
- When a speed limit changes at an intersection, the sign for the new speed zone might be up to 200 feet after the intersection. If the speed limit changes more than 200 feet from the intersection, then add a junction at the sign and make the speed limit change there.
- If you find a sign saying Reduced Speed Ahead = XX. Then usually about 1000 feet down the road you will find the New Speed limit sign, add a junction at the sign and make the speed limit change there.
- Speed limits for School Zones should be set as the non-school hours speed limit of the road.
Summary of National Guidelines
Yes
No
- Only map speeds found on regulatory white rectangular signs with black lettering.
- Do not map advisory speed limits (generally an orange or amber rectangular sign with black lettering).
- Where there are variable speed limits, map only the speed limit which is in effect most of the time during daylight hours (most hours of the day, days of the week).
- Do not map special speed limits for special vehicles. Waze only supports speed limits for private passenger cars.
- Do not map speed limits on any roads labeled as a Ferry.
- Where the speed limit changes, make it change in the map. A new junction may need to be added, but do not add a new junction for a speed limit if it will be within 200 feet of an existing junction.
Road Segment Lock Guidelines
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.
Any road of a certain segment type must be locked at least to the rank (level) in the chart below. Roads may be locked higher for protection and special situations (areas with construction, tricky design, frequent mistakes, incorrect images, etc.).
| Segment Type | Statewide |
|---|---|
| Freeway | 5 |
| Ramp | Highest rank of connected segments |
| Major Highway | 4 |
| Minor Highway | 3 |
| Primary Street | 2 |
| Street | 1 (Auto) |
| Private Road | 1 (Auto) |
| • • • • Ferry • • • • | 5 |
| |-|-|-|-|-|-|-|-|-| Railroad |-|-|-|-|-|-|-|-|-| | 2 |
Base Map Areas
There are still many areas in North Carolina which have not been touched by editors since the "base map" was imported in 2009. Only touch these areas if it is necessary to reach the objectives of this mapraid. If no information is available for setting Speed Limits, do not fix these parts of the map. These areas will be addressed at a later time.
- Before setting speed limits on a segment, set the road direction correctly and correct all turns and other obviously incorrect information.
- Please use the County GIS Map for correct road information. The can be found on the NC wiki page.
- If roads are very bad and very difficult to fix, you may report the problem to your group leader.
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. In addition, Waze will throttle your edits and points if you use scripts excessively.
Update Requests (URs)
Some editors have made URs about speed limits they have seen on the road. These all contain the string "mph". If you can find these URs, you can use them to help you set the correct speed limit on that segment.
Other types of URs are not a focus of this mapraid. If you spot a big problem which should be addressed, please let a group leader know.
Road Types, Names, and Functional Classification (FC)
Road type classification is not a focus of this map raid. It has been addressed in many areas of North Carolina. If you see an easily-fixable problem on the segments you are editing for speed limit and elevation, please fix it. If you find a large problem with road type, let a group leader know.
Road Names are not a focus of this map raid. If you see an easily-fixable problem on the segments you are already editing, please fix it. If you see any large problems with road naming, please let a group leader know.
Places
Places are not a focus of this mapraid. If you see obviously incorrect places that will cause incorrect routing, please feel free to fix it. Otherwise, please feel free to ignore places.
Issues to Address after the MapRaid
Any major issues that need to be address will be followed up by local editors after the MapRaid conclusion. Issues such as city name merging, large scale naming (primary or alt), etc, will be handled after the fact. Remember, the concentration is speed limits and lock levels.
Any issues that require future follow up should be entered on this form.
Mapping Resources
Only use Street View and Satellite view from within waze, websites from businesses, and the sources listed below. Do not use Google Maps. Do not use Google Maps Street View. Do not use any other online mapping resources.
Warning: If you copy information from unauthorized sources, you may be removed from this mapraid. Also, every segment or place you edited might be removed from the map. Copying information from copyrighted sources is illegal!
NC Mapping Resources
- NCDOT Speed Limit Map It is not 100% accurate where speed limit is changing. It can help you find speed limit zones. Please confirm using WME Street View.
Tools for this mapraid
Basic References
- 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
- WME Reference Sheet[PDF]
- a printable double-sided tri-fold quick reference guide to some of the common topics used in WME.
- Community Plugins, Extensions and Tools
- links and descriptions to most of the editing scripts being used. Some of these are essential to good editing, and others make the editing process much easier. WME Validator, URO+, and WME Toolbox are highly recommended.
- How to Install a Chrome Extension (YouTube)
Basic Scripts and Extensions
- WME Color Highlights
- Install Chrome Extension or tampermonkey / greasemonkey script
- Check the option for "No Speed Limit" and Uncheck the other highlight options.
- Segments with no speed limit or unverified speed limit will be highlighted orange.
- Speed Limit Helper
- Makes it easier to add the correct speed limits.
- tampermonkey/greasemonkey required
- WME Speeds
- Adds colours to road segments to show their speeds.
- tampermonkey/greasemonkey required
- WME Street View Availability
- WME userscript that shows where you can expect to find Street View imagery. The information provided is quite basic, but this is all that is readily available to show.
- tampermonkey/greasemonkey required
- WME Chat Addon
- a script that improves the WME chat interface. For a list of all the features check the thread here -- Tampermonkey/Greasemonkey required
Advanced Scripts and Extensions
- WME Context Menu
- Right-click pop-up menu that works with speed limit helper.
- requires tampermonkey / greasemonkey. Works best alongside Speed Limit Helper.
- Read more at WME Context Menu
URO+ settings to find speed limit URs - Search for mph URs using URO+
- In the "misc" tab, scroll down to custom markers, choose the last one, and type "mph" in the text box.
- Speed Limit URs and elevation URs are the only ones we should be working with during this mapraid.
- WME Toolbox
- Now with a speed limit highlight option.
- This script has lots of ways to help remove unnecessary nodes, cut segments, locate "Soft Nodes", or nodes with undefined directions.
- Validator
- highlights issues on the map and can generate a very detailed report with U.S. wiki references and possible solutions.
- For Chrome Browser
- GreasyFork.org For Firefox -- Tampermonkey/Greasemonkey required
Mapraid edit lists
Spreadsheets and forms are being used to streamline management of various group efforts and track important edits. Below you can find links to use these these forms, sheets, and see the lists.
Results
 |
Check back here after the raid is completed to see the results and achievements |
MapRaid Promotions
Some editors really let their bright side out, and let their community skills shine. This is even more evident in a concerted group effort with high-density editing like a MapRaid!. Editors of all ranks working closely with each other and the Champs, really lets us everyone get to know each other, and allows certain editors to be recognized for their skills and effort.
When the Champs see someone consistently editing well, interacting well with the community, and knowledgeable of the various details from the Wiki, they can issue promotions. This can be anything from the size of a managed area, to a rank increase, or even a new role.
|
Watch here for results of promotions during and after the raid. |