Pennsylvania Speed Limit Mapraid 2016 ended on 14 Mar 2016 00:00:00 UTC. Please check back here for results and check the Mapraid Forum for mapraid announcements.
The Pennsylvania Speed Limit Mapraid
will be 29 Feb through 14 March 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.
Goals
Our goals are:
Put correct speed limits on segments in Pennsylvania, with emphasis on the connecting roads
Use realistic elevations where roads cross (so-called seagull edits).
Adjust segment locks, as appropriate, to meet the new Northeast locking standards.
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 WazeMapRaid 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
Right-click your group area to open WME
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
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.
Pennsylvania follows the US guideline for speed limits, with a few exceptions listed below.
Pennsylvania guidelines
When a speed limit changes at an intersection, the sign for the new speed zone can be found up to 200 feet after the intersection. If the speed limit changes more than 200' from the intersection, add a junction at the sign and make the speed limit change there.
Long term work zone speed limits may be mapped instead of the "ordinary time" speed limits.
Speed limit signs are supposed to be posted on every street, no further than 1/2 mile apart. If there are no posted signs, follow the PA guidelines:
35 miles per hour in any urban district.
25 miles per hour in a residence district (unless it is a numbered route classified as a local highway)
55 miles per hour in other locations.
Summary of National Guidelines
Regulatory Yes Advisory 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.
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.
Elevations should be mapped more-or-less realistically. Elevation numbers are relative. An overpass has a higher elevation than the road it passes over.
If a seagull can fly right under it, it’s a bridge (level greater than 0).
A road is only level = +2 if there’s another bridge (+1) running underneath it.
If it is underground and covered over, check the tunnel checkbox. The road segment must begin at least 50 feet before GPS signal is lost, and continue at least 50 feet after GPS signal is recovered.
If you see tunnels with negative (-1) elevations, leave them. If you create a new tunnel, set the lowest level to ground and set all crossing roads above that.
For every other case the road is ground level (level = Ground), even if it’s artificially elevated or dug under street level.
Tight MarkingTight Marking. We mark bridges with level = +1. In some cases we will need to split segments into two or more segments to mark only the right parts of the road as a bridge or a tunnel. This is Tight Marking.
At interchanges, where there is already a nearby junction, it will often not be necessary to use "tight" marking for an elevation change on the overpass. Use the existing junctions if at all reasonable.
Road Segment Lock Guidelines
In Pennsylvania we have a set minimum standard for locking roads based on segment type. 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, imaging inaccuracies, and the like), but should not be locked lower.
A great time to implement these locks is while bringing the road types of an area into compliance with the current US road type standards (FC and highway systems). Lock the roads based on type after they've been set to current US road type standards.
Pennsylvania Minimum Locking Rank Standard
Segment Type
Statewide
Freeway
5
Ramp
Highest rank of connected segments
Major Highway
3
Minor Highway
3
Primary Street
1 (Auto)
Street
1 (Auto)
Private Road
1 (Auto)
• • • • Ferry • • • •
5
|-|-|-|-|-|-|-|-|-| Railroad |-|-|-|-|-|-|-|-|-|
2
Note: Do Not Mass Edit just to update locks to these standards, these can be adjusted as you find them while editing other aspects of the segments such as FC, speed limits, naming, etc.
Some segments still warrant higher locks and care should be taken when setting segment lock to these standards to look for and protect these special setups with higher locks. Some examples; segments which are part of BDP, U-turn prevention, or using micro-doglegs, or other complex intersection setups.
Base Map Areas
There are still many areas in Pennsylvania 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, and no elevation adjustments are required, 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 the turns.
If roads are very bad and very difficult to fix, you may report the problem to a 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.
Micro-Doglegs
We use micro-doglegs to control turn- vs. stay/keep/exit instructions. Zoom in very close to see the closely-spaced geometry nodes. Preserve them.
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 report it to a group leader.
Road Types, Names, and Functional Classification (FC)
Road type classification is not a focus of this mapraid. It has been addressed in many areas of Pennsylvania. If you find a large problem with road type, please contact a group leader.
Road Names are not a focus of this map raid. If you see any large problems with road naming, please contact a group leader.
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.
Mapping Resources
Only use sources that are allowed by Waze, like Streetview from within WME. Do not use Google Maps. Do not use Google Maps Streetview. Websites from businesses are considered allowed sources.
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!
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.
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.
