Difference between revisions of "Pedestrian path"

From Wazeopedia
(text copied from Road type#nNon-drivable roads)
 
(first updates and reorganizations)
Line 1: Line 1:
==  {{@|Non-drivable roads}} ==
+
Pedestrian paths (US English) or walking trails (default English) are a set of non-drivable road types with unique properties. It is possible to connect them to other roads using a virtual node rather than a real junction node. The virtual node does not cut the segment that it is connected to but modifies it. It doesn't store turn data, nor does it allow routing into a non-drivable road connected to it. Because of the presence of virtual nodes, it is not possible to convert segments between pedestrian path types and other road types. Therefore, they must be created as a category separate from other roads.
  
'''Your car should not be here!'''
+
Use of these types requires special care and caution. This is because the Waze app is intended only for drivers of motor vehicles, and Waze has no plans ever to support any other application.  In fact, 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 benefits non-driving Wazers should not be mapped. '''However, there are certain use cases for these paths, which are described under each section.
  
*{{As of|2015|4}} the Waze app is intended only for drivers of motor vehicles, and Waze has no plans ever to support any other application.  In fact, cyclists and pedestrians who use Waze near drivable roads can damage Waze's speed and traffic database! '''Editors should not map <u>any</u> road type for the sole purpose of encouraging non-driving Wazers.'''
+
Note: As this is guidance for the USA, this page uses US English "translated" names for these road types. The default international English interface in [[Waze Map Editor]] uses different terms for these, which are given in parentheses.
*It may be useful to map certain non-drivable roads as navigational references if they are '''visually obvious to drivers''', for example by showing where a turn lies in relation to a railroad crossing (use the Railroad type) or a major Rails-to-Trails right-of-way (use the Pedestrian Boardwalk type).
 
*If the GPS Points layer clearly shows frequent improper Wazing on a non-vehicle route near drivable roads, marking this route with a non-drivable road type can prevent damage to Waze's speed and traffic database.  Do not, however, use the Walking Trail type for this purpose.
 
*The Walking Trail road type, although listed as non-drivable, is fully routable and should only be used by experts in very limited cases.
 
*{{As of|2015|6}}, the non-drivable road types of Pedestrian Boardwalk, Stairway and Runway/Taxiway should '''not have any type of junction with a drivable road'''.  When crossing drivable roads, these non-drivable road types should be bridged across without a junction and set at a different elevation. ''Note:  this guidance is subject to change.''
 
* ''It is OK to junction drivable roads with the Railroad type.'' See specific details in the Railroad section later on this page.
 
*{{Red|Walking Trails, and other non-drivable road type which are visible in the app, can cause significant routing issues.}} If a walking trail (even when not connected to any other drivable segment) is closest to the latitude and longitude of the search result, the routing server will route you to the spot on the segment closest to that walking trail.<br/><br/>In the sketch below, if you assume the Place target is a latitude and longitude returned by a Google search result, you would think that the actual destination would be the parking lot segment because it is the closest reachable/connected segment to the target. But it won't be. The actual destination will be where the green spot is, because the closest segment to the latitude and longitude is the walking trail, and the closest Waze can route to the walking trail is to where the green spot is.
 
  
[[File:Walking trail dest.png|center|Walking trail dest.png]]
+
{{@|Routable pedestrian path}}
  
{{clear}}
+
{{Walking Trail|&nbsp;}}
  
 +
The routable pedestrian path (default English: walking trail) is the only type among the three pedestrian paths that has an effect on routing, and it is only the only type that snaps users to it. This''' type should never be used where effects on routing are not desired.'''
  
 +
Use routable pedestrian paths only with assistance from an expert in them. They should only be used in rare cases to improve routing to and from destinations located on them. Routable pedestrian paths may have strange side effects on nearby routing.  Never use this type type for ordinary hiking or cycling paths. Most hiking and cycling paths should not be on the map at all.
  
===  {{@|Emergency Vehicle and DOT Service Roads}} ===
+
Routable pedestrian paths can cause significant routing issues. If a routable pedestrian path is closest to the latitude and longitude of a destination, users will be routed to a junction of the trail with a drivable road, which can be far away from the destination they are hoping to reach.
  
[[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. 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}}
+
===  Applications ===
  
===  {{@|Walking Trails}} ===
+
In rare cases, connected routable paths can bring drivers to destinations where otherwise Waze might fail to offer the best route.  For example:
 
 
<!-- [[File:RoadPicN9.jpg|right|300px|RoadPicN9.jpg]] THIS FIGURE OF A PLEASANT LEAFY WALKING TRACK COMMENTED OUT UNTIL A MORE APPROPRIATE IMAGE CAN BE FOUND. --DwarfLord, June 6 2015 -->
 
 
 
{{mbox|type=caution|text=This section is new {{As of |2015|05|24|df=us|lc=yes}}.  For details, please
 
see the [http://www.waze.com/forum/viewtopic.php?f=276&t=98949 forum discussion].}}
 
 
 
Use Walking Trails only with assistance from an expert in Walking Trails. They should only be used in rare cases. Walking Trails may have strange side effects on nearby routing.  Never use the Walking Trail road type for ordinary hiking paths or bike paths. Most hiking and bicycling paths should not be on the map at all.
 
 
 
The WME lists the Walking Trail road type as non-drivable.  However, {{as of|2015|5|lc=yes}}, Walking Trails are fully routable and even support Waze House Numbers.  Waze treats them in some ways like "Dirt road / 4X4 Trail" but displays them differently.  Historically, editors have disconnected Walking Trails to make sure Waze doesn't route drivers over them.  This doesn't always work as desired. If a disconnected Walking Trail comes closer to a destination than any other road, Waze may route drivers to a location nearer to the Walking Trail than to the destination.  This problem can be severe for Walking Trails passing close to many destinations in a dense neighborhood.  '''Connected or not, the Walking Trail type should never be used where effects on local routing are not desired.'''
 
 
 
The name "Walking Trail" suggests that Waze wants to support pedestrians and cyclists.  However, {{as of|2015|4|lc=yes}}, Waze focuses on drivers of motor vehicles and has no plans to encourage or support any other application.  In fact, pedestrians and cyclists using the Waze app may damage Waze.  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.
 
 
 
Because of this effect, '''editors should not map Walking Trails, or any other road type, for the sole purpose of encouraging non-driving Wazers.'''  See the descriptions of other non-drivable road types for recommended applications of those types.
 
 
 
If the GPS Points layer shows clearly that pedestrians and cyclists already use Waze on a path or trail that lies parallel to a drivable road, then, {{as of|2015|5|lc=yes}}, the path may be mapped with a Pedestrian Boardwalk.  Doing so will limit the damage these Wazers would otherwise cause to the road's speed data.  Such paths should only be mapped once it is clear Wazers regularly use them.
 
 
 
====  {{@|Applications}} ====
 
 
 
In rare cases, connected Walking Trails can bring drivers to destinations where otherwise Waze might fail to offer the best route.  For example:
 
  
 
*A concert pavilion in an urban park accessed by a pedestrian path from a distant parking lot.
 
*A concert pavilion in an urban park accessed by a pedestrian path from a distant parking lot.
  
*A train station reachable from either side of the tracks but with no drivable road across them.
+
*A train station reachable from either side of the tracks but with no drivable road across them. ({{As of|2018-05}} {{Red|routable pedestrian paths do not provide routing optimized for this application}}).
  
 
*A destination addressed on a non-drivable footpath.
 
*A destination addressed on a non-drivable footpath.
  
A connected Walking Trail may be used to route drivers to such destinations. If the Walking Trail goes through from one drivable road to another, ensure that outgoing turn restrictions are red to disallow through routing via the Walking Trail.  Lock the Walking Trail as this is uncommon usage that may puzzle other editors.
+
A connected routable pedestrian path may be used to route drivers to such destinations. Lock the path as this is uncommon usage that may puzzle other editors.
  
Orientation or destination applications involving foot or bicycle paths that do not require routing, such as marking where an obvious bicycle path crosses a road or where a trailhead is located, should not use the Walking Trail type. Use Pedestrian Boardwalks, Stairways, or Point Places as appropriate.
+
Orientation or destination applications involving foot or bicycle paths that do not require routing, such as marking where an obvious bicycle path crosses a road or where a trailhead is located, should not use this type type. Use non-routable pedestrian paths, stairways or places as appropriate.
  
====  {{@|Naming}} ====
+
===  Creation ===
  
If destinations are addressed using House Numbers on a Walking Trail, it is essential that the Walking Trail's name and city fields be set accordingly so that routing to the addresses will work. For other routing situations, Walking Trails should be named to alert drivers that they must leave their car. For example, a Walking Trail connecting the two sides of a train station may be named "Station Access Footpath".
+
{{As of|2018-05}} virtual nodes do not work correctly with routable pedestrian paths. For desired routing these paths must be connected to junction nodes rather than virtual nodes. This may require cutting the drivable road segment with a normal street and deleting the street before creating the routable path.
{{clear}}
 
  
=== {{@|Pedestrian Boardwalks}} ===
+
If destinations are addressed using house numbers on a routable pedestrian path, it is essential that the path's name and city fields be set accordingly so that routing to the addresses will work.
{{Pedestrian Boardwalk|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;}}[[File:RoadPicN10.jpg|right|300px|RoadPicN10.jpg]] {{clear}}
+
== Non-routable pedestrian path ==
 +
{{Pedestrian Boardwalk|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;}}
 +
*It may be useful to map certain non-drivable roads as navigational references if they are '''visually obvious to drivers''', for example by showing where a turn or destination lies in relation to a
 +
*If the GPS Points layer clearly shows frequent improper Wazing on a non-vehicle route near drivable roads, marking this route with a non-drivable road type can prevent damage to Waze's speed and traffic database. Remember to use one of the two non-routable types for this purpose
  
===  {{@|Stairway}}  ===
+
==  {{@|Stairway}}  ==
 
{{Stairway|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;}}
 
{{Stairway|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;}}
[[File:RoadPicN11.jpg|right|300px|RoadPicN11.jpg]] {{clear}}
+
 
 +
Stairways appear and behave identically in the app. They appear at similar zoom levels to private roads and parking lot roads, and they have no effect on routing.

Revision as of 19:08, 11 May 2018

Pedestrian paths (US English) or walking trails (default English) are a set of non-drivable road types with unique properties. It is possible to connect them to other roads using a virtual node rather than a real junction node. The virtual node does not cut the segment that it is connected to but modifies it. It doesn't store turn data, nor does it allow routing into a non-drivable road connected to it. Because of the presence of virtual nodes, it is not possible to convert segments between pedestrian path types and other road types. Therefore, they must be created as a category separate from other roads.

Use of these types requires special care and caution. This is because the Waze app is intended only for drivers of motor vehicles, and Waze has no plans ever to support any other application. In fact, 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 benefits non-driving Wazers should not be mapped. However, there are certain use cases for these paths, which are described under each section.

Note: As this is guidance for the USA, this page uses US English "translated" names for these road types. The default international English interface in Waze Map Editor uses different terms for these, which are given in parentheses.

Routable pedestrian path link to this section

 |   |   |   |   |   |   |   |   |   | 

The routable pedestrian path (default English: walking trail) is the only type among the three pedestrian paths that has an effect on routing, and it is only the only type that snaps users to it. This type should never be used where effects on routing are not desired.

Use routable pedestrian paths only with assistance from an expert in them. They should only be used in rare cases to improve routing to and from destinations located on them. Routable pedestrian paths may have strange side effects on nearby routing. Never use this type type for ordinary hiking or cycling paths. Most hiking and cycling paths should not be on the map at all.

Routable pedestrian paths can cause significant routing issues. If a routable pedestrian path is closest to the latitude and longitude of a destination, users will be routed to a junction of the trail with a drivable road, which can be far away from the destination they are hoping to reach.

Applications

In rare cases, connected routable paths can bring drivers to destinations where otherwise Waze might fail to offer the best route. For example:

  • A concert pavilion in an urban park accessed by a pedestrian path from a distant parking lot.
  • A train station reachable from either side of the tracks but with no drivable road across them. (As of 2018-05 routable pedestrian paths do not provide routing optimized for this application).
  • A destination addressed on a non-drivable footpath.

A connected routable pedestrian path may be used to route drivers to such destinations. Lock the path as this is uncommon usage that may puzzle other editors.

Orientation or destination applications involving foot or bicycle paths that do not require routing, such as marking where an obvious bicycle path crosses a road or where a trailhead is located, should not use this type type. Use non-routable pedestrian paths, stairways or places as appropriate.

Creation

As of 2018-05 virtual nodes do not work correctly with routable pedestrian paths. For desired routing these paths must be connected to junction nodes rather than virtual nodes. This may require cutting the drivable road segment with a normal street and deleting the street before creating the routable path.

If destinations are addressed using house numbers on a routable pedestrian path, it is essential that the path's name and city fields be set accordingly so that routing to the addresses will work.

Non-routable pedestrian path

 |  |  |  |  |          |  |  |  |  | 

  • It may be useful to map certain non-drivable roads as navigational references if they are visually obvious to drivers, for example by showing where a turn or destination lies in relation to a
  • If the GPS Points layer clearly shows frequent improper Wazing on a non-vehicle route near drivable roads, marking this route with a non-drivable road type can prevent damage to Waze's speed and traffic database. Remember to use one of the two non-routable types for this purpose

Stairway link to this section

 | | | | |          | | | | | 

Stairways appear and behave identically in the app. They appear at similar zoom levels to private roads and parking lot roads, and they have no effect on routing.