Carpool lanes, High-occupancy Vehicle (HOV) lanes, and Transit lanes are road lanes reserved for vehicles meeting special requirements, either carrying at least a specific number of passengers more than the driver, or being a specific vehicle type. The number of required passengers in the vehicle can vary depending on the specific road.
Although currently Waze does not support the requirements of routing over these types of lanes, there are plans to add support for them in the future.
Supporting these lanes is a priority for Waze, and they are aware of the problems caused by such lanes.
- 1 Configuration and setting restrictions
- 2 Lessons Learned
- 3 Pointers for a complete solution
Configuration and setting restrictions
|These guidelines have been updated As of July 2015[update] to prepare for the upcoming HOV features. The old method was to map these lanes as Parking Lot Roads. This new method below should be used when mapping new lanes. There is no rush to redo existing lanes to make them compliant; do so only if you are working on them anyway, or are doing a general refresh in the area.|
As an interim measure, these lanes should be added to the map as separate roads, with the road type set the same as the non-HOV lanes. However only the entrance ramps to these lanes should be set with the appropriate partial segment restrictions. The actual lanes themselves should not have any restrictions set on them, except for reversible lanes, or other restrictions which are in effect at all times on multi-use lanes as discussed below. This means that if you are not currently in one of these lanes the routing will avoid it, but if you choose to get into the lane, the routing will work correctly. Being that only the entrance to the lane is restricted, once you are already in the lane there will be no penalty for staying there, and you will be routed the fastest and most appropriate way to your destination. The caveat will be for multi-use lanes which will have restrictions set to force everyone who does not meet the lanes use criteria (at this time that will be everyone, since the client and routing server can only handle routes for private vehicles) out of the lanes before the enforcement period begins.
|As of July 2015[update] the client and routing server are still unable to differentiate different vehicle types. Therefore all vehicles using Waze are treated as Private Vehicles, and any HOV restrictions will be applied to all vehicles. (This is the reason why the restrictions should ONLY be set for the on ramps, and not the entire length of the lanes on the segments themselves.)|
This should only be applied to dedicated lanes that have exit and entry points.
Any time you are setting a road to allow HOV - 2, it must also be set to allow HOV - 3.
In the USA motorcycles are allowed to use HOV lanes, therefore when setting partial restrictions to only allow HOV - 2 (HOV -3), Motorcycles should also be allowed (unchecked). Some jurisdictions also Taxis and Buses to use the HOV lanes. These should be set accordingly in those jurisdictions.
There are special configurations needed for reversible, and multi-use lanes which change use criteria or direction at different times of the day.
Lanes which only have the HOV restrictions in place for certain hours, and open to regular vehicles during other hours, need to have the restrictions on the entrance ramps set to only allow the specific vehicles for that road during the enforcement times, AND that same restriction must be set to only be in effect during the enforcement time.
The enforcement time should be expanded to start 15 minutes earlier, to account for drivers who experience traffic along their route prior, and prevent them from accidentally being routed onto the HOV lanes after the enforcement period begins.
These lanes will also require a similar restriction set on ALL the exit ramps, also with the enforcement period expanded to begin 15 minutes early. This will ensure that vehicles which do not meet the roads HOV criteria, but have been routed into these lanes prior to the enforcement period, will be routed out of these lanes before the enforcement begins. It is imperative that every exit ramp has these restrictions in place, otherwise instead of these vehicles being routed out of the lanes when the enforcement begins, they will all be funneled and routed to the one exit ramp which does not have these restrictions.
If when these lanes are open to the public (when the HOV restrictions are not in effect), they are still restricted to certain vehicle types (i.e. No Trucks), then that should be set as a separate restriction on the actual lanes to be in effect at all times.
These lanes should be set with separate time based partial restrictions restricting travel in each direction for the appropriate hours.
If the hours are adjacent to each other, meaning that there is no buffer time between the two travel direction of the lanes, then we will have to add a buffer time into to Waze for safety. In that case expand the restriction to start 15 minutes earlier so there is at least a 15 minute window when there travel is restricted in both directions between the open periods.
Some jurisdictions have adopted the position that any vehicle which has legally entered one of these lanes may proceed to their intended exit regardless of when the lane officially closes. For these lanes, the restrictions must be placed on each of the entrace ramps leaving the lane itself and the exit ramps unrestricted. To do otherwise, results in drivers being instructed to exit the lane for no obvious reason.
A multi-use lane which is open to the all vehicles during off-peak hours has to be set as a separate restriction from each of the enforcement periods.
Each of those restrictions must be set to the criteria restricted to only HOV - 2, HOV- 3, Motorcycles or Buses on weekdays during the hours of 6-10 am, and 3-8 pm.
The following concepts were developed after reviewing the HOV/HOT lane restrictions in the Houston area.
Keep each restriction simple
It appears that the Texas Department of Transportation (TxDOT) regulations tend to describe them in terms of when they are available rather than the restrictions that WME uses. When inverting the TxDOT regulations to restrictions approach the task one restriction at a time. If the lane is closed on weekends, that's a restriction. If it is closed to certain classes of vehicles then that's another restriction. Try to avoid having restrictions that specify multiple attributes of days, times, and vehicle types, as they'll be very hard for the next editor to verify. Instead, try to use restrictions that are constrained by only one attribute (days, times, or types).
For example, given an HOV lane that is open from 0500 to 1100 on weekdays to HOV-2 and Motorcycles. The restrictions can be described like this:
- An all day restriction for all vehicle types on Saturday and Sunday.
- An all day, all week, restriction blocking all vehicle types except HOV-2 and Motorcycles.
- We're using an all week restriction here both to keep it simple and to prevent a dependency on the first restriction.
- A weekday restriction for all vehicle types from 0000 to 0459.
- A weekday restriction for all vehicle types from 1100 to 2359.
Avoid use of restrictions spanning midnight
A timed restriction whose stop time is earlier in the day than its start time will begin on one day and continue to the stop time on the next day. One of the common problem with this type of restriction is that it is applied to the weekdays rather than all days. For example, 1300 to 0459 Monday through Friday. While the restriction obviously appeared correct to many editors, waze interpreted it as
Viewed this way, its easy to see that starting the restriction on Monday results in 0000 through 0459 Monday being left unrestricted while that time is closed on the other days.
The recommendation is to avoid using this feature as the next editor may not be as familiar with its use. Instead, create both an early (0000 to 0459) and a late (1300 to 2359) restriction.
Provide specific comments on each restriction
HOV lanes will usually be locked at a high rank to prevent accidental damage to the map. As a result, lower ranked editors are unable to examine the restrictions. For lower ranked editors to assist with resolving HOV-related User Reports those editors must install URO+ as URO+ adds a dialog that appears when the editor mouses over a restricted segment. This dialog includes the optional comment of each restristion.
Part-time tolls or HOV/HOT lanes
One of the interesting problems encountered when a single lane is used as both a HOV (restricted by vehicle types and times) lane and as a HOT (part-time toll) lane is that the toll status is an attribute of the road. It can't be enabled, or disable, at arbitrary times. Even if that were to work, enabling toll on a segment meant to be used by HOV traffic would cause routing issues for HOV-2 vehicle with toll avoidance enabled. What is necessary is to split the road for a short distance so that one of the parallel roads can be restricted per the HOV rules while the other road is restricted per the toll rules.
To avoid keep left/right instructions when the driver reaches the "split" road, the segments must overlap at their common junctions as shown in this deconstruction.
Pointers for a complete solution
A complete solution needs to consider the following factors:
- The driver would need to tell the Waze client app how many passengers are present in the car, or what vehicle type they are in for that trip. Waze would only offer routes over carpool lanes when they meet the criteria to be eligible
- In some places, Electric or Plug-in Hybrid vehicles may also use HOV lanes, so this local situation must be known and the driver should be asked if the vehicle is allowed in HOV lanes for reasons other than number of passengers.
- As car pool lanes are often adjacent to normal roads, GPS tracking is not always sufficient to differentiate between the two. For accurate road speeds Waze needs to assume you are using the car pool lane when you have passengers (and/or based on your speed). However if the lanes are separated even by a few meters, the server can usually tell the difference and the speed to the correct lanes, even if the client displays you as being on the wrong lane.
- HOV lanes are being merged with Toll lanes (HOT lanes) and the user needs to be able to select if they want to allow toll roads. The map needs the ability to track multiple lane restrictions (HOV and/or Toll) for the same road rather than defining the road as either an HOV or a Toll lane.