Carriles

Inicio

Quienes Somos

Como Editar

Estados de Venezuela

Foro

Intro

Nombres de Vías

Tipos de Vías

Estacionamientos

Glorietas, Rampas y Retornos

Peajes

La guía de carriles es una nueva característica de la aplicación Waze que muestra al usuario exactamente qué carriles deben usar para hacer su próximo movimiento. Esta característica aumenta la confianza de Wazer al brindar tranquilidad en los cruces, tanto típicos como inusuales. Los datos de guía de carril se agregan a través del Editor de Mapas Waze (WME) . Cuando se selecciona un solo segmento en el WME, una pestaña adicional llamada Carriles está disponible en el panel izquierdo. La pestaña Carriles permite que los editores de mapas le digan a Waze qué carril mostrar al conductor para que lo guíe en la aplicación móvil.

Hay algunas consideraciones importantes con respecto a la orientación de carriles en Waze:

• La guía de carril no afecta el enrutamiento , es simplemente una característica visual.
• La guía de carril no afecta las instrucciones de audio , con la excepción de las instrucciones de giro en U resultantes de la heurística para intersecciones en caminos divididos .
• La guía de carril solo se mostrará cuando se proporcione una instrucción de navegación. Si la mejor continuación es en línea recta, no se mostrará la orientación del carril, a menos que haya un anulación de instrucción de giro

A partir del 28 de mayo de 2020, la pestaña Carriles solo es visible en WME para los editores de rango 3 y la guía de carriles en la aplicación solo es visible para los beta testers y una pequeña porción de los usuarios de la aplicación de producción.

A partir del 30 de mayo de 2020, la función de mapeo de carriles de WME y la función de guía de carriles de la aplicación móvil aún están en desarrollo. Consulte esta guía con frecuencia para obtener actualizaciones de las características y la orientación.

Guía de mapeo

¿Qué cuenta como un carril?

P: ¿Cuántos carriles debe asignar al final de un segmento? ¿Qué cuenta como un carril?
R: mapee cualquier carril que logre un ancho completo y consistente ANTES del giro en sí. Para un carril de salida de la autopista, esto significa un carril de ancho completo ANTES del punto divisor entre un carril de carretera y una rampa de entrada. Si alguien que viaja en el carril derecho puede continuar en línea recta sin cambiar de carril, entonces asigne esto como un carril recto / giro.
Considere cómo se ve el camino para un conductor: haga que el número de carriles en la pantalla de guía de carril se ajuste a lo que verá el conductor.

Salidas de autopista y otras rampas

Ejemplo 1: No es un carril separado El carril de salida no alcanza el ancho completo hasta el punto divisor entre el carril y la rampa de entrada; mapearlo como parte de la línea recta más salida a la derecha.

Example 2: Ejemplo 2: No es un carril separado El carril de salida no alcanza el ancho completo hasta el punto divisor entre el carril y la rampa de entrada; mapearlo como parte de la línea recta más salida a la derecha


Ejemplo 3: Carril separado Cuando el carril de salida alcanza el ancho completo antes del punto de división, mapearlo como un carril separado y salida a la derecha

HOV y otros carriles restringidos

Las restricciones HOV (llamado VAO en nuestro país, vehículos de alta ocupación) o restricciones de otro tipo de vehículos a veces solo pueden aplicarse a una parte de la carretera. Solo incluya estos carriles restringidos en la guía de carriles si están disponibles para los usuarios en el segmento en cuestión. Les dejamos unos ejemplos en donde los carriles deben mapearse y donde no

• 

  Los carriles HOV que están en el mismo segmento (no separados físicamente) deben incluirse en los carriles.

• 

  Se deben incluir autobuses, bicicletas u otros carriles restringidos. En este caso, se permiten giros a la derecha desde el carril del autobús, por lo que se muestra como un carril de giro a la derecha.

• 

  En el caso de los canales exclusivos para autobuses que tienen un separador en la vía, este carril NO debe mapearse para no confundir a los conductores

• 

  El carril HOV es claramente visible para todo el tráfico, y sería considerado por la mayoría de los conductores como un carril, debe incluirse en el conteo de carriles en los segmentos que terminan en la salida.

Cuando mapear carriles

En general, los carriles se deben mapear donde hay más de un carril y solo un subconjunto de los carriles está disponible para giros. Además, los carriles se deben mapear en lugares potencialmente confusos donde la orientación de los carriles puede mejorar significativamente la seguridad y la experiencia del conductor.

Cuando el conductor necesita elegir el carril correcto

Cada vez que hay dos o más carriles y se da una instrucción en el nodo. En el ejemplo a continuación, la calle que corre de este a oeste tiene solo dos carriles, pero solo uno de esos carriles puede girar hacia el sur hacia la calle lateral.

Para aclarar qué camino tomar

Hasta ahora, Waze no podía mostrarle al conductor la diferencia entre giros leves, 90 ° y bruscos. Sin carriles, las intersecciones con múltiples giros a la derecha o múltiples a la izquierda podrían ser confusos para los conductores. La guía de carril puede aclarar esta confusión al mostrarle a los conductores si deben tomar, por ejemplo, la curva leve o la curva cerrada.

Esta situación es generalmente el único lugar donde es útil agregar carriles, donde solo hay un carril en la dirección de viaje relevante.

• 

  Ejemplo 1

• 

  Ejemplo 2

When the driver needs reinforcement or reassurance for safety

For this freeway off-ramp onto a one-way roadway, reinforce “no left turn”; either lane is fine.

There are some cases where lanes should be added to reassure drivers that they need not switch lanes, or that they may not turn from the lane they are in. In the example below, both lanes of the highway off-ramp must turn right — drivers have no choice. Lane guidance should be added to reassure drivers in the left lane that they need not change lanes and to reinforce the prohibition on the left turn to reduce the chance of them making a wrong-way turn.

When not to map lanes

When drivers have no choice

Suburban local streets typically don't have multiple lanes, and don't need lane guidance.

Generally, don’t add lanes when there is only one lane, or at a node where no instruction is to be given. An exception to this general rule is at confusing intersections and interchanges where the driver needs reassurance that a lane change will not be necessary before the next turn or exit maneuver, or reinforcement that what might look like a valid turn is not allowed (see the reinforcement and reassurance example above).

Merges and new lanes

Waze does not offer lane guidance for a reduction in the number of lanes.

Lane guidance is not appropriate for freeway lane reductions that do not occur near an interchange

How Waze selects 'Waze Selected' lane arrows

Waze Selected lane arrows are displayed for us both in the edit dialog (to the left of the checkboxes for each outbound segment) and in the Lanes pane (once changes are applied).Plantilla:Collapsible section top Expand for more information...Plantilla:Collapsible section content The determination is mostly simple and mostly based on angles. Consider there is a pizza pie on the map. Cutting the pizza pie into 8 slices, outbound segments in the top slice (i.e., turn angles from 0° up to 22.5° either way) might show straight, slight left, or slight right depending on context; the top-left and top-right slice (i.e., turn angles from 22.5° to 67.5° either way) will show slight left or slight right arrows; the left slice and right slice (between 67.5° and 112.5°) will have regular turn left or turn right arrows; and the bottom 3 slices (between 112.5° and 180°) will have sharp left/sharp right arrows. Capische? Mamma mia. Regarding the top slice, when there is only one outbound segment within the <22.5° slice, that segment will get the “straight” arrows. However, if multiple segments exist within this slice, some form of the “best continuation” analysis is used to determine which one gets the straight arrow, and other arrows in that slice get slight left or slight right arrows. If there is no “best continuation”, then the segment that is closer to 0° gets the straight arrow, and the other one(s)]] Plantilla:Collapsible section bottom

When to override lane arrows

See How Waze selects lane arrows for information on the default turn arrows.

Always review the lane arrows displayed in the Lanes pane carefully once you have applied your edits. Use override when it makes sense to do so, and leave the “Waze selected” setting in place otherwise. Do what makes sense to the person in the driver’s seat—choose the arrow which is going to make the most sense to the driver based on what they are going to have to do (continue straight, U turn, slight right, etc.) and what they are going to see as they approach the intersection or interchange where they need to make the maneuver.

This does not necessarily mean that the lane arrows should be forced to match the instruction—for example, there are times when a "keep left" instruction is best paired with "straight" arrows, or when a "turn right" instruction is paired with a slight right arrow. The lane arrows should be set according to how a driver would perceive the lane configuration, but the audio guidance should reflect the action to be taken.

When you change the arrow associated with one outgoing segment, check the remaining segments. In most situations, no two outgoing segments should use the same arrow.

When more than one outbound segment have the same 'Waze selected' arrow

Change one or more of them in a way that makes sense.

Where segment geometry doesn’t match reality

This happens in some locations because Waze road segment width does not match the real life road width. This can result in turn angles on the map which are somewhat different from the true turn angle. Lane arrow override may be necessary.

Where the Waze selected arrow doesn't match reality

Even in areas with very high quality maps, the Waze arrow selection mechanism can create arrow configurations which are confusing to the driver. This is particularly likely at nodes where there are multiple outbound segments essentially straight ahead (within a couple dozen degrees either way) from the inbound segment. These potentially-confusing generated arrows are most often found at ramp splits, wayfinders, and forks in the road, discussed in the section immediately below.

However, these situations occur in other places as well. For example, in situations where a main road veers off in one direction, and a side road continues straight ahead, the Waze selected arrows will sometimes give straight-ahead arrows to the continuation of the main road, and a “slight turn” arrow to the straight-ahead side road. This does not make sense from a driver’s perspective. In such cases, use lane angle overrides to achieve the desired result.

In this example, the continuing road veers left, while the side road exits straight ahead. Both street level and overhead imagery clearly shows the driver's perspective and the need for adjustments.

Waze selected arrows do not match reality.	Use lane angle overrides to create reality.

Ramp splits, wayfinders, and forks in the road

Sometimes the Waze selected lane arrows are the best choice and sometimes they are not. Look at both overhead and street views to consider what makes the most sense from the driver’s perspective. Given the processes by which Waze selects the “Waze selected” selection, sometimes the “Waze selected” straight-ahead arrow does not match well with the actual geometry of a junction.

Generally, only one outbound segment (if any) should have the “straight” arrow. If both outbound segments at a split or wayfinder take you down an equally-straight or equally-not straight path (whether immediately or foreseeably ahead), then neither should use the straight arrow. If one of the outbound segments leads to a straighter path than the other, however, then that one should have the straight arrow. If this is already happening, great. If not, use lane override to make it happen (and to ensure that the other path doesn’t keep it).

Adding lanes to the map

Before adding lane information, check both aerial and street view to make sure how many lanes there are on the segment at the node(s) where you are about to add lanes. See What counts as a lane? for more.

Plantilla:As of the lanes tab shows when a segment is selected at zoom level 4 (500 ft) or closer. If you don’t see the tab, try zooming and panning until it shows. The node you are editing must also be in the window.

Adding lanes to a segment

1. Select the segment to which you would like to add lanes.

2. In the left pane, click the Lanes tab.

The lanes tab appears in the left pane

3. For two-way segments, ensure you are editing the correct end of the segment. The “B” end (for A-to-B traffic) will show first, followed by the “A” end (for B-to-A traffic). The text at the top of each ‘end’ will describe the directionality of the lanes below.

For two-way segments, there is a section for each direction of lanes

4. Click "Add lane guidance".

For two-way segments, there is a section for each direction of lanes

5. Enter the number of lanes (NOT the number of possible directions). Use the number of lanes that connect to the next segment, even if there are a different number of lanes at some other point on the segment. See the What counts as a lane? section above for more information.

Count the numbers of lanes at the end of the segment.

6. Use the checkboxes to assign the available lanes for each outbound movement. Confirm using street-level imagery, where available. Note that the same lane may be used for more than one movement (e.g., the right lane may be used for both continuing and right-turning traffic).

Each lane is dedicated to a specific movement.

The right lane is shared for continuing and turning traffic.

7. Click Apply, then save your changes when you are ready. Changes will go live in the app after the next map tile update.

Mousing-over the turn arrow in the lanes panel will highlight that turn arrow on the map.

Editing existing lanes

Editing existing Lane Guidance for a segment is done similarly to adding the lanes for the first time:
1. Select the segment.
2. In the left pane, click the Lanes tab.

3. Click "Edit lane guidance" to bring up the Lane Guidance editing console.

Click 'Edit lane guidance'

Lane errors

If lane data is incomplete, or has been corrupted due to edits on connected segments, then an error alert symbol will appear on the affected segment and on the Lanes tab when the segment is selected.

Overriding a turn angle

Turn angle override controls

In some cases, the displayed turn angle may need to be adjusted. Rather than adjusting the geometry of the road segments, an override function is available in the Lanes tab.

1. Select the segment.
2. In the left pane, click the Lanes tab.
3. Click “Edit lane guidance”.
4. Click the given turn angle icon under the TURNS header to open the Override turn angle menu.
5. Select a new turn angle, or the ‘Waze selected’ angle.
   

Junction Boxes

Lane information can be added to segments which are part of a Junction Box just as they can be added to any other segment. In order for lane guidance to work, all turn arrows on the segments underlying a Junction Box must be green (unrestricted) if they are on a route allowed by the overlaid Junction Box. Use the Junction Box itself to restrict any necessary routes.

If a junction box uses a turn instruction override to override the Waze-selected turn instructions along one of the junction box routes, then the underlying lane data may not be displayed in the app.

Lanes on divided roadways

At intersections where one or both roads are divided, lanes cannot always be added directly.

Many such intersections can be classified as either “H” intersections (where only one road is divided) or “#” intersections (where both roads are divided).

On the divided roadway approaches to an “H” intersection, lanes can be added directly to the segments.

For some “#” intersections, and on the undivided roadway approaches to some “H” intersections, Waze can combine lane guidance information from more than one segment into a single set of lanes that includes both left and right turns, as the driver expects. This will only be possible if all of these conditions are met:

1. Both left and right turns are possible at the intersection;
2. The two portions of the divided roadway are essentially parallel to each other;
3. The two intersecting roads are more or less perpendicular to each other;
4. The median segment in question is 50 m or shorter; and
5. The number of lanes entering the intersection is equal to the total number of lanes exiting the intersection (total number of lanes exiting intersection = number of lanes on the median segment + number of right-turn only lanes on the entry segment—in other words, no new lanes are added in the median).

If these conditions are met, then follow the guidance in the next section to add lane information.

The purpose of the heuristics is to combine left turn, straight, and right turn arrows into a single lane set. At intersections where either left turns or right turns are disallowed, lanes can be added directly, and heuristics are not needed—in other words, there is no need to add “straight only” lane information. In the example below, right-turning traffic will get the full set of lanes from the entry segment; adding lanes to the median segment would serve no purpose.

One side effect of the H/# heuristics is that in many cases the server will identify 'turn left, then turn left' movements across a H/# intersection (when they are not prohibited by the U-turn prevention algorithm) as a U-turn, and display the U-turn lane guidance arrow in the app. In addition to the visual display of the U-turn arrow, the app's voice turn-by-turn instructions will vocalize the movement as a u-turn.

Mapping lanes on divided roadways

Hash intersections

Entry and Median Segments (for each direction of travel)

First, make sure that the intersection and the turn you are mapping for meet the guidelines above. Handle one direction of travel at a time.

For each direction of travel, lanes must be mapped on two segments: the “entry segment” (immediately before the median) and the “median segment” (within the median). See the adjacent figure.

1. On the entry segment, include the total number of lanes entering the intersection.
   1. Any lane that can be used to either turn left or continue straight should be mapped as a continuing straight lane.
   2. Any right turn lanes should be mapped as usual.
2. On the median segment, include the total number of lanes which actually exist in the median. The number of lanes on the median segment should equal the number of lanes that can continue straight from the entry segment.
   

Entry segment:	Median segment:

The heuristic in the routing server will combine these two sets of lanes together and provide a single set for drivers making either left or right turns. Unfortunately, there is no way to visualize the result in WME.

Lanes resulting from heuristics:

H Intersections

The same heuristic applies to the undivided road side of an H junction. No heuristic is necessary for the divided road side.

Undivided road side:	Divided road side:

The median segments of # and H junctions are a rare instance where, on occasion, it is proper to add “1 lane” to a segment. This will be necessary any time there are multiple lanes on the entry segment but only one lane remaining on the median segment (because any other lane was right turn only).

Checking your work

There are a few things you can do to double-check your work on divided-roadway intersections that need to be mapped with heuristics.

1. The total number of lanes on the entry segment should equal the total number of lanes at the intersection:
   • total lanes (intersection) = total lanes (entry)
2. The total number of lanes on the median segment should equal the difference between the total number of lanes on the entry segment and the number of right-turn only lanes on the entry segment:
   • total lanes (median) = total lanes (entry) – right turn only lanes (entry)
3. The number of straight-ahead lanes on the entry segment (i.e., the number of boxes checked for the straight-ahead movement) should equal the total number of lanes on the median segment:
   • straight-ahead lanes (entry) = total lanes (median)

If these conditions are not met, the heuristic method may not function as expected, and it is best to leave lanes off for the time being.