(more tweaks incl. motorcycle reference) |
No edit summary |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 3: | Line 3: | ||
=== Segment speed tracking === | === Segment speed tracking === | ||
As part of the HOV/Express Lane process, Waze computes a maximum of two separate road speeds per segment during the user drive evaluation process<ref name="moto">With one exception: a separate set of speed data is kept for the '''motorcycle''' vehicle type.</ref>: the "entire segment" speed and up to one single-lane speed. While the Waze editor interface allows the addition of multiple single-lane restrictions (e.g., HOV left lane, regular traffic center lane, and Bus right lane), the user drive evaluation process does not support three different speeds on a single segment. Therefore, do not add more than one single-lane restriction on any segment. | As part of the HOV/Express Lane process, Waze computes a maximum of two separate road speeds per segment during the user drive evaluation process<ref name="moto">With one exception: a separate set of [[Routing server#Problems with average road speeds|speed data]] is kept for the '''motorcycle''' vehicle type.</ref>: the "entire segment" speed and up to one single-lane speed. While the Waze editor interface allows the addition of multiple single-lane restrictions (e.g., HOV left lane, regular traffic center lane, and Bus right lane), the user drive evaluation process does not support three different speeds on a single segment. Therefore, do not add more than one single-lane restriction on any segment. | ||
Speed measurements are normally gathered per lane, not per vehicle or restriction type<ref name="moto" />—for example, an HOT or Express road segment allowing both toll free and tolled traffic in the same lane gathers only one set of average speed data (instead of keeping separate times for private vehicle, taxi, electric vehicle, etc.). This makes sense, as vehicles in the lane are traveling together as a single pack. In other words, the complexity of restrictions in a single lane does not matter—as long as only one single-lane restriction set is used, speed data will be collected properly. | Speed measurements are normally gathered per lane, not per vehicle or restriction type<ref name="moto" />—for example, an HOT or Express road segment allowing both toll free and tolled traffic in the same lane gathers only one set of average speed data (instead of keeping separate times for private vehicle, taxi, electric vehicle, etc.). This makes sense, as vehicles in the lane are traveling together as a single pack. In other words, the complexity of restrictions in a single lane does not matter—as long as only one single-lane restriction set is used, speed data will be collected properly. | ||
{{reflist}} | |||
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ||
To be included in a new section in [[Routing server#Problems with average road speeds]] possibly, or on a new [[Segment data]] page: | |||
Speed data | Speed data is normally collected with a maximum of two speeds for any road segment: one for the entire segment, and another if there is a single-lane (left/right/center) restriction. However, because motorcycles can get through traffic more easily and split lanes in some jurisdictions, a separate set of motorcycle speeds is kept separately, making motorcycles the only known vehicle type to have its own speed history data. Motorcycle speeds are kept alongside the normal one or two sets of speed data for all other vehicle types (private, taxi, electric vehicle, etc.). The routing server uses the appropriate stored speed data and current conditions for calculating the best routes and estimated time of arrival based on the user's selected vehicle type. | ||
Latest revision as of 17:16, 9 March 2018
Propose to add a new section to the HOV wazeopedia
Segment speed tracking
As part of the HOV/Express Lane process, Waze computes a maximum of two separate road speeds per segment during the user drive evaluation process[1]: the "entire segment" speed and up to one single-lane speed. While the Waze editor interface allows the addition of multiple single-lane restrictions (e.g., HOV left lane, regular traffic center lane, and Bus right lane), the user drive evaluation process does not support three different speeds on a single segment. Therefore, do not add more than one single-lane restriction on any segment.
Speed measurements are normally gathered per lane, not per vehicle or restriction type[1]—for example, an HOT or Express road segment allowing both toll free and tolled traffic in the same lane gathers only one set of average speed data (instead of keeping separate times for private vehicle, taxi, electric vehicle, etc.). This makes sense, as vehicles in the lane are traveling together as a single pack. In other words, the complexity of restrictions in a single lane does not matter—as long as only one single-lane restriction set is used, speed data will be collected properly.
- ↑ 1.0 1.1 With one exception: a separate set of speed data is kept for the motorcycle vehicle type.
To be included in a new section in Routing server#Problems with average road speeds possibly, or on a new Segment data page:
Speed data is normally collected with a maximum of two speeds for any road segment: one for the entire segment, and another if there is a single-lane (left/right/center) restriction. However, because motorcycles can get through traffic more easily and split lanes in some jurisdictions, a separate set of motorcycle speeds is kept separately, making motorcycles the only known vehicle type to have its own speed history data. Motorcycle speeds are kept alongside the normal one or two sets of speed data for all other vehicle types (private, taxi, electric vehicle, etc.). The routing server uses the appropriate stored speed data and current conditions for calculating the best routes and estimated time of arrival based on the user's selected vehicle type.