Non-drivable roads: Difference between revisions View history

(Marked this version for translation)
mNo edit summary
Line 6: Line 6:
Non-drivable roads are roads on which you cannot drive, or are not allowed to drive on. Many foot paths and bicycle paths are physical good enough to drive, but should not be taking into routing as a part to cross by car, motorcycle or another Waze vehicle type. As Waze is intended for drivers, we rather not map them. However, some of the non-drivables do serve a function:
Non-drivable roads are roads on which you cannot drive, or are not allowed to drive on. Many foot paths and bicycle paths are physical good enough to drive, but should not be taking into routing as a part to cross by car, motorcycle or another Waze vehicle type. As Waze is intended for drivers, we rather not map them. However, some of the non-drivables do serve a function:
* To help visual orientation
* To help visual orientation
* To calculate walking times to parking lots (not yet functional?)
* To calculate walking times to parking lots
* To calculate the most nearby stop point for destinations that are not directly reached by car.
* To calculate the most nearby stop point for destinations that are not directly reached by car.
<!--T:12-->
<!--Use of pedestrian paths requires special care and caution, because cyclists and pedestrians who use Waze near drivable roads can harm routing for drivers! By Wazing at speeds different from nearby traffic, they can create false traffic indications and even influence Waze's records of average road and turn speeds. Therefore, editors should only map roads that increase usefulness to Wazers driving motor vehicles, and any road that only encourages or benefits non-driving Wazers should not be mapped.-->


==Railroads==  <!--T:13-->
==Railroads==  <!--T:13-->
Line 37: Line 34:


<!--T:16-->
<!--T:16-->
[[Road types|Road type]] <i>Runway/Taxiway</i> is used for airport runways and private airstrips. The <i>Runway/Taxiway</i> type is for display only and must never connect to drivable road segments.
The <i>Runway/Taxiway</i> type is used for airport runways and private airstrips. This [[Road types|road type]] is for display only and must never connect to drivable road segments.


<!--T:17-->
<!--T:17-->
Line 55: Line 52:
<!--T:19-->
<!--T:19-->
Walking Trails (WTs) are used for segments on which you are not able to drive, but that have or lead to a destination. Waze will stop routing at the start of the WT, where the Wazer should ideally park and finish on foot. The walking time is calculated in the routing, although there are still some flaws reported for this function. Usage:
Walking Trails (WTs) are used for segments on which you are not able to drive, but that have or lead to a destination. Waze will stop routing at the start of the WT, where the Wazer should ideally park and finish on foot. The walking time is calculated in the routing, although there are still some flaws reported for this function. Usage:
* In pedestrian areas, where houses or other <i>destinations</i> are located
* In pedestrian areas, where houses or other destinations are located
* Pedestrian connections with parking lots <!-- Should be PB, but bug Sept 2019 says it doesn't work. Is this still so?-->
* All other non-drivable paths that have or lead to destinations and need to be taken into account in routing for the served vehicle types
<!-- * The segment is relatively long and separated of the normal road (so this can be used as a reference / landmark)
shouldn't this a PB then? Or is it necessary for GPS?-->


<!--T:20-->
<!--T:20-->
Always connect Walking Trails. If no junction node exists, connecting can also be done using a [[Nodes|phantom node]]. <!-- works as of March? 2020-->  
Always connect Walking Trails. If no junction node exists, connecting can also be done using a [[Nodes|phantom node]]. <!-- works as of March 2020-->  


<!--T:21-->
<!--T:21-->
Line 81: Line 76:
* visual orientation (if navigation and/or the map is unclear without the pedestrian path)
* visual orientation (if navigation and/or the map is unclear without the pedestrian path)
* public transport by bus
* public transport by bus
* It could lead users to their parked car, allowing Waze to estimate better walking times to [[Parking Lot Place|parking lot places]]</i>.  
* It could lead users to their parked car, allowing Waze to estimate better walking times to [[Parking Lot Place|parking lot places]].  


<!--T:24-->
<!--T:24-->

Revision as of 16:01, 20 June 2020

We are currently updating the pages to include all regionally different guidelines. If you find inconsistencies, please refer to the English page. Thank you!
Other languages:
Non-drivable roads

Non-drivable roads are roads on which you cannot drive, or are not allowed to drive on. Many foot paths and bicycle paths are physical good enough to drive, but should not be taking into routing as a part to cross by car, motorcycle or another Waze vehicle type. As Waze is intended for drivers, we rather not map them. However, some of the non-drivables do serve a function:

  • To help visual orientation
  • To calculate walking times to parking lots
  • To calculate the most nearby stop point for destinations that are not directly reached by car.

Railroads

 |-|-|-|-|-|-|-|-|-| Railroad |-|-|-|-|-|-|-|-|-| 
Used for railway lines, metros tracks and tramways. They are mainly used for visual orientation or to prevent contamination of traffic data when close to other roads.

  • It is not neccessary to map all railroad, tram, or metro tracks. One rail road track suffices for multiple tracks next to each other.
  • Tracks that are embedded in a road surface or a median strip should not be mapped.
  • At crossings with drivable roads on the same elevation level, the railroad may be connected to the road with a junction node. Leave the turns disabled.
  • Add a Railroad Crossing (RCC) at junctions with drivable segments
Attributes
Street City Lock Elevation
*
3
as is

Note: * A street name can be added if it helps drivers to orient themselves. Better avoid general names like "Railroad" to prevent cluttering the screen

Runway/Taxiway

 ─═─═─═─═─ Runway/Taxiway ─═─═─═─═─ 

The Runway/Taxiway type is used for airport runways and private airstrips. This road type is for display only and must never connect to drivable road segments.

Attributes
Street City Lock Elevation
5
ground

Walking trail

 |   |   |   |   | Walking Trail |   |   |   |   | 

Walking Trails (WTs) are used for segments on which you are not able to drive, but that have or lead to a destination. Waze will stop routing at the start of the WT, where the Wazer should ideally park and finish on foot. The walking time is calculated in the routing, although there are still some flaws reported for this function. Usage:

  • In pedestrian areas, where houses or other destinations are located
  • All other non-drivable paths that have or lead to destinations and need to be taken into account in routing for the served vehicle types

Always connect Walking Trails. If no junction node exists, connecting can also be done using a phantom node.

Attributes
Street City Lock
if available
1 *

*Lock 3 to protect complex routing

Pedestrian Boardwalk

 |  |  |  | Pedestrian Boardwalk |  |  |  | 

Pedestrian Boardwalk (PBs) are used for segments on which you are not able to drive, and that are not connected to a possible destination. They show almost the same in WME as Walking trails (WT), the color is slightly more grey (see the picture #Stairway). Use for:

  • visual orientation (if navigation and/or the map is unclear without the pedestrian path)
  • public transport by bus
  • It could lead users to their parked car, allowing Waze to estimate better walking times to parking lot places.

This road type is not used to add house numbers, if the non-drivable road has destinations use road type walking trail instead. PBs don't need to be connected to a drivable road; If you do, use an existing node or a Phantom node.

Attributes
Usage Street City House# Lock
Pedestrian area
1
Public transport by bus
French: Bus
Dutch: Busbaan
German: Busspur
3

Note: Despite the fact that it has become impossible to set junction arrows for PB's it's still possible to have an 'Isolated segment' error when you save. This error can be ignored.

Handling existing unnecessary Pedestrian Boardwalks

As Waze is meant for drivers, most segments without destination are obsolete to the Waze map. However, with the expanding features added, they might fulfill an important function in the future. It is already used to calculate the walking time to find back your car. In addition, it is a nice way for starting editors. It is not needed to strictly keep or remove them at this moment.

Stairway

SW-Stairway, PB-Pedestrian Boardwalk, WT-Walking Trail as shown in WME

 | | | | | Stairway | | | | | 

Stairways (SWs) have the same characteristics as the Pedestrian Boardwalk (PB), but show different in WME. In the app, it shows similar to PB. The reason to use them at this moment is for editors to quickly distinguish them. Like PBs, stairways don't need connection to a drivable road and you do not need to make a junction node. If you connect, use an existing node or a Phantom node.

If the stairs are used to reach a destination, use the road type walking trail instead.

Attributes
Street City House# Lock
if available
1

Note: Despite the fact that it is impossible to set junction arrows for Stairways, it's still possible to have an 'Isolated segment' error when you save. This error can be ignored.

When to map what?

In short:

  • Walking trail: For non-drivable, with possible destinations
  • Pedestrian Boardwalk: For non-drivable, without destinations. Also used for Public Transport by Bus
  • Stairway: Can be used to indicate stairs without routing functionality in WME
  • Railroad: railway lines, metro tracks and tramways, see above
  • Runway/Taxiway - designated for airplane taxiing lanes on airports, see above

Routing difference between WT and PB

Note: there are signs routing is still not always working as intended.



  Main Page | Index