|
|
| Line 1: |
Line 1: |
| ''MegaMapRaid'' will begin Saturday, March 7, 2015 at 1500 UTC and will last approximately 4 days, until March 12, 0300 UTC.
| | #redirect [[MegaMapRaid/Bay_Area,_California]] |
| {{mbox
| |
| | type = critical
| |
| | small = left
| |
| | textstyle = color: red; font-weight: bold; font-style: italic;
| |
| | text = This page is under construction, and is not yet ready for Mega Map Raid: please check back later in the week
| |
| | smalltext = Text for the top of article sections.
| |
| }}
| |
| ----
| |
| [[File:MMRMapBayAreaPrelim.jpg]]
| |
| | |
| ==Welcome to Northern California!==
| |
| The group will be divided into {{font color||red|'''17'''}} teams, one for each section, and two exclusive teams; one to handle PURs, the other for the Waze provided problem sheet. Each team will have their own assigned senior editors (rank 6, or 5) who will be able to edit anywhere in the Raid area, but will focus on their assigned section.
| |
| | |
| To begin, make sure to review the [https://wiki.waze.com/wiki/MegaMapRaid MegaMapRaid] main wiki page, the [https://wiki.waze.com/wiki/California California] wiki page, and its associated [https://wiki.waze.com/wiki/California/Places Places] wiki page.
| |
|
| |
| === {{font color||red|Raid Areas}} ===
| |
| The MapRaid area is being divided up by teams. You can see the [http://mapsengine.google.com/map/u/0/edit?mid=zIoPO0KHtaWo.khISn97ChBmQ interactive map] with all the teams, and PUR areas drawn out [http://mapsengine.google.com/map/u/0/edit?mid=zIoPO0KHtaWo.khISn97ChBmQ here].
| |
| | |
| ====Raid Groups====
| |
| | |
| | |
| ====PUR Areas====
| |
| | |
| | |
| == Mission ==
| |
| | |
| Our primary mission will be to handle the URs, and PURs, followed by Place validation, and general map verification.
| |
| {{mbox
| |
| | type = critical
| |
| | small = left
| |
| | textstyle = color: red; font-weight: bold; font-style: italic;
| |
| | text = Functional Classification (FC) has been implemented for the Bay Area. Some road types deviate intentionally from the state DOTs classifications. If you find a road which you feel is not classified correctly or set to the right type, please contact a local champ or State Manager (SM) before making changes.
| |
| | smalltext = Text for the top of article sections.
| |
| }}
| |
| | |
| ==Local Hosts==
| |
| | |
| {{Username|jemay}} - Southwestern Regional Coordinator
| |
| | |
| {{Username|ottonomy}} - US Local Champ & Mentor
| |
| | |
| {{Username|tonestertm}} - California State Manager
| |
| | |
| ==Important!==
| |
| '''Please do not alter any of the following road ''types'' without first consulting a [[#Local Hosts | Local Host]]''': Freeway, Ramp, Major Highway, minor Highway, Primary Street.
| |
| | |
| '''Please do not mass-edit''' Do not perform edits which will affect large numbers of segments at once. The edit history of segments is highly valuable in the process of solving URs. Mass editing effectively mass erases this history, permanently. We ask that all necessary processes which might affect large portions of the map, or long stretches of roads, be reserved until near the end of the MapRaid, using the [[#Scheduled Edits | Scheduled Edits]] form, below. This includes the “Select entire street” function.
| |
| | |
| '''Anything locked at 5 or 6?''' Please check with a local editor before making changes. Rank 5 and 6 editors - consider keeping highlights active for locks 5 and 6, so as not to inadvertently miss an intentional unusual edit.
| |
| | |
| '''Close nodes''' We make use of the "micro-dogleg" technique, where a geometry node is carefully placed, at full zoom, directly next to a junction node, in order to set the angle to create a desired Turn/Stay/Exit prompt. Please watch for these if you move any junction node, and be sure to recreate the same angle at the new location.
| |
| | |
| ==Local Guidance==
| |
| | |
| ===Functional Classification===
| |
| | |
| In the United States, we set our road types using a national standard called Functional Classification (FC). You can read a detailed explanation in our [http://wiki.waze.com/wiki/Road_types/USA#Functional_classification Road Type Wiki]
| |
| | |
| The Functional Classification has been completed in the San Francisco Bay Area. Occasionally, we find short segments that were missed in the selection process for conversion, and it is important that these be corrected for routing continuity. In general, however, we ask that Road Types not be changed without consulting one of the [[#Local Hosts | Local Hosts]]. In isolated cases, we have chosen to deviate from official classifications, due to errors or outdated information in the Caltrans (DOT) FC maps, or to better accommodate real-life situations and Waze quirks. It is important that these remain intact. Sometimes dirt roads may appear higher on FC maps but shouldn't be used by Waze for routing. Unfortunately, at the moment, our interactive map is not working for Roads or Functional Classification. You can go to [http://earth.dot.ca.gov/ Caltrans Earth] and select the CRS Maps layer, then click on the area you want, which will pop up a link to download the right map for that area, in pdf form. Or you can go straight to the [http://www.dot.ca.gov/hq/tsip/hseb/crs_maps/ CRS Maps Grid] site, which allows you to select the correct map according to a grid system.
| |
| | |
| If you find an area that doesn't seem to be complete please bring it to the attention of a Local Host for review.
| |
| | |
| We observe the following minimum lock levels for Waze road types:
| |
| | |
| '''Freeway (Fwy) - 5'''
| |
| | |
| '''Ramp - 5'''
| |
| | |
| '''Major Highway (MH) - 3'''
| |
| | |
| '''minor Highway (mH) - 2''' - In some dense metropolitan areas, the minimum lock for mH is 3
| |
| | |
| '''Primary Street (PS) - 2'''
| |
| | |
| '''All others - 1, or as needed'''
| |
| | |
| | |
| Note that these are minimums and, for protection, certain segments may be at higher lock levels. If you find a road locked to a higher level than its minimum, please leave it locked no lower than that level when you have finished editing.
| |
| | |
| ===Place Editing===
| |
| | |
| Places and updates from both editors and trusted users have become a major issue. Misspelled names, wrong categories, missing addresses (EVERY business place should have an address!!) poor location and incorrectly assigned photos are all over the map. Use the powerful Place Browser (link below) and the information on the [https://wiki.waze.com/wiki/California/Places Place editing] page to get these places corrected. Please do not lock a place without first confirming the correct location, naming, and category, and filling ''at least'' the address fields.
| |
| | |
| Also be on the lookout for Area Places which should actually be Point Places. See the [https://wiki.waze.com/wiki/Places#When_to_use_Area_or_Point Places] wiki table for guidance.
| |
| | |
| '''Gas Stations'''<br>
| |
| Gas Stations should be locked to level 3 but, only after all important data fields in the gas station have been filled. At least ensure that Brand, Name and Address have information. Remember to ask a hosting local if you need help identifying gas station information. When a convenience store is co-located with a gas station, naming varies, depending on the setup. ARCO ampm and Chevron Extra Mile have brand-associated convenience stores, and should include that Category. Circle K convenience stores, for example, are sometimes affiliated with certain gas stations and should have their own, separate, Place Point.
| |
| | |
| For editors below rank 3, once you have completely filled out a gas station with the min required information, please ask for a lock.
| |
| | |
| ===Complex Intersections===
| |
| | |
| There are many complicated intersections in the Bay Area which should not be edited without consulting a local senior editor, even if the presence of URs seems to indicate problems. Some of these intersections have been carefully refined to achieve the best Waze performance, which can involve years of testing, adjustment, and experimentation. Others are locations which are currently under construction, and daily changes to the physical roads cause Wazers to report problems which will no longer exist by the time our edits could take effect. We have done our best to lock the most important of these intersections to Rank 6. When dealing with URs at these locations, please keep in mind that few, if any additional road changes are required. Again, please consult with a [[#Local Hosts | Local Host]] before making changes.
| |
| | |
| ===Toll Roads / HOV / HOT / Truck Lanes===
| |
| | |
| It is our custom to mark the Toll checkbox ''only on the entrance segments'' to Toll Roads, or at Toll collection locations. HOV and HOT road types have already been set correctly according to our local practices. If you have a question about one of these lanes, please contact a [[#Local Hosts | Local Host]].
| |
| | |
| ===Left turns at intersections without traffic signals===
| |
| | |
| '''In California it is perfectly legal to make a left turn across one double yellow line.''' Drivers are sometimes confused and think that they can't, when in reality it is permitted. Turning across ''two'' double yellow lines, spaced apart 2 feet or more, is considered a barrier, and is illegal to cross. '''Passing''' another vehicle over a double yellow line is prohibited. For illustration of these concepts, visit the California DMV Drivers' Handbook [http://apps.dmv.ca.gov/pubs/hdbk/traffic_lanes.htm page on traffic lanes]
| |
| | |
| A common complaints we receive in the Bay Area is when Waze directs drivers to turn left from a smaller side street on to a major thoroughfare, without the benefit of a traffic control signal. Most of these turns are completely legal and, when driven properly, can be significant time-savers on a route, as opposed to waiting at a traffic signal, sometimes through several cycles. It is also known that making such turns can be difficult at certain times of the day, due to passing cross-traffic. On many larger roads in California, we have Center Left Turn Lanes, which are intended for use in completing left turns to, and from, driveways and side streets. Please '''do not''' disallow left turns due to URs reporting “dangerous” or “too difficult” turns, without consulting a level 4, 5 or 6 Local Host.
| |
| | |
| We usually inform the reporter of such a UR that if they wait and complete the left turn, it may actually be faster than the alternative. If it’s not faster, then their wait time will contribute to Waze’s database, thus helping to discourage the routing server from suggesting left turns at that site. We also suggest to the reporters that if they feel too uncomfortable making such left turns, they can always turn right instead, and let Waze recalculate. More info about this can be found on the [http://wiki.waze.com/wiki/California/Map_Raid_LA/UR_Guidance UR Guidance] page.
| |
| | |
| ===Construction===
| |
| | |
| There are a number of major construction projects in process within the overall MapRaid area. These construction projects can cause frequent intermittent road closures. Many closures change daily and cause great numbers of URs to appear. When handling URs in one of these areas, be aware that reports of "Turn not allowed", "Missing road", "Wrong driving direction" are common, but may not indicate a map problem that can be fixed, because the physical road situation will change before our edits can take effect.
| |
| | |
| LINKS:
| |
| | |
| | |
| | |
| [http://www.dot.ca.gov/dist4/ Caltrans (CA DOT) District 4 Projects]
| |
| | |
| | |
| | |
| ===U-turns===
| |
| | |
| In California, U-turns are generally allowed unless unsafe, or specifically denied by signage. In general we can confirm, lock or "harden" U-turns (click to remove the Purple question mark indicating a soft turn -- see [[Turn_restrictions#Turn_restrictions|the Wiki]]) on major streets, which have room for large vehicles to turn, but please avoid confirming or enabling them on residential streets.
| |
| | |
| ===Alleys===
| |
| | |
| In California, we have many access/service roads which run behind businesses and between houses on residential streets. We mark these Alleys as Parking Lot Roads, to prevent routing through them.
| |
| | |
| Often, Google address points are closer to these alleys than to the street they belong to, and Waze routing suffers. The correct response is to "nudge" the House Numbers on the streets along (either side of) the alley, so they will become trusted. See the UR page below for a suggested response to these issues.
| |
| Alleys should not be named, unless they are signed, or are already named "Alley".
| |
| | |
| ===UR & MP Guidance===
| |
| Investigating and responding to URs and MPs will be a primary objective of the MapRaid teams. Therefore, a [[California/Map_Raid_LA/UR_Guidance|UR Guidance]] page has been created to help guide teams through the maze of MPs and URs.<br /> There are also various scripts available to help with commenting on URs. If you use one of these, please be sure to check if the UR is solvable with the information already given, before sending a comment. All too often, editors are abusing these scripts and entering comments without first examining the available information. This behavior will be frowned upon.
| |
| | |
| Also, DO always leave a closing comment; no UR should be closed without one.
| |
| | |
| | |
| ===Cameras===
| |
| | |
| '''Speed Cameras''' are never used in California.
| |
| | |
| Following is a list of Bay Area Cities known to currently use '''Red Light Cameras''':
| |
| | |
| Capitola
| |
| | |
| Daly City
| |
| | |
| Fremont
| |
| | |
| Menlo Park
| |
| | |
| Millbrae
| |
| | |
| Napa
| |
| | |
| Newark
| |
| | |
| Pleasanton?
| |
| | |
| San Francisco
| |
| | |
| San Leandro
| |
| | |
| San Mateo
| |
| | |
| This list may not be comprehensive, so if you have doubts about a city not on this list, please do some web research, preferably with the city's official site or their police/sheriff department's site.
| |
| | |
| ==Mapping Resources==
| |
| | |
| Our local GIS maps ([[#GIS|see below]] for links)are almost always more up-to-date and correct than the Caltrans information. Please use them instead of any Caltrans documentation.
| |
| | |
| ===GIS===
| |
| Most of the interactive viewers in the links below will open with many layers enabled. The maps will run faster if you disable everything but Streets or Roads, and only enable Parcels when needed.
| |
| [http://www.marinmap.org/Html5Viewer/Index.html?viewer=mmdataviewer Marin County]
| |
| | |
| [http://imsportal.sonoma-county.org/ActiveMap/ Sonoma County]
| |
| | |
| [http://gis.napa.ca.gov/gcmaps/?Viewer=Public Napa County]
| |
| | |
| [http://regis.solanocounty.com/SilverlightViewer_1_9/Viewer.html?ViewerConfig=http://regis.solanocounty.com/Geocortex/Essentials/REST/sites/TaxParcelviewer/viewers/TaxParcelViewer/virtualdirectory/Config/Viewer.xml Solano County] (requires Silverlight plugin)
| |
| :[http://gis.zoomprospector.com/client/Vallejo/ Vallejo]
| |
| [http://gismap.ccmap.us/imf/imf.jsp?site=ccmap Contra Costa County]
| |
| | |
| [http://www.acgov.org/assessor/resources/parcel_viewer.htm Alameda County]
| |
| | |
| [http://sfgov.maps.arcgis.com/home/webmap/viewer.html?useExisting=1 San Francisco]
| |
| | |
| [http://maps.smcgov.org/planning/ San Mateo County]
| |
| | |
| [http://www.sccgov.org/arcgis/SCCPubInteractiveMap/# Santa Clara County]
| |
| | |
| [http://gis.co.santa-cruz.ca.us/PublicGISWeb/%7C Santa Cruz County]
| |
| | |
| == Communication ==
| |
| Communication will be handled mainly in Slack and WME chat which means WME Chat addon will be required (which can be found [http://www.waze.com/forum/viewtopic.php?f=819&t=95038 here]).
| |
| Chat rooms will be split up and named by location or group.
| |
| | |
| In addition, there is a Waze Forum dedicated to the MapRaid [http://www.waze.com/forum/viewforum.php?f=1350 here], where questions can be asked, and specific issues may be identified as the Raid progresses.
| |
| | |
| == Reference Links ==
| |
| | |
| === The Basics ===
| |
| *[[Waze Map Editor/Welcome|New editor welcome page]]
| |
| *[[Waze Map Editor]]
| |
| *[[Best Map Editing Practice]]
| |
| *[[Editing manual]]
| |
| *[[Common editing mistakes]]
| |
| *[[Permalink|How to make a Permalink]]
| |
| *[[WME Chat|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 MegaMapRaid San Francisco Bay Area===
| |
| * The [http://greasyfork.org/en/scripts/7094-wme-mapraid-los-angeles-overlay LA MapRaid Group/Region Overlay] is available on GreasyFork to indicate the Group areas on the map as you work. You will need TamperMonkey (Chrome) or GreaseMonkey (Firefox) to install and use this.
| |
| | |
| * [http://www.google.com/url?q=http%3A%2F%2Fwiki.waze.com%2Fwiki%2FUser%3ARickzabel%2FUrComments%2F&sa=D&sntz=1&usg=AFQjCNF3YdPXqECiZuPNd9F3MqtR2xgSiQ UR Comments] - a tremendous time and labor saving tool with automation and integration with URO+, to help with working URs. Read the documentation.
| |
| | |
| * [http://joyriding-001-site1.myasp.net/?group=MapRaidLA Place Browser] - In combination with the [https://wiki.waze.com/wiki/California/Places#Place_Name_Harmonization Place Name Harmonization] list, this is an invaluable tool for working on existing places. Be sure to click the About tab to get an overview of the tool.
| |
| | |
| * The [http://drive.google.com/file/d/0B8WbeRGWGEOjQ1BvbHFtYlJSV2pIOVdyQlgtRmJzQUtHNjRz WME Reference Sheet<sup><small><nowiki>[PDF]</nowiki></small></sup>] is a printable double-sided tri-fold quick reference guide to some of the common topics used in WME.
| |
| | |
| * [https://www.waze.com/forum/viewtopic.php?t=76488 Validator] is a script that validates a map area in Waze Map Editor, highlights issues and generates a very detailed report with wiki references and solutions.<br>
| |
| Download links:
| |
| * For Chrome browser please download the script at [http://chrome.google.com/webstore/detail/wme-validator/baojhpeknpmkhplkcnpdcficcaaniaih Chrome Web Store]
| |
| * For Firefox browser please download the script at [https://greasyfork.org/scripts/1571-wme-validator GreasyFork.org]
| |
| ''Note: for Firefox browser you also need Greasemonkey or Tampermonkey installed.''
| |
| | |
| * [http://greasyfork.org/en/scripts/2103-wme-chat-addon WME Chat Addon] is a script that improves the WME chat GUI. For a list of all the features check the thread [https://www.waze.com/forum/viewtopic.php?f=819&t=95038 here].
| |
| Tapermonkey/Greasmonkey is required to use this script
| |
| ----
| |
| | |
| {{Mbox|type=forum|text=Click [http://www.waze.com/forum/viewtopic.php?f=3&t=120113 here to view the MapRaid! LA forum] thread}}
| |
| | |
| == 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.
| |
|
| |
| ===Scheduled Edits===
| |
| | |
| These are edits which need to be completed but must be postponed in order to retain history for UR Solving. These edits are designated to specific editors to complete, once they get the green light from the MapRaid! leaders.
| |
| {{Mbox|type=critical|text=<big><big>'''These editing tasks have been delegated to specific editors for future completion at the end of MegaMapRaid. {{red|Please {{u|DO NOT EDIT or try to fix any of these items unless you are the designated "Editor to Complete"}} for that item in the list.}} These edits may only be completed once the {{u|"Continue When"}} instructions on the row for that item are met. If you have any questions please ask one of the listed [[#Local Hosts|Local Hosts]].'''</big></big>}}<br />
| |
| | |
| '''<big>Please enter new information on [http://docs.google.com/forms/d/161SBxzMA5KzvDYKoiLqBcdH_TsXNV6pXRfIHL_gpnwY/viewform? this form]</big>'''
| |
| | |
| [http://docs.google.com/spreadsheets/d/1eiXLMZicyM9AL0wnZxCOSYlmlHqwVkxT7NrV0416GBk/pubhtml?gid=488622377&single=true Click here to view this list in fullscreen]
| |
| {{#widget:Google Spreadsheet
| |
| |key=1eiXLMZicyM9AL0wnZxCOSYlmlHqwVkxT7NrV0416GBk
| |
| |width=100%
| |
| |height=300
| |
| |page=false}}
| |
| | |
| === Boots on the ground ===
| |
| | |
| We need local boots on the ground to check things. Please add requests for locals to go and scout things in person, as in on the road.
| |
| Some examples when this would be used include to check and see if:
| |
| * The street view is accurate,
| |
| * A road is really closed,
| |
| * A turn really allowed/prohibited, etc.
| |
| | |
| '''<big>To make a new request, or respond to an existing request, please use [http://docs.google.com/forms/d/1U1dSWZ8ZkNQa_FGldXDenDGvB2xsuD2N6vYczFW_eXY/viewform this form].</big>'''
| |
| | |
| [http://docs.google.com/spreadsheets/d/1KkgTWfNYflSZI4XFZmUktUbwoX3hVJBW2yvEdg1sC68/pubhtml Click here to view this list in fullscreen]
| |
| {{#widget:Google Spreadsheet
| |
| |key=1KkgTWfNYflSZI4XFZmUktUbwoX3hVJBW2yvEdg1sC68
| |
| |width=100%
| |
| |height=300
| |
| |page=false}}
| |
| | |
| == Results ==
| |
| | |
| {{Mbox
| |
| | type = speculation
| |
| | text = [http://i.imgur.com/pBRqBhG.jpg #MegaMapRaid Hall of Fame]}}
| |
| | |
| == 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.
| |
| | |
| | |
| == Teams ==
| |
| | |
| [[Category:Mapraid]]
| |
