|
|
| (21 intermediate revisions by 7 users not shown) |
| Line 1: |
Line 1: |
| Speed limit (SL) data is part of each segment's details and is added from the Waze Map Editor. This speed limit is used by the client app to alert the Wazer when they exceed the speed limit designated on the Waze map by a threshold set in the app.
| | #REDIRECT [[Speed_limits]] |
| | | {{ReviewRedirects}} |
| This article discusses When, How, and Which speed limits should be added to the map in the USA. The guidelines set forth below may be expanded by local regional or state guidance, Please be sure to check your local wiki for any relevant information as well.
| |
| [[File:Speed_Limit_70.png|150px|thumb|Right|Speed Limit Sign]]
| |
| | |
| | |
| == {{@|Which speed limits should be added to the map}} ==
| |
| | |
| The '''ONLY''' speed limits added to the map are '''Regulatory Speed Limits'''. These must match federal, state, and municipal laws or regulations that designate enforceable maximum speeds for passenger vehicles. These are marked with black lettering on white rectangular signs.
| |
| | |
| | |
| === {{@|Fixed regulatory speed limits}} ===
| |
| | |
| Any fixed (non-variable) speed limits posted on the regulatory black and white signs should be added to the road corresponding segments in the WME.
| |
| | |
| | |
| ==== {{@|Ramps}} ====
| |
| | |
| If there is a regulatory speed limit sign posted on the ramp itself, this speed limit should be added for the ramp segments.
| |
| | |
| If the speed limit for the segments on either end of the ramp are the same, then that limit should be added to the ramp as well.
| |
| | |
| {{mbox|type=important|text=Ramps with only '''[[#Advisory speed limits|advisory speed limit]]''' signs, as shown below, should have '''no speed limit''' in the WME.}}
| |
| | |
| | |
| ==== {{@|At grade connectors}} ====
| |
| | |
| AGCs follow these 3 basic rules in this order of preference (apply first match):
| |
| # If it has its own dedicated posted regulation SL, use it.
| |
| # If the SL before and after are the same, use it
| |
| # If it physically looks and functions as a [[#Ramps|ramp]], leave it blank, otherwise use the SL of the segment feeding into the AGC (s-in)
| |
| | |
| {{expand|nt=yes|Basically there are three types of AGCs
| |
| # Extra segments we add to the map for ETA or prompt control, which are essentially just us mapping a specific lane of the road. These AGCs typically terminate at the intersection, and {{u|can be considered a part of the road they are on}}. <br>These would share the same SL as the segment they are coming from/run parallel with.(s-in)
| |
| # Segments that functionally are ramps which for some reason are not using the ramp type, these are median separated from the regular road, and includes acceleration / deceleration type lanes. <br>{{u|We can treat these just as [[#Ramps|ramps]]}}.
| |
| # Actual strips of road physically connecting different streets. Like triangle intersections these may or may not be named streets. With these in general they would legally follow the SL of the segment leading into them since the SL is applied until you enter a new zone which supercedes them. {{u|Therefore until you traverse the AGC to the new road where a new SL is in place you are still bound by the previous SL}}.
| |
| | the rationale behind these rules.}}
| |
| | |
| ==== {{@|Private}} ====
| |
| | |
| Speed limits that are designated on private property using regulatory signs may be added to road segments on the Waze map at the discretion of the Regional Coordinator or State Managers. Be sure to check your [[#Regional and state local wiki pages|local wiki]] for guidance.
| |
| {{mbox
| |
| | type = notice
| |
| | text = Speed Limits are added to parking lot and private road types by changing type to street, adding limits, then reverting to the original road type.
| |
| }}
| |
| | |
| ==== {{@|Work zones}} ====
| |
| [[File:Mbox construction yellow.png|150px|right]]
| |
| [[File:Work zone SL.png|150px|right|Work Zone Speed Limit sign]]
| |
| Speed limits in work zones are often lowered to protect workers and prevent collisions. If these speed limits appear on regulatory black and white signs, they '''MAY''' be added to the associated WME road segments, '''IF''' supported by your local area. However, this should be done in consultation with State Managers or Regional Coordinators, so that the temporary speed limits can be monitored for changes. It may be prudent to only modify the speed limit for long-term construction projects, each region must decide what terms are best locally.
| |
| | |
| <!-- To be removed once the SL feature is pushed to production clients in the USA -->
| |
| Another option is to add the underlying to speed limit to the map for now, and put the work zone speed limit in a specially marked UR note (or otherwise keep track of it). Being that {{as of|2016|02|alt=as of the writing of this page}} the speed limit feature is not yet functional in the production client app, this will prevent redundant effort to go back and fix the speed limits if the construction ends before the speed limit feature is rolled out.
| |
| | |
| Check your regional or state wiki to see which work zone limits should be added in your area, and the process for monitoring them.<br />
| |
| <small>''Click [show] below for links to your wiki.''</small>
| |
| {{USA Navbox}}
| |
| | |
| | |
| === {{@|Variable Speed Limits}} ===
| |
| [[File:Var Speed Sign.jpg|framed|center|Variable Speed Limits]]
| |
| The WME and Waze app do not support Variable Speed Limits (VSLs) that are changed based on traffic and road conditions. These VSLs can be changed at any time by government officials. If there is a 'standard' speed limit at which the signs on a stretch of road are set for the majority of the time, this 'standard' speed '''COULD BE''' added to the associated road segments in the WME. However, the setting of any speed limit on a road with VSLs must be made in consultation with the appropriate State Manager, or Regional Coordinator.
| |
| | |
| | |
| === {{@|Time based speed limits}} ===
| |
| | |
| {{As of|2016|02}}, the WME and Waze App only support a single speed limit, without variation for time of day, or day of the week. Segments with time based different speed limits should use the speed limit which is in effect the majority of the time (most hours of the day, days of the week).
| |
| | |
| For example let's assume a 35mph street has a reduced speed limit of 20mph for the hours of 7am-4pm School Days. Then it is not in effect every single day, and even the days it is in effect, it's only for 9 hours. The rest of the time the 35mph limit is in effect. This segment should be set to the 35mph limit.
| |
| | |
| | |
| | |
| === {{@|Unsupported speed limits}} ===
| |
| | |
| The following speed limits are unsupported by the WME and the Waze app, and '''MUST NOT''' be added to road segments in the WME. Road segments with posted 'advisory' speeds or special speed limits should continue the Speed Limit for passenger vehicles as posted on the '''black and white''' signs pictured above.
| |
| | |
| ==== {{@|Advisory speed limits}} ====
| |
| | |
| In addition, yellow 'advisory' speed signs (as shown below) are usually not enforceable; therefore, 'advisory' speeds, like the ones shown below, should '''NOT''' be added to the waze map.
| |
| <gallery>
| |
| File:Advisory_Plaque.jpg|Advisory Plaque
| |
| File:Right_Turn_Advisory.jpg|Turn Advisory
| |
| File:Exit_Speed_Sign.png|Exit Advisory
| |
| File:Exit_Sign_Speed_Plaque.gif|Exit Sign Plaque
| |
| </gallery>
| |
| | |
| ==== {{@|Special speed limits}} ====
| |
| | |
| {{As of|2016|02}}, the WME and Waze App only support maximum speed limits for passenger vehicles, without variation for time of day, or day of the week. Specialty, also known as 'bannered' speed limits, like the ones shown below, should '''NOT''' be added to the Waze map.
| |
| <gallery>
| |
| File:Night_Speed_Sign.jpg|Night Speed
| |
| File:Truck_Speed_Sign.jpg|Truck Speed
| |
| File:School_Speed_Sign.gif|School Speed
| |
| File:Minimum_Speed_Sign.jpg|Minimum Speed
| |
| </gallery>
| |
| {{mbox|text=School zone speed limits that are in effect 24 hrs per day, and 365 days a year, should be added to the map. }}
| |
| | |
| | |
| == {{@|Where speed limits change}} ==
| |
| | |
| Speed limits should change where they legally go in effect for your state, that may be at the sign, a specified distance before the sign, or the nearest intersection; check your [[#Regional and state local wiki|local wiki]] for the practice in your area. When a speed limit changes in the middle of a segment, {{u|a new junction should added to support the SL change}}.
| |
| * However '''a new junction should never be added for a SL if it will be within 200 feet of an existing junction''', or potential junction.
| |
| * Depending on your [[#Regional and state local wiki pages|local guidance]] this distance may be expanded above 200 feet, always confirm local practice.
| |
| * A new junction should always be added if it will be more than 1,000 feet from the nearest existing, or potential junction.
| |
| | |
| | |
| === {{@|Creating a new junction for a speed limit change}} ===
| |
| | |
| When creating a new junction solely for the sake of showing a speed limit change, you can attempt to get more value from the junction. Survey the area around the speed limit change, determine if there is a PLR or other segment which should be connected to the road and would result in a junction. You may find that there's a parking lot which could benefit from being added to the map within the allowable distance of 200 feet (or more depending on your area) to where the SL changes. In such a case connect that segment and use that junction. Otherwise you should create a new junction to show where the SL changes.
| |
| | |
| On roads where traffic for one turn direction typically backs up waiting to make the turn further than 200 feet, and traffic going straight or turning the other direction does not have to wait as long to pass through, turn delays can be affected even with the new junction 200 feet away. In these cases you may choose to extend the buffer zone to beyond the point where traffic backs up, and instead make the change at an existing junction node. These situations are governed by editor discretion and local guidance.
| |
| | |
| {{expand|nt=yes|
| |
| It is very important that we do not create new junctions too close to existing intersections, yet marking the speed limit change too far can have a negative impact on the user experience.
| |
| | |
| The minimum distance of 200 feet was chosen because a distance less than that is negligible, and unnoticeable in the client experience. It is not much different than the delay we expect with GPS lag and error anyway. For example think of where you hear the turn prompts announced, they can sometimes precede a junction by up to 200 feet.
| |
| | |
| We have confirmed directly with the routing developers that adding a junction node connecting only 2 segments does not have an associated [[routing penalty]]. We have also confirmed that creating and adding new junction nodes where necessary using these above guidelines will not have a negative effect on route calculation.
| |
| | |
| However there is a legitimate concern when adding new junctions too close to existing intersections / interchanges, that they may interfere with and pollute the ability for Waze calculate accurate [[turn delays]].
| |
| | |
| The reason to use a minimum of 200 feet from the nearest junction as a buffer is to account for turn delay calculations.
| |
| If we create junction nodes very close to intersections we will effectively eliminate Waze's ability to differentiate the time it takes to go straight, vs the time to turn left or right. {{u|A distance of less than 200 feet between junctions poses a significant risk to the ETA calculations (turn delays).}} Over 200 feet it is up to local practice , and the editor's discretion to determine if a junction node there will negatively impact turn delay calculations. We must stipulate a minimum buffer zone, but it doesn't need to be exact. The area between 200-1,000 feet is open to interpretation, editor discretion, and local guidance.
| |
| | |
| If an exit or turn lane does back up over 1,000 feet, it is unlikely that traffic beyond the 1,000 mark will be drastically affected by the new junction placed that far away. ''However specific exceptions with the consultation of Regional Coordinators, or State Managers will always be allowed.''
| |
| | |
| : The turn delay issue could potentially be mitigated by adding [[User:CBenson/Junction_Box|Junction Boxes]] to each of these situations to correct them. However doing so would result in a lot more work for editors, and a lot more strain on the servers. It would make it harder to manage these intersections since all the included segments, and turns get locked from editing. It will have an effect on route calculation timing as well. We therefore had to come up with a compromise that is still visibly accurate, without anything being noticeably different to the client user, yet maintaining the ability for Waze to calculate proper ETA timing through intersections.
| |
| | the rationale behind these rules.}}
| |
| | |
| == {{@|Regional and state local wiki pages}} ==
| |
| | |
| {{USA Navbox|state=expanded}}
| |
| | |
| <!-- Interim guidance in NY until the feature goes live to production has been only add WZ SLs if they are anticipated to persist more than a year, otherwise add the regular SL, and the WZ SL as a note in a UR with the keyword "mph WZ" in the text.
| |
| Once it goes live I'd support adding WZ SLs which are expected to last at least 3 months.-->
| |
