| The new Waze Wiki, aka Wazeopedia, is now live at Wazeopedia.waze.com! While this legacy wiki will remain accessible for the time being, it is no longer updated by the community. For the most up-to-date guidance, please visit your local Wazeopedia.
Please do not make any more updates to these legacy wiki pages, all future updates should be made in your country's local Wazeopedia.
Pennsylvania/Speed limit mapraid
|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. This mapraid page is still under construction. Please be patient as we get it ready for the upcoming raid.|
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.
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.
- 1 Goals
- 2 Hosts
- 3 Communication
- 4 Groups
- 5 Important / Mapraid guidelines
- 5.1 Speed Limits in Pennsylvania
- 5.2 Elevation Guidelines
- 5.3 Road Segment Locks
- 5.4 Base Map Areas
- 5.5 Edit Quality and Mass Editing
- 5.6 Micro-Doglegs
- 5.7 Update Requests (URs)
- 5.8 Road Types, Names, and Functional Classification (FC)
- 5.9 Places
- 6 Mapping Resources
- 7 Reference Links
- 8 Mapraid edit lists
- 9 Results
- 10 MapRaid Promotions
|OrbitC ( )||6||GC / MapRaid Coordinator|
|Voludu2 ( )||5||State Manager / Country Manager|
|DrNeubie ( )||4||State Manager|
|Odessit68 ( )||4||State Manager|
|Unlimited1808 ( )||4||State Manager|
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.
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 Limits in Pennsylvania
Pennsylvania follows the national guideline for speed limits, with a few exceptions listed below.
- 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
- 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.
PA Speed Limit Resources
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 greather 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.
- 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 Locks
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.
|Highest rank of connected segments|
Note: Do Not Mass Edit just to update locks to these standards, these can adjusted as you find 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. In these areas, most of the major roads are correct, but many of the smaller roads are incorrect in surprising ways. Please fix base map areas well enough to apply speed limits as appropriate, and feel free to leave the rest alone.
- Set the road direction correctly before setting speed limits
- If you discover incorrect or unconfirmed turn arrows, please fix them as you work.
- If you discover an area where the roads are obviously incorrect and are not easy to fix well enough, please feel free to leave it alone. In some cases, the best available external resources (county or state GIS maps) have the same incorrect information that was imported into WME in 2009, and there is no WME street view.
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 you edit segments previously edited by others, your name will be on these segments. This makes you responsible for any problems left on those segments, no matter who put them there originally.
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.
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)
Update Requests are one of the most important tools for finding problems to fix on the map. However -- solving all the problems on the map in Pennsylvania is not a focus of this mapraid. If you find an obvious problem that is causing problems for wazers, and you can fix it, please do so. If you find a problem that will require more help to fix, please contact your group leader or a mapraid host.
Road Types, Names, and Functional Classification (FC)
Road type classification is not a focus of this mapraid. It has been addressed in most areas of Pennsylvania. Pennsylvania follows the US guidelines for road types. If you think there are road type problems that may affect routing, please contact your group leader or a map raid host.
Road Names are not a focus of this map raid, but may be fixed, if necessary, while you are addressing speed limits and elevations on the same segments. Please see Pennsylvania#Naming for more information.
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.
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!
- New editor welcome page
- Waze Map Editor
- Best Map Editing Practice
- Editing manual
- Common editing mistakes
- How to make a Permalink
- All about using the WME Chat
- Community Plugins, Extensions and Tools where you'll 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.
Recommended Tools for MapRaid
- Mapraid Overlay -- coming soon.
- mapraid overlay (tampermonkey/greasemonkey required)
- highlights issues on the map and can generate a very detailed report with U.S. wiki references and possible solutions.
- WME Toolbox
- This script has lots of ways to help remove unnecessary nodes, cut segments, locate "Soft Nodes", or nodes with undefined directions.
- WME Chat Addon
- a script that improves the WME chat GUI. For a list of all the features check the thread here -- Tampermonkey/Greasmonkey required
- WME Reference Sheet[PDF]
- a printable double-sided tri-fold quick reference guide to some of the common topics used in WME.
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.
|Check back here after the raid is completed to see the results and achievements|
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.|