User:CBenson/ParkingLot View history

No edit summary
Line 4: Line 4:


*it allows Waze to provide door-to-door directions within the lot;
*it allows Waze to provide door-to-door directions within the lot;
*it allows the Waze client to get off the main road, avoiding erroneous traffic reports.
*it allows the Waze to recognize that the client is off the main road, avoiding erroneous traffic reports.
*it prevents the Waze client from routing thru-traffic along the parking lot segments.
*using the special type prevents Waze from routing traffic through the parking lot.


For information pertaining to using the Parking Lot Place please see: [[Places/Parking lot]].
Parking lot segments are not related to the .[[Places/Parking lot|Parking Lot Place type]].


The Parking Lot Road type exists to allow the mapping of parking lots, while discouraging the routing server from using them for through navigation. Waze applies a [[Routing penalties|transition penalty]] when transitioning from a Parking Lot Road to another road type. This penalty decreases the chance that Waze will route through a parking lot as a shortcut but allows better navigation in and out of a parking lot. It is advised not to mix road types within a parking lot to avoid triggering the transition penalty unnecessarily.
The Parking Lot Road type exists to allow the mapping of parking lots, while discouraging the routing server from using them for through navigation. Waze applies a [[Routing penalties|transition penalty]] for leaving a Parking Lot Road segment to enter another road type. This penalty decreases the chance that Waze will route through a parking lot as a shortcut but allows better navigation in and out of a parking lot. It is advised not to mix road types within a parking lot to avoid triggering the transition penalty unnecessarily.


==== Shopping Centers ====
==== Shopping Centers ====
Line 17: Line 17:
*Main entrances from the roads outside the parking lot
*Main entrances from the roads outside the parking lot
*Lanes that run along storefronts
*Lanes that run along storefronts
*Lanes that run along main roads outside the parking area (to prevent cars in the parking area from snapping to the main roads and sending incorrect speed information)
*Lanes at the edge of the lot which run alongside public roads (prevents Wazers in the parking area from "snapping" to the public road, and then sending incorrect speed information it)
*Primary lanes that serve to get people from one area of the lot to another
*Primary travel lanes that serve to get people from one area of the lot to another


Remember, the goals here are usability and simplicity. When in doubt, imagine yourself in a car in the lot at various points, and ask yourself what the most efficient way would be to get to a store at the other end of the lot, or to exit the lot and get back on a main road, with as few convolutions as possible. The lanes that are used the most in this thought experiment should be mapped, with the rest being omitted. You can turn on the GPS points layer ([[Shortcut key]] Shift-G) to see where traffic has been most recently to help determine what might be the best section to map.<br/>[[File:ParkingLotRoad ShoppingCenter.png|714px]]
Remember, the goals here are usability and simplicity. When in doubt, imagine yourself in a car in the lot at various points, and ask yourself what the most efficient way would be to get to a store at the other end of the lot, or to exit the lot and get back on a main road, with as few convolutions as possible. The lanes that are used the most in this thought experiment should be mapped, with the rest being omitted. You can turn on the GPS points layer ([[Shortcut key]] Shift-G) to see where traffic is concentrated to get a sense of what needs mapping.<br/>[[File:ParkingLotRoad ShoppingCenter.png|714px]]


In particular, '''do not''' map every single lane, and especially not every single parking space (it has been done!). This serves no purpose but to clutter the map, confuse directions, and put an unnecessary burden on both the client and server hardware. Remember usability and simplicity are #1. Your editing time and expertise can be better used elsewhere in the map.
In particular, '''do not''' map every single lane, and especially not every single parking space (it has been done!). This serves no purpose but to clutter the map, confuse directions, and put an unnecessary burden on both the client and server hardware. Remember usability and simplicity are #1. Your editing time and expertise can be better used elsewhere in the map.
Line 26: Line 26:
==== Small Parking Lots ====
==== Small Parking Lots ====


Parking lots that serve a small number of businesses should be minimal: enough to give the driver correct directions into and out of the lot, and navigate to a particular business. Very small lots with a single entrance/exit could even be represented by a single segment running diagonally across the parking area (lots with entrances on both sides) or a single, flattened curve (lots that only have entrances/exits along a single road, such as for strip malls).
Parking lots that serve a small number of businesses should be minimal: enough to give the driver correct directions into and out of the lot, and navigate to a particular business. Very small lots with one entrance and one exit could even be represented by a single segment running through the parking area (either a diagonal across the lot if it connects to roads on each side, or a single, flattened curve for strip mall-style lots with entrances and exit along the same road).


Beware of Parking Lot exits that have a restricted turn (typically no left turn allowed across a median). Due to the way that Waze routing works in regards to penalties, if there is only one way out of a Parking Lot Waze may route you to take that restricted left turn. In these cases it would be better to provide another path out of the lot via an unrestricted turn.
Beware of Parking Lot exits that have a restricted turn (typically no left turn allowed across a median). Due to the way that Waze routing works in regards to penalties, if there is only one way out of a Parking Lot Waze may route you to take that restricted left turn. In these cases it would be better to provide another path out of the lot via an unrestricted turn.
Line 34: Line 34:
Because these lots can be narrow and congested, with one-way sections, the simplest way to represent them may be as just a one-way drive-through loop. ''Caveat: because both ends of a segment cannot connect to the same junction, if the lot has only one entrance/exit, it is necessary to build the [[Junction Style Guide#Loops|loop using three segments]].''
Because these lots can be narrow and congested, with one-way sections, the simplest way to represent them may be as just a one-way drive-through loop. ''Caveat: because both ends of a segment cannot connect to the same junction, if the lot has only one entrance/exit, it is necessary to build the [[Junction Style Guide#Loops|loop using three segments]].''


==== Parking Lots Separated By A Street ====
==== Two parking lots connected to the same street ====


Be aware that when two parking lots are directly connected there is no routing penalty for routing through one from the other. Thus, there is no routing penalty to transition from one parking lot to another when the two parking lots are separated by a street and both share a junction node on the street. To be sure that Waze will apply the transition penalty when routing through one parking lot from another, the two parking lots must be isolated from the each other such that passing from one to the other requires driving over a road segment of a type that is not parking lot road or private road.
Bad routing can occur when two parking lots connect to the same street. This can happen, for example, where two lots face each other. If you connect both parking lots to the public road using ''the same junction'' as the connection point for both, Waze will treat them as one parking lot, and could route the driver from public roads through one parking lot to reach a destination in the other parking lot. Waze is designed to avoid such routes, but in this configuration, Waze does not apply the expected penalty - because crossing through the junction from one parking lot segment to the other is not considered a transition, even though there is also a public road running through the junction. This may be most easily understood by looking at the example image below.
 
To be sure that Waze will apply the transition penalty when routing through one parking lot from another, the two parking lots must be isolated from the each other such that passing from one to the other requires driving over a standard road segment (not a parking lot road or [[Private road|private road]]). You should map a very short "stub" segment (5m/17ft) of the same type as the public road. This segment will run from teh junction to the entry/exit segment of one of the lots. With this configuration, exiting the parking lot will have a consistent penalty, whether the exit leads to the public road or to another parking lot.
 
Parking lots do not have to be across the street from each other. In a strip mall, if the exit segment of one business is joined to the entrance segment of the next business, the same problem can occur.
 
If it is not legal to cross from one lot to the other, the stub segment is not necessary, as you can put in [[turn restrictions]] to prevent any sort of routing between the lots.
 
===== Illustration =====


For example, in the configuration shown below if routing from the west parking lot, there is no transition penalty to route through the gas station parking lot on the east side of the street if routing east on Riva Rd.  Conversely, if routing to the west parking lot from Riva Rd. there is no transition penalty to use the gas station.   
For example, in the configuration shown below if routing from the west parking lot, there is no transition penalty to route through the gas station parking lot on the east side of the street if routing east on Riva Rd.  Conversely, if routing to the west parking lot from Riva Rd. there is no transition penalty to use the gas station.   

Revision as of 23:33, 25 October 2015

Parking Lots

Mapping a parking lot road serves three purposes:

  • it allows Waze to provide door-to-door directions within the lot;
  • it allows the Waze to recognize that the client is off the main road, avoiding erroneous traffic reports.
  • using the special type prevents Waze from routing traffic through the parking lot.

Parking lot segments are not related to the .Parking Lot Place type.

The Parking Lot Road type exists to allow the mapping of parking lots, while discouraging the routing server from using them for through navigation. Waze applies a transition penalty for leaving a Parking Lot Road segment to enter another road type. This penalty decreases the chance that Waze will route through a parking lot as a shortcut but allows better navigation in and out of a parking lot. It is advised not to mix road types within a parking lot to avoid triggering the transition penalty unnecessarily.

Shopping Centers

When mapping a large parking lot (e.g., at a shopping center) consider mapping only the following:

  • Main entrances from the roads outside the parking lot
  • Lanes that run along storefronts
  • Lanes at the edge of the lot which run alongside public roads (prevents Wazers in the parking area from "snapping" to the public road, and then sending incorrect speed information it)
  • Primary travel lanes that serve to get people from one area of the lot to another

Remember, the goals here are usability and simplicity. When in doubt, imagine yourself in a car in the lot at various points, and ask yourself what the most efficient way would be to get to a store at the other end of the lot, or to exit the lot and get back on a main road, with as few convolutions as possible. The lanes that are used the most in this thought experiment should be mapped, with the rest being omitted. You can turn on the GPS points layer (Shortcut key Shift-G) to see where traffic is concentrated to get a sense of what needs mapping.

In particular, do not map every single lane, and especially not every single parking space (it has been done!). This serves no purpose but to clutter the map, confuse directions, and put an unnecessary burden on both the client and server hardware. Remember usability and simplicity are #1. Your editing time and expertise can be better used elsewhere in the map.

Small Parking Lots

Parking lots that serve a small number of businesses should be minimal: enough to give the driver correct directions into and out of the lot, and navigate to a particular business. Very small lots with one entrance and one exit could even be represented by a single segment running through the parking area (either a diagonal across the lot if it connects to roads on each side, or a single, flattened curve for strip mall-style lots with entrances and exit along the same road).

Beware of Parking Lot exits that have a restricted turn (typically no left turn allowed across a median). Due to the way that Waze routing works in regards to penalties, if there is only one way out of a Parking Lot Waze may route you to take that restricted left turn. In these cases it would be better to provide another path out of the lot via an unrestricted turn.

Drive-Through Lots

Because these lots can be narrow and congested, with one-way sections, the simplest way to represent them may be as just a one-way drive-through loop. Caveat: because both ends of a segment cannot connect to the same junction, if the lot has only one entrance/exit, it is necessary to build the loop using three segments.

Two parking lots connected to the same street

Bad routing can occur when two parking lots connect to the same street. This can happen, for example, where two lots face each other. If you connect both parking lots to the public road using the same junction as the connection point for both, Waze will treat them as one parking lot, and could route the driver from public roads through one parking lot to reach a destination in the other parking lot. Waze is designed to avoid such routes, but in this configuration, Waze does not apply the expected penalty - because crossing through the junction from one parking lot segment to the other is not considered a transition, even though there is also a public road running through the junction. This may be most easily understood by looking at the example image below.

To be sure that Waze will apply the transition penalty when routing through one parking lot from another, the two parking lots must be isolated from the each other such that passing from one to the other requires driving over a standard road segment (not a parking lot road or private road). You should map a very short "stub" segment (5m/17ft) of the same type as the public road. This segment will run from teh junction to the entry/exit segment of one of the lots. With this configuration, exiting the parking lot will have a consistent penalty, whether the exit leads to the public road or to another parking lot.

Parking lots do not have to be across the street from each other. In a strip mall, if the exit segment of one business is joined to the entrance segment of the next business, the same problem can occur.

If it is not legal to cross from one lot to the other, the stub segment is not necessary, as you can put in turn restrictions to prevent any sort of routing between the lots.

Illustration

For example, in the configuration shown below if routing from the west parking lot, there is no transition penalty to route through the gas station parking lot on the east side of the street if routing east on Riva Rd. Conversely, if routing to the west parking lot from Riva Rd. there is no transition penalty to use the gas station.


This potential problem arises when two parking lots on opposite sides of a street connect at the same junction node on the street.

If this configuration causes routing problems it can be solved by changing the road type of one (or both) of the parking lot roads that intersect with the street.

A five meter or longer stub of a different road type will accomplish the same result.

If the street is a divided highway, then the road type of the crossover segment may be changed (this may also allow U-turns at the crossover segment).