User:PesachZ/SyncScratch View history

Mapraid
VisualWikitext
m (Copying text of wiki page for coparison with the "Minnesota/Special roads/Main" page)
m (Copying text of wiki page for coparison with the "Tennessee/Speed Limit Mapraid" page)
Line 1: Line 1:
<!-- This page is only transcluded into (displayed on) the main page for this state. See more detailed instructions below. --><noinclude>{{:USA/CommonState/ReturnPurge|{{SubPage2}}}}<br/></noinclude><!--
'''This page is still under construction, but will be ready soon!'''
------ DO NOT MODIFY ABOVE THIS LINE -------- DO NOT MODIFY ABOVE THIS LINE ------>
=== Ramsey County Lettered Roads ===
The Ramsey County lettered roads are a special situation.  They do not get abbreviated with the letter.  For example County J should not be named CR-J or CH-J.


These roads have a long history. They were laid out by Ramsey County on unincorporated land north of St Paul before most of the cities we know today were created. [http://www.historicmapworks.com/Map/US/487761/Index+Map+001/Ramsey+County+1931/Minnesota/ See a historical 1931 map here].  As cities incorporated land, many of them kept these names even though they were no longer county owned and maintained roads.  As far as Ramsey County is concerned, if it is a county owned road, it will have a #. For example County J is Ramsey County 1.  All the official blue 5-sided Ramsey county sign's only have the numbered routes.  Nowhere is there a letter on a blue shield sign (in Ramsey County).  So that's why we don't abbreviate them.  CR- should eventually make the white county sign, and CH- should eventually make the blue county sign, The lettered roads never appear on a blue or white sign, so they do not get the CR- or CH- abbreviation.  Also some of these are not even county owned roads so they don't get upgraded to primary street by default either.  For example, [https://www.waze.com/editor/?env=usa&lon=-93.13445&lat=45.03588&layers=5&zoom=9 Count D at this link] is a city road maintained by the cities of Roseville and Shoreview who have decided to leave the road named as County Rd D.  It is not a Ramsey County owned or maintained road and has no white or blue county highway signs.  So it is named "County D" to match the street signs and is classed as a street classification.  It is not upgraded to a primary street because it is not a real "County Road."
{{mbox|type=warning|text=
{{Mapraid dates
|raidname=TN Speed Limit Mapraid 2016
|formlink=//docs.google.com/forms/d/e/1FAIpQLScrKqWsXSARTPjEiS0t2tI2Rom3wRATQp1ajonhmTQMXe3aNw/viewform?c=0&w=1                                                                          
|endreg=2016-09-09T2100
|startraid=2016-09-23T2100
|endraid=2016-10-03T2100}}
}}<!--


One bit of trivia since it is often asked, where are the missing letters? County A was where Larpenter Ave is today and County G was where Highway 96 is today.
The timed statement will automatically change if you put in the correct date/ UTC times.
Remove the "under construction" notice when the page is ready to be read.
-->
<!--
  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>
-->
The '''Tennessee Speed Limit Mapraid'''
will be '''23 September''' through '''3 October  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 ==
# The primary goal of this mapraid is to set speed limits on {{Minor Highway}} and {{Primary Street}} segments throughout the state of Tennessee. Freeways and Major Highways should already have 100% of speed limits set, but if you come across one that is incorrect please bring it to your group leader's attention.
# Roads with the {{Street}} type are also within the scope of the raid, but are considered low priority and editors should not expend significant time on them unless associated with an update request. Mass editing of speed limits on streets within urban areas based on local laws and regulations is discouraged during the raid.
# Many minor Highways are state routes that need to have their names properly formatted (see below for details). Doing so is encouraged if this can be easily done when setting speed limits.
# In light of the fact that many rural areas in Tennessee have significant amounts of basemap, 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, or if fixing these issues would significantly impede progress on the other three goals, contact your group leader or[[File:Google form icon.PNG|frameless|15px|link=//docs.google.com/forms/d/e/1FAIpQLSffylnoHWzXgZV4PbZ5A0d16sUigAxwOVFvmidLahfF56_Gtg/viewform?c=0&w=1]][//docs.google.com/forms/d/e/1FAIpQLSffylnoHWzXgZV4PbZ5A0d16sUigAxwOVFvmidLahfF56_Gtg/viewform?c=0&w=1 record it in this form].


=== Other drivable roads ===
==Hosts==
(table here)


==== Dirt Road / 4X4 Trail[[File:Service road.png|200px|Service road.png]] ====


{{mbox
== Communication ==
| type = important
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://wazeusa.slack.com/messages/general 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.
| text = Minnesota has different interpretations of Dirt Roads than many other locations.  Even veteran editors need to pay attention to this section!
}}
 
 
[[File:MNdirtrd.jpg|300px|left]]In the state of {{RootPage2}}, most unpaved roads are considered [[Road_types/USA#Dirt_Road_.2F_4X4_Trail|dirt roads]].  Knowing this will help you create the correct road levels. Undrivable roads should not be mapped, should be restricted, or should be listed as a trail instead and not be connected to any functional roads.  Even though 4x4 is in the title, we will only use dirt roads for standard gravel or dirt roads that most vehicles can drive on.  Keep in mind that because of the way Waze handles dirt roads, we will not use the dirt road class in the city limits of any town.  Any in-town gravel roads will be streets.
 
Because most likely people in {{RootPage2}} feel a gravel road is a dirt road, we will use Dirt Road for both examples.  Please be aware of any of these dirt roads that are minimum maintenance roads as these roads should have [[Scheduled_restrictions#Segments|restrictions]] in place for winter months.
 
[[File:Dirtroad.PNG|300px|right]]
 
The reason the dirt roads classification is important is because a user can decide to not be sent on dirt roads or to only be sent on dirt roads for short distances in the settings of the Waze App. 
 
Keep in mind that if the person does allow for dirt roads, Waze will treat the road as a Primary Street so do not try to make an exception to well maintained dirt roads as a street or you will cause the driver to be directed on undesirable roads. Yes, that's right, a dirt road can be seen as a higher priority than a street! This is very important in rural areas where the Street Category should only be used on very short road segments that are paved. In towns, the Dirt Road Category should be rarely used and an unpaved road should be considered a street or a private road.
 
==== Parking Lot Road[[File:Service road.png|200px|Service road.png]] ====
 
[[File:Parklotrhmmn.png|right|300px]]
Parking lots roads are essential to navigating users to the proper destinations.  It also helps to properly exit a parking lot.  Follow these examples to creating parking lots correctly. Click the image to the right to see a well-designed parking lot section.
 
* Simple is best. Do not map every lane
* Map the main entrances from the roads outside the parking lot
* Map lanes that run along storefronts
* Map lanes that run along main roads outside the parking area
* Map primary lanes that serve to get people from one area of the lot to another


For for information about mapping parking lots, follow this [[Best_map_editing_practice#Parking_Lots|article]]
You can also use WME chat. The [http://www.waze.com/forum/viewtopic.php?f=819&t=95038 WME Chat addon] is recommended.


==== Private Road[[File:Service road.png|200px|Service road.png]] ====
== Groups ==
(cool map widget goes here)


[[File:Pi gated-community1.jpg|right|300px|Pi gated-community1.jpg]]
==Important / Mapraid guidelines==
[[File:Choose imperial units.png|thumb|right]]Please read the entire MapRaid wiki and familiarize yourself with the guidance on the [[Tennessee|Tennessee]] wiki page. 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.'''


Private Roads should follow the Wiki Example on [[Private_road#Private_Road|Private Roads]]. Please be very limited on using this for [[Driveways|driveways]] as, for the most part, these should not be mapped at all.
===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 county or city websites. Do not rely on predicted speeds (with "verified" check box).


Keep in mind that on the Waze App, a private road will look like a street. Nothing looks more off than a bunch of streets connected to a dirt road.
Please set your WME preferences to '''imperial''' and enter speed limits in miles per hour.


If you are adding a private road for a private housing section, make sure house numbering is correct or there is a place point or area within a private road section. This area will still be able to be navigated to the correct destination as long as it has a proper address to navigate to. Pay attention to [[Private_Installations#Problem_Definition|this article]] for more information.
[[File:SpeedLimitReminders.png|frameless|right|400px]]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.


In the case of very long driveways, it may helpful to a driver to see the driveway mapped on the client app or even necessary for Waze to determine how to reach the destination. In those cases it may be prudent to add a road. See the article on [[Driveways]] for more information.
Tennessee follows the [[Speed_limits/USA|US guideline]] for speed limits, with a few exceptions listed below.


==== Alleyways[[File:Service road.png|200px|Service road.png]] ====
====Summary of National Guidelines====
<div style="float:right;">[[File:Speed_Limit_70.png|50px|thumb|Right|Regulatory<br/>Yes]]<br/>[[File:Advisory Speed Plaque.png|50px|thumb|Advisory<br/>No]]</div>
*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.'''


Avoid drawing alleyways unless it is considered a street by the general public.  Most alleyways should not be used to direct traffic and will cause unneeded [[Node_penalties#Junction_penalties|nodes]] in the road that can cause roads connected to the alleyways to be less desirable. Most alleyways that would be mapped will use the Private Road classification.
====Tennessee Specific Guidelines====


[[File:Pizzalola.png|300px|left]]
According to Tennessee Code Annotated [http://law.justia.com/codes/tennessee/2010/title-55/chapter-8/55-8-152 55-8-152], the following '''maximum''' speed limits apply in Tennessee, with individual counties and municipalities setting lower speeds on individual roads as needed:


This is a good example of where alleyways will be mapped.  This is in South Minneapolis at the corner of Xerxes Ave S and W 56th St.  It is also the location of Pizzeria Lola.  The parking at this location is on the side of the Cavé Vin building.  It is a one-directional section and the only way to leave is through an alleyway. In this case, you would create the section as a Private Road and you only map out what is needed to enter the parking lot and exit; however, you would not need to map any other section of that alleyway.
* Interstates and limited access freeways (urban and rural): 70 MPH
* Divided highways: 65 MPH
* Undivided and two-lane roads: 55 MPH
* Residential streets: 30 MPH


==== Roundabouts [[Image:Round.png |50px]] ====
Do NOT use the above to set speed limits on roads! However, if a UR reports a speed limit higher than one of those listed above, the report should be treated with skepticism.


{{RootPage2}} has been adding [[Road_types/USA#Roundabouts|roundabouts]] in many locations throughout the state. It is important to note that most roundabouts should only have three to four connections or it will sound confusing to a driver. Following this [https://www.waze.com/editor/?env=usa&lon=-93.94724&lat=44.16858&layers=2981&zoom=4 Example] will give proper turn information and roundabout icons on the screen.  If you would use multiple-point access, it instead will say the exit number such as, "At the Roundabout, take the 3rd exit".
In addition, many counties and municipalities have enacted ordinances that establish default speeds for certain road classes. Use these data only as a last resort if you have exhausted all other options, and are able to confirm the absence of signage in street view. Even so, do not use this information to mass edit speed limits onto neighborhood streets, but instead focus on Primary Streets and above.
[[File:Roundabouts.png|400px|right]]
This is an indication of what a user of Waze should see on an upcoming Roundabout.  It is clear at showing the direction of the turn.  It also will verbally say what is referenced on the signage such as "At the Roundabout, Continue Straight" or "turn left". This is the {{RootPage2}} Standard for creating and editing Roundabouts.  


'''DO NOT''' map the following speed limits:


* Construction zones - contact a state or area manager instead
* Variable speed limits based on digital signs - these can be found on several freeways
* School zones or other time-based speed limits - map to the maximum speed


[[File:Roundboutmn2.png|400px|left]]
===Base Map Areas===
There are still many areas in Tennessee 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.


This is how it looks when more than four exit points occur. It does not give clear guidance to the driver on what way to go aside from the highlighted road ahead. This should be avoided, Only add multiple connections per side if the signs clearly mark Exit numbers (Commonly seen on signs showing 5 or more exit points).
* Before setting speed limits on a segment, set the road direction correctly and correct all turns and other obviously incorrect information.
** Please use the TDOT FC Maps (see link on the TN wiki page) to determine road numbers and format (SR-xxx or TN-xxx).
** The FC maps list a large number of roads that had classifications upgraded in summer 2016. These roads are currently mapped as streets in Waze, but will be upgraded to Primary Street. Please do not fix these roads unless ALL other mapraid goals have been met in your area, as these will be addressed after the raid.
* 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.


Roundabouts will use the same functional class of the main route traveling through the roundabout.  Follow [[Creating_and_Editing_a_roundabout#Road_type|This Article]] for more information.
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.


If at all possible, drive through a roundabout after it has been created or updated.  Verify that it seems to give correct information.
Again, DO NOT mass edit speed limits onto neighborhood streets in urban/suburban areas.  


==== HOT & Hov Roads/Lanes ====
=== Update Requests (URs) ===
[[Image:Hovmn.png|right]]
Some editors have made URs about speed limits they have seen on the road. These all contain the string "mph" or are tagged with [WSLM]. If you can find these URs, you can use them to help you set the correct speed limit on that segment.
High Occupancy Toll or High-occupancy Vehicle roads are not yet handled 100% by Waze as of yet, but we will still map these out to prepare for that time.


These roadways have the following features:
Do not just update the speed limit on one segment where the UR was and close the UR. Do your research and update the speed limit on that whole section of road where the user has driven. Additionally, add any speed limits on any easily correctable segments such as connecting roads with visible speed limit signs. After all of that has been completed, please follow correct procedure with closing speed limit URs with appropriate closing comments. If you have concerns about one that needs to be closed, please let your group leader know.
* These lanes/roads allow both toll traffic and HOV traffic to traverse the same lanes.
* There are no toll plazas or booths for paying by cash. All tolls are paid electronically to maintain traffic speed.
* Entrances and exits to the HOT lanes are limited to help maintain high speeds.
* There are no entrance/exit combinations where the toll fare rules don't apply.
* Tolls are discounted or waived for users that meet High Occupancy Vehicle (HOV) requirements. These requirements may change based on time of day.


To avoid traffic from entering this section, all entrance ramps will be will be restricted as in [[Carpool,_HOV,_Transit_lanes#Example_configurations|this article]]. From there, nothing will be restricted so if a user decides to take this route, he or she will be directed correctly.
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.


This will all be changing shortly as we find a better way to develop these roads.
=== Road Types, Names, and Functional Classification (FC) ===


==== Bus or Cab Only Lanes[[File:Service road.png|200px|Service road.png]] ====
Road type classification is not a focus of this map raid. Freeways, Major Highways, and minor highways should already be classified correctly, while Primary Streets will be addressed after the raid. If you see and easily-fixable problem on the segments you are editing for speed limits, please consult with your group leader before fixing it.


When a road or lane is designated for bus or cab use only, mark that road segment(s) as a '''Private Road''' to prevent the Waze router from using that segment(s) for general traffic, since the majority of the users will not be able to use that lane. It is also advisable to set the turn restrictions to prevent turns into that segment(s), but permit turns exiting the segment.
Road Names are not a primary focus of this map raid, but if you see an easily-fixable problem on the segments you are already editing, please fix it. State highway names need to be in either TN-xxx or SR-xxx format as per the TDOT FC maps. If you see any large problems with road naming, please let a group leader know.


If a road is one-way but allows bus or cab traffic to flow the other direction, leave the road as one-way with the normal flow of traffic. There is no need to create a second road traveling the opposite direction for the bus and cab-only traffic.
===Places===
Places are not a focus of this mapraid. If you see obviously incorrect places that will cause incorrect routing or a staff locked advertisement place that is wrong, please let your group leader know.


==== Emergency Vehicle and DOT Service Roads [[File:Service road.png|200px|Service road.png]] ====
===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.


[[File:Emergency.jpg|right|300px|Emergency.jpg]] "Emergency and Authorized Vehicles Only" and DOT Service Roads are to be treated as Non-drivable roads. These are found primarily through the median of divided highways to connect opposite direction lanes. In most cases, these should not be mapped at all. If mapped, they should not be connected to any drivable road, with properties set to road type Private Road, and lock the segment at as high a rank as possible, up to rank 5. {{clear}}
==Mapping Resources==
Use Street View and Satellite View from within Waze and the sources listed below. Do not use any unauthorized online mapping resources and if you have any questions on legitimacy of a resource, please talk to you group leader.


=== Non-drivable roads ===
{{red|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!}}


==== Railroad [[File:Service road.png|200px|Service road.png]] ====
===TN Mapping Resources===
* [http://www.tn.gov/tdot/topic/maps-functional-classification Long Range Planning Functional Classification Maps]
* Several counties and cities have their own GIS sources. Please see the main page of the TN wiki for links.


[[File:RailroadTracksVanishingPoint.jpg|right|300px|RoadPicN11.jpg]]
== Tools for this mapraid ==


=== Basic References ===
;[[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]]; [//www.youtube.com/watch?v=xYmU6UPCiZs YouTube]
;[[WME Chat|All about using the WME Chat]]
;[http://drive.google.com/file/d/0B8WbeRGWGEOjQ1BvbHFtYlJSV2pIOVdyQlgtRmJzQUtHNjRz WME Reference Sheet<sup><small><nowiki>[PDF]</nowiki></small></sup>]
: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.
;[//www.youtube.com/watch?v=7f3GNL0_La0 How to Install a Chrome Extension (YouTube)]


Railroads are not yet added to the map, but these can be added to prepare the maps for when it is.  Mapping the tracks allows Waze to recognize spurious speed data from people Wazing on the train and prevent it from corrupting speed data for the adjacent road.
=== Basic Scripts and Extensions ===
<!--;[//greasyfork.org/en/scripts/20147-wme-nc-mapraid-overlay Mapraid Overlay]
:This script shows the boundaries of each mapraid group area. It may be useful to you if you have editable area in more than one mapraid group area.-->
;[//www.waze.com/forum/viewtopic.php?t=40705#p369457 WME Color Highlights]
: Install [//chrome.google.com/webstore/detail/wme-color-highlights/ijnldkoicbhinlgnoigchihmegdjobjc Chrome Extension] or [//greasyfork.org/scripts/3206-wme-color-highlights 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.
;[//greasyfork.org/scripts/13774-wme-speedhelper Speed Limit Helper]
: Makes it easier to add the correct speed limits.
: tampermonkey/greasemonkey required


;[//greasyfork.org/en/scripts/12402-wme-speeds WME Speeds]
:Adds colours to road segments to show their speeds.
: tampermonkey/greasemonkey required
;[//greasyfork.org/en/scripts/17112-wme-street-view-availability 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


;[//greasyfork.org/en/scripts/2103-wme-chat-addon WME Chat Addon]
:a script that  improves the WME chat interface. For a list of all the features check the thread [http://www.waze.com/forum/viewtopic.php?f=819&t=95038 here] --  Tampermonkey/Greasemonkey required


===Advanced Scripts and Extensions===
; [//greasyfork.org/scripts/17087-wme-context-menu 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 [//www.waze.com/forum/viewtopic.php?f=819&t=178371 WME Context Menu][[File:URO+ MPH.PNG|thumb|right|100px|URO+ settings to find speed limit URs]]
;[//greasyfork.org/en/scripts/1952-uroverview-plus-uro 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.
:* Install for [http://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].
;[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.
:* [http://chrome.google.com/webstore/detail/wme-validator/baojhpeknpmkhplkcnpdcficcaaniaih For Chrome Browser]
:* [http://greasyfork.org/scripts/1571-wme-validator GreasyFork.org for Firefox] -- Tampermonkey/Greasemonkey required


{{mbox
== Mapraid edit lists ==
| type = important
| text = Please notice that railroads have changed from previous interpretations of railroad mapping.  Even veteran editors need to pay attention to this section!
}}


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.


* Elevation will be set to the same elevation standards as a drivable road. When tracks junction a road on the ground, the Elevation should be set to Ground.
== Results ==
* If the railroad crosses a segment of road, it should be connected to the road to so the historical data for the rail crossing will be more accurate.
* Always select "None" for the city name. This avoids [[Smudged_city#Overview|city smudging]].
* Set railroad to 2-way directionality and Restrict turns ''to'' and ''from'' the railroad segments.
* Follow the [http://fragis.fra.dot.gov/Apps/GISFRASafety/ Federal DOT Railroad GIS] to verify the owner of the rail line to help on naming of the segment. Use the acronyms under RROWNER1 to help on naming.
* Name each segment using the rail owner name acronyms or abbreviations railroad.  For example, Twin Cities & Western Railroad uses TCWR. We would name this section TCW Railroad.  We leave off the R in the acronym because it would be redundant to say, Twin Cities & Western Railroad Railroad.
* Canadian Pacific uses the acronym CPRS, but it is more know as CP, so it will be called CP Railroad
*Do not map every piece of parallel track, such as in sidings or yards, or industrial spurs that don't cross any roads. Your work may otherwise be seen as clutter, much like mapping every parking lot row.
* Lock all railroads to a Level 2
* Keep segment lengths under 10,000 meters (32,808 Ft) – the longer the segment length, the more sluggish the editor is to respond to changes.
* Read [[Road_types/USA#Railroad|this section]] for more information about railroads.


==== Runway/Taxiway[[File:Service road.png|200px|Service road.png]] ====
{{Mbox
[[File:Aelrwmn.png|right|250px]]
| type = speculation
We will map all airports runways such:
| text = Check back here after the raid is completed to see the results and achievements}}


* These roads will not connect to any drivable sections
== MapRaid Promotions ==
* The runways will not be connected to each other
* Always select "None" for the city name. This avoids [[Smudged_city#Overview|city smudging]].
* Using [http://en.wikipedia.org/wiki/List_of_airports_in_Minnesota this article] we will find the airport code.  We will use the [http://en.wikipedia.org/wiki/International_Air_Transport_Association IATA] code unless the airport does not have one, then we will revert to the [http://en.wikipedia.org/wiki/International_Civil_Aviation_Organization ICAO] code.
* After finding the code, we will use [http://www.airnav.com/airports/ this] to find the runway numbers for the airport.
* Most of the time, you will see the number of the runway at the beginning and end of each runway from the aerial views.
* Name each runway as such: [Airport Code] Runway [x-x] ... for example, in the image to the right, you will see the runways for Albert Lea Municipal Airport.  The IATA code for this airport is AEL and it has two runways including Runway 5/23 & Runway 17/35 so one will be named "AEL Runway 5-23" and the other AEL Runway 17-35".


Please follow this Wiki article on [[Runway#Runway.2FTaxiway|Runways]] for information about how to set runways correctly.  These roads should be locked to the same standard as Airport Area itself.
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.


==== Ferry [[File:Service road.png|200px|Service road.png]] ====
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.


{{mbox
{{mbox
| type = warning
| type       = speculation
| text = The Ferry Road type is not to be used at this time. '''Do not use the Ferry Road type for any purpose.''' See [[ferries]] page for more information on how to map ferries.
| text       = Watch here for results of promotions during and after the raid.
}}
}}
==== Walking Trails [[File:Service road.png|200px|Service road.png]] ====
[[File:RoadPicN9.jpg|right|300px|RoadPicN9.jpg]]
Because Waze currently only supports navigation for drivers and not walkers or bikers at all, we will not be drawing any of these types of roads.  Please delete any of these types of roads that you find.  If you find automatically set URs claiming a road is indicated to be be present, Please fill out the form located [//docs.google.com/forms/d/e/1FAIpQLSekzNg6aMKuxgz2fASws5Cjzadho9BLVKpHsZluWJgL446EyQ/viewform?c=0&w=1&usp=send_form Here] and choose Second Set of Eyes so a high level editor can check out the situation.
==== Pedestrian Boardwalks [[File:Service road.png|200px|Service road.png]] ====
Because Waze currently only supports navigation for drivers and not walkers or bikers at all, we will not be drawing any of these types of roads.  Please delete any of these types of roads that you find.  If you find automatically set URs claiming a road is indicated to be be present, Please fill out the form located [//docs.google.com/forms/d/e/1FAIpQLSekzNg6aMKuxgz2fASws5Cjzadho9BLVKpHsZluWJgL446EyQ/viewform?c=0&w=1 Here] and choose Second Set of Eyes so a high level editor can check out the situation.
==== Stairway [[File:Service road.png|200px|Service road.png]] ====
Stairways will not be added to Waze maps in Minnesota at all.  Please delete any of these sections that you find added to the map
== Speed Limits ==
Minnesota primarily follows the USA Speed Limits wiki: [[Speed_limits/USA | USA Speed Limits Wiki]] with some clarifications
=== Ramp Speed Limits ===
For ramps that are for accelerating to a road with a higher speed limit, use the higher speed limit of the destination road that the ramp goes to.
For ramps that go from a higher speed limit to a lower speed limit such as a freeway off ramp, do not place any speed limit on the ramp.
For ramps where the start and end have the same speed limit, keep the same speed limit on the ramp.
Do not use advisory speed limits that are black text on yellow signs.
=== Other Minnesota Specific Speed Limit details ===
The MN state laws for default unposted speed limits statewide are;
*Alleyways and mobile home parks <b>10 mph</b> unless otherwise posted.
*Urban residential roads <b>30 mph</b> unless otherwise posted.
*Rural roads <b>55 mph</b> unless otherwise posted.
Check with your Area or State Managers for clarification if needed.




<!---- DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ----
[[Category:Mapraid]]
-------------------------------------------------------------------------------------
---- This page is only transcluded into (displayed on) the main page for this state.
---- It directly follows the common guidelines applicable to all states. When this
---- page is present (even if blanked), it displaces any optional code that might be
---- in that section.
---- If the original optional code from the main page for this section is still
---- desired, it can be restored by adding the following code to the first line
---- between the "DO NOT MODIFY" lines on this page:
----  {{:USA/CommonState/Special roads|optional}}
----
-------------------------------------------------------------------------------------
---- If there will be a full page for this section, use code similar to the wording
---- below to provide a hyperlink to that page. When creating the full page, use the
---- link on the talk page to ensure the preload data is provided to help with
---- formatting the page. Don't just use the red link from this section once it is
---- saved.
----
See [[{{BasePage2}}/Special roads]] for guidance in {{RootPage2}} that may not be universal to all other states.
----
-------------------------------------------------------------------------------------
---- This section has three possible purposes:
---- 1. It is only providing a hyperlink to the full page for this section.
---- 2. It is only providing some unique guidance for this state that differs from
---- other states.
---- 3. It is intentionally wiping out the general optional content for this section
---- for this state.
------------------------------------------------------------------------------------>

Revision as of 17:35, 2 September 2016

This page is still under construction, but will be ready soon!
TN Speed Limit Mapraid 2016 ended on 03 Oct 2016 21:00:00 UTC. Please check back here for results and check the Mapraid Forum for mapraid announcements.

The Tennessee Speed Limit Mapraid will be 23 September through 3 October 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

  1. The primary goal of this mapraid is to set speed limits on  Minor Highway  and  Primary Street  segments throughout the state of Tennessee. Freeways and Major Highways should already have 100% of speed limits set, but if you come across one that is incorrect please bring it to your group leader's attention.
  2. Roads with the  Street  type are also within the scope of the raid, but are considered low priority and editors should not expend significant time on them unless associated with an update request. Mass editing of speed limits on streets within urban areas based on local laws and regulations is discouraged during the raid.
  3. Many minor Highways are state routes that need to have their names properly formatted (see below for details). Doing so is encouraged if this can be easily done when setting speed limits.
  4. In light of the fact that many rural areas in Tennessee have significant amounts of basemap, 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, or if fixing these issues would significantly impede progress on the other three goals, contact your group leader orrecord it in this form.

Hosts

(table here)


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

(cool map widget goes here)

Important / Mapraid guidelines

Please read the entire MapRaid wiki and familiarize yourself with the guidance on the Tennessee wiki page. 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 county 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.

Tennessee follows the US guideline for speed limits, with a few exceptions listed below.

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.

Tennessee Specific Guidelines

According to Tennessee Code Annotated 55-8-152, the following maximum speed limits apply in Tennessee, with individual counties and municipalities setting lower speeds on individual roads as needed:

  • Interstates and limited access freeways (urban and rural): 70 MPH
  • Divided highways: 65 MPH
  • Undivided and two-lane roads: 55 MPH
  • Residential streets: 30 MPH

Do NOT use the above to set speed limits on roads! However, if a UR reports a speed limit higher than one of those listed above, the report should be treated with skepticism.

In addition, many counties and municipalities have enacted ordinances that establish default speeds for certain road classes. Use these data only as a last resort if you have exhausted all other options, and are able to confirm the absence of signage in street view. Even so, do not use this information to mass edit speed limits onto neighborhood streets, but instead focus on Primary Streets and above.

DO NOT map the following speed limits:

  • Construction zones - contact a state or area manager instead
  • Variable speed limits based on digital signs - these can be found on several freeways
  • School zones or other time-based speed limits - map to the maximum speed

Base Map Areas

There are still many areas in Tennessee 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 TDOT FC Maps (see link on the TN wiki page) to determine road numbers and format (SR-xxx or TN-xxx).
    • The FC maps list a large number of roads that had classifications upgraded in summer 2016. These roads are currently mapped as streets in Waze, but will be upgraded to Primary Street. Please do not fix these roads unless ALL other mapraid goals have been met in your area, as these will be addressed after the raid.
  • 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.

Again, DO NOT mass edit speed limits onto neighborhood streets in urban/suburban areas.

Update Requests (URs)

Some editors have made URs about speed limits they have seen on the road. These all contain the string "mph" or are tagged with [WSLM]. If you can find these URs, you can use them to help you set the correct speed limit on that segment.

Do not just update the speed limit on one segment where the UR was and close the UR. Do your research and update the speed limit on that whole section of road where the user has driven. Additionally, add any speed limits on any easily correctable segments such as connecting roads with visible speed limit signs. After all of that has been completed, please follow correct procedure with closing speed limit URs with appropriate closing comments. If you have concerns about one that needs to be closed, please let your group leader know.

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. Freeways, Major Highways, and minor highways should already be classified correctly, while Primary Streets will be addressed after the raid. If you see and easily-fixable problem on the segments you are editing for speed limits, please consult with your group leader before fixing it.

Road Names are not a primary focus of this map raid, but if you see an easily-fixable problem on the segments you are already editing, please fix it. State highway names need to be in either TN-xxx or SR-xxx format as per the TDOT FC maps. 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 or a staff locked advertisement place that is wrong, please let your group leader know.

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.

Mapping Resources

Use Street View and Satellite View from within Waze and the sources listed below. Do not use any unauthorized online mapping resources and if you have any questions on legitimacy of a resource, please talk to you group leader.

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!

TN Mapping Resources

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.

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.
Retrieved from "https://www.waze.com/wiki/USA/index.php?title=User:PesachZ/SyncScratch&oldid=149643"