Pennsylvania/Speed limit mapraid: Difference between revisions Discussion View history

Revision as of 14:49, 19 February 2016

Pennsylvania Speed Limit Mapraid 2016 ended on 07 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 7 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).
Lower segment locks, as appropriate, to meet the new Northeast locking standards.

Hosts

Editor	Location	Roles
XXX(6) [PM [Help]]	Statewide	Map Raid Organizer

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 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

Placeholder for image map

Placeholder for group list

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

Elevation Guidelines

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.

**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. 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.

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)

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

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!

Reference Links

The Basics

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)

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

WME Toolbox

This script has lots of ways to help remove unnecessary nodes, cut segments, locate "Soft Nodes", or nodes with undefined directions.

Install for Chrome
Install for Firefox.

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.

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.

@@ Line 1: / Line 1: @@
 {{mbox|type=warning|text=
 {{Mapraid dates
-|raidname=Mapraid South Carolina 2016
+|raidname=Pennsylvania Speed Limit Mapraid 2016
-|formlink=http://waze.com
+|formlink=http://goo.gl/forms/i3L63t2lNI
-|endreg=2016-01-07T0000
+|endreg=2016-02-24T0000
-|startraid=2016-01-06T0000
+|startraid=2016-02-29T0000
-|endraid=2016-01-07T0000}}
+|endraid=2016-03-07T0000}}
 This mapraid page is still under construction. Please be patient as we get it ready for the upcoming raid.
@@ Line 16: / Line 16: @@
    Put the mapraid meme here.  Something like:
    [[File:Mapraid JerseyShore meme3.jpg|frameless|550px|center]]
+<div style="width:550px;height:200px;  margin-left:auto; margin-right:auto;border: 1px solid black;">Placeholder for mapraid meme</div>
 -->
-<div style="width:550px;height:200px;  margin-left:auto; margin-right:auto;border: 1px solid black;">Placeholder for mapraid meme</div>
+The '''Pennsylvania Speed Limit Mapraid'''
+will be '''29 Feb''' through '''7 March 2016'''.
-Optional short intro phrase.
+The participants will be divided into several
-'''MapRaid Location Month year'''
-will be '''dd Mmm
-through
-dd MMM yyyy
-'''.
-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.
-== Mission ==
+== Goals ==
-Our primary mission is to handle <!-- customize this to fit the needs of the mapraid area -->
+Our goals are:
-<div style="column-count:2;-moz-column-count:2;-webkit-column-count:2">
+# Put correct speed limits on segments in Pennsylvania, with emphasis on the connecting roads
-* URs
+# Use realistic elevations where roads cross (so-called seagull edits).
-* MPs
+# Lower segment locks, as appropriate, to meet the new Northeast locking standards.
-* PURs (Places)
-* General map verification and
-* Functional Classification.
-</div>
 __TOC__
 ==Hosts==
-*''The raid hosts and ''
-* ''Every participating editor who can help answer local questions. Generally:''
-** ''rank 3 and up''
-** ''from the state''
-** ''with AM area''
-** ''has been active recently''
 {| class="wikitable"
 |-
@@ Line 55: / Line 38: @@
 == Communication ==
-The main language of this mapraid is English. You can get help for translations.
+When you are editing in the raid area, please [[Waze_Map_Editor/Chat#Visible.2FInvisible|set yourself visible]] and enable the [[Map_Editor_Interface_and_Controls#Live_Users|Live Users]] layer. We will use [http://wazemapraid.slack.com/messages/general 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.
-When you are editing in the raid area, please [[Waze_Map_Editor/Chat#Visible.2FInvisible|set yourself visible]] and enable the [[Map_Editor_Interface_and_Controls#Live_Users|Live Users]] layer
-We will use ''#''Slack Channels. There is a [http://wazemapraid.slack.com/messages/
-xxx
-yyy Raid general channel] and also a channel for each raid group. {{U|Please be sure to join the slack WazeMapRaid Team and join the channels for the specific MapRaid and group you are assigned to.}} If you are not already part of the WazeMapRaid slack team, '''Click here to get your [http://bit.ly/GetWazeSlackInvite Slack invitation]. Be sure to choose {{u|WazeMapRaid}} to the MapRaid question.'''  If you have trouble getting into the slack team and channels, please reach out to one of the MapRaid organizers.
-WME chat can also be used. The [http://www.waze.com/forum/viewtopic.php?f=819&t=95038 WME Chat addon] is recommended.
+You can also use WME chat. The [http://www.waze.com/forum/viewtopic.php?f=819&t=95038 WME Chat addon] is recommended.
@@ Line 81: / Line 60: @@
 -->
 </div>
-<div style="width:350px;height:1500px; border: solid black 2px;">Placeholder for group list</div>
+<div style="width:350px;height:500px; border: solid black 2px;">Placeholder for group list</div>
 <!--
@@ Line 92: / Line 71: @@
 |width=350
 |border=0
-|height=1600
+|height=500
 }}
@@ Line 106: / Line 85: @@
 <!-- keep this list short. link to other pages where possible. -->
-===Mapraid UR Rules===
+===Speed Limits in Pennsylvania===
-<!--
+===Elevation Guidelines===
-      Usually, mapraid rules are as follows -- set the wait time (3 or 4 days).
+===Road Segment Locks===
-      Otherwise, write a whole new set of Mapraid UR rules
+{{Lock Standard State|NORTHEAST}}
--->
+===Base Map Areas===
-We will follow the [[Update_Requests_in_Waze_Map_Editor#The_resolution_process_.2F_Etiquette|usual US UR etiquette]] with one exception: During the Map raid, the wait time is reduced to
+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.
-X
+* Set the road direction correctly before setting speed limits
-days.
+* 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 ===
-Do not close URs if the UR contains a tag such as [NOTE], [CLOSURE], or any other [MESSAGE]. Ask the editor who created the tag.
+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.
-=== Do Not Mass-Edit ===
+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.
-DO NOT perform edits that affect large numbers of segments at once. We want to know who fixed what so we can understand how problems got resolved.
 [[File:Jct 4 offset align.png|frameless|right|100px]]
 === Micro-Doglegs ===
 We use [[Glossary#Micro-dogleg|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) ===
-In
+Road type classification is not a focus of this mapraid. It has been addressed in most areas of Pennsylvania. Pennsylvania follows the [[Road_types_usa#Quick_reference_chart|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.
-XXX
-, we ... <!-- follow the general [[Road_types_usa#Quick_reference_chart|US standards for road types]] based on the hybrid rule of FC and Route Type. -->
-We distinguish the
-different types of routes found in the state as follows:
-<!-- * Federal: '''I-195 E''', '''US-9'''
-* State: '''SR-35 S''', '''SR-72'''
-* County: '''CR-537''', '''CR-4'''
--->
-If a road has more than one name ...<!--follow the standard for [[Road_Naming_(USA)#Concurrent_names|Concurrent names on US roads]].-->
-===Road Locks===
-<!--
-      Copy the appropriate lock standard wiki template from the appropriate wiki page
-      For US mapraids, this will be from the state wiki page
-{{Lock Standard State|xx}}
+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.
-      Another option is to create a lock standard table from scratch. Here is an example:
-{{Locking Standard|lede=&nbsp;|caption=South Carolina Coastal Segment Locks
-|Fwy=5
-|MH=4
-|mH=3
-|PS=2
-}}
--->
 ===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.
-===Left Turns===
-''Will there be a lot of questions about when left turns are allowed?''
-<!--;Left turns are prohibited when:
-:* a posted sign prohibits the left turn
-:* there are two double yellow lines Sometimes, there is a raised median or diagonal striping between.This is often seen in the form of the "bubble" prior to a dedicated left turn lane,
-:* there is a dedicated left turn lane in the main road, not counting a bi-directional "suicide" center turn lane.
-;Left turns are allowed when:
-:* They are not prohibited (see above)
-:* Left turns are even allowed across a double-yellow line into a driveway or private road or parking lot. Double-yellow lines are usually interrupted at a public street where a left turn is permitted.-->
 ==Mapping Resources==
@@ Line 192: / Line 141: @@
 -->
-* <span style="background-color: lightgray;">mapraid overlay</span> (tampermonkey/greasemonkey required)
+;Mapraid Overlay -- coming soon.
-<!--
+: <span style="background-color: lightgray;">mapraid overlay</span> (tampermonkey/greasemonkey required)
-      Below is a generic link to all the place browsers.
-      Add the query string to customize it for this map raid
-      Here is an example from the SC raid
-      [//w-tools.org/PlaceBrowser?group=MapRaidSouthCarolina Map Raid Place Browser]
--->
-* [//w-tools.org/PlaceBrowser Map Raid Place Browser]
 ;[http://www.waze.com/forum/viewtopic.php?t=76488 Validator]
 :highlights issues on the map and can generate a very detailed report with U.S. wiki references and possible solutions.
@@ Line 208: / Line 149: @@
 ;WME Toolbox
-:This is a script that facilitate the process of editing maps in the WME. It has a toolbar that facilitates the process of removing unnecessary nodes, cut segments, locate "Soft Nodes", or nodes with undefined directions.
+:This script has lots of ways to help remove unnecessary nodes, cut segments, locate "Soft Nodes", or nodes with undefined directions.
 :* Install for [https://chrome.google.com/webstore/detail/wme-toolbox/ihebciailciabdiknfomleeccodkdejn?utm_source=chrome-app-launcher-info-dialog Chrome]
 :* Install for [http://gitlab.com/doctorkb/wme-toolbox-public/raw/master/Dist/Firefox/wmetoolbox.xpi Firefox].
@@ Line 214: / Line 155: @@
 ;[http://greasyfork.org/en/scripts/2103-wme-chat-addon WME Chat Addon]
 :a script that  improves the WME chat GUI. For a list of all the features check the thread [http://www.waze.com/forum/viewtopic.php?f=819&t=95038 here] --  Tampermonkey/Greasmonkey required
-;[//wiki.waze.com/wiki/User:Rickzabel/UrComments/ UR Comments]
-:a tremendous time and labor saving tool with automation and integration with URO+, to help with working URs. Read the documentation.  Tampermonkey / greasemonkey required
 ;[http://drive.google.com/file/d/0B8WbeRGWGEOjQ1BvbHFtYlJSV2pIOVdyQlgtRmJzQUtHNjRz WME Reference Sheet<sup><small><nowiki>[PDF]</nowiki></small></sup>]

Search