Revision as of 21:51, 30 January 2018 by Voludu2 (talk | contribs) (→What traffic data is stored: Added Tonestertm's illustration, updated the text to match.)
 |
This new page is currently undergoing modifications. The information presented should be considered a draft, not yet ready for use. This content is open to changes from anyone during construction. If you would like to make changes or have questions, please post a message in this forum. |
Traffic data
Along with every routable segment, Waze stores data about how long it takes to cross that segment and transition (straight, right, left, exit, keep) to every other segment that is junctioned to it. This information is used by the routing engine to figure out the fastest way to get to a destination. If a segment is deleted, then the information about the time it takes to cross it or enter it from another segment is also deleted,
This article explains what traffic data is stored and what happens to it when we change the map.
What traffic data is stored
- Waze stores Forward (A to B) and Reverse (B to A) segment cross times for each time slice, for each possible exit from the segment. So if segment 100 is junctioned to segments 201, 202, and 203 at its B junction node, there will be 3 cross times in the A->B direction - for 100->201, 100->202, and 100->203.
- If the segment has a restricted lane (Bus, Express, HOV, etc) , the same type of information is stored for that "extra" lane. So if segment 100 also has a left HOV lane, then there will be 3 more cross times in the same direction - for 100HOV -> 201, 100HOV->202, 100HOV->203
Where does this information come from
- When a new segment is created, initial segment cross times are created based on a default average speed for the road type and a transition time to each segment it is junctioned to. These values will be updated as soon as waze decides traffic has used the segment.
- Segment Cross Times are frequently updated by analyzing the traffic that has travelled on each segment at each time slice of the week, and that real-life segment cross times are averaged to come up with the stored values. There are a lot of details we do not know about how traffic data is analyzed, and how the traffic calculations take into account loss of cell service, wazers stopping on the side of the road or entering or leaving a segment in the middle. LiveMap shows us 48 times per day (every hour and half hour), and we don't know whether that has anything to do with the number of time slices Waze uses in its calculations.
Glossary
Stored Traffic Data
- Time slice
- A specific day of week and portion of a day. A time slice might cover an hour or half hour of the day, or it might cover a different length of time.
- Segment cross time
- The time it takes a wazer to enter the the segment, cross it, and exit the segment i one of the possible exit directions. This time includes time, on average, spent "waiting for the light to change", "waiting to make a turn", or "waiting at the 4-way stop". For a 2-way segment connected to a 4-way intersection at each end, there are 4 segment cross times in the A->B direction (straight, left, right, and u-turn) and 4 more in the B->A direction. For segments marked as an HOV/Express segment (a segment which has an HOV or express lane on the right or left), there is an additional full set of cross times associated with the Express/HOV lane.
Calculated Traffic Data
- Segment cross speed
- segment cross time divided by length.
- Traversal Time
- A calculated "base" time to cross a segment in the A->B or B->A direction, not including transition times to cross from one segment to one of the other segments it is junctioned to. Might be used to calculate new segment cross times when an existing segment is cut into two new segments.
- Transition Time
- A calculated "wait" time to transition from one segment to another, not counting the Traversal time. Might be used to calculate new segment cross times when an existing segment is cut into two new segments.
What information we can see
Scripts like route speeds can retrieve segment cross times for an hour or half hour, any day of the week, along any of the routes the routing server gave it. These scripts can calcuate speeds based on these cross times.
When is traffic data lost?
- When a segment is deleted, all traffic data involving that segment is lost.
- When a segment is permanently disconnected from another segment at a junction, all segment cross times involving transitions between those two segments will eventually be lost.
- If no traffic is assigned to a segment or a direction on a segment then the old traffic data for that direction will be retained for a week or two. After that, it will be lost.
What happens to traffic data when you make changes to the roads
- When you delete a segment (let's call it segment 100)
- its cross times to other segments are deleted.
- all cross times from other segments to that segment are lost; waze does not remember "turning left from segment 101 is a long wait" it remembers "the cross time from segment 101 to segment 100 is 4 minutes at 5:30 PM on Monday". If you delete segment 100, Waze no longer has any use for that information.
- When you delete a segment and replace it with a newly-drawn segment, waze has to start from scratch collecting data on segment cross times.
- When you shift the position of a junction without disconnecting anything, changing the lengths of several segments
- The cross times are not changed OR The cross times are changed in a proportional way to account for the fact that the junction has moved
- Over time, the stored traffic data will change to bring segment cross times back into line with reality.
- When you cut a segment (let's call it segment 100) into 2 shorter segments without changing anything else at the 2 original junctions
- Two new segments are created with brand-new segment IDs (let's call them 201 and 202)
- The segment and the segment ID (100) from the segment you cut is removed.
- A junction node is created where the two new segments are joined.
- The segment cross times of the original segment are used to calculate new cross times for the new segments, including cross times connecting the two new segments.
- Over time, the stored traffic data will change to adjust the new transition times in line with reality.
- When you disconnect all segments from a junction node and save:
- The junction node is deleted.
- The cross times passing through that junction node are lost.
- When you move segments from one junction node to another junction node
- All segment cross times which passed through the first junction node are lost, because they were associated with the two connected segment IDs.
- New segment cross times onnecting the same segments through the new junction node are created.
- If you begin with two segments, 101 and 102 disconnected them, and reconnected them through a new junction node, the transition times between 101 and 102 will be lost. They will be replaced by new default values.
- Over time, transition times between the two segments will be adjusted to reflect the new traffic data.
- Traffic data corresponding to a restricted (red) transition arrow between segment 200 and 201 will still be collected as long as traffic can be assigned to a route from segment 200 to 201 (see below)
- Traffic data corresponding to the "wrong direction" on a one-way segment will not be collected if the traffic data is assigned to other nearby segments. If no traffic is asigned to a segment direction, the old traffic data will be retained for a week or two.
- If a 2-way segment is improperly divided by drawing a new one-way segment parallel to the old segment, and the old segment is made one-way, then the stored "wrong way" traffic data on the old segment will be retained for a period of a week or two. New traffic data in that direction will be collected on the new one-way segment.
Unanswered Questions
What happens when
- Drag one junction node with two segments on top of another junction node with another 2 segments. Are the s1->s2 and s3->s4 transition times retained at the new junction node?
- Create 1 segment from 2 by deleting the junction joining them.
- Cross speed?
- Transition times at the nodes on either end of the new segment?
- Transition time between the 2 segments that have been joined to create the new segment?
- disconnect a segment from a junction
- and reconnect it before saving.
- and save it disconnected, but reconnect it and save again before the next tile update
- and save it disconnected through the next tile update, then reconnect directly after tile update.
- for a few days, weeks, or months -- as a way to close a road during construction.
- and then reconnect it to the same junction (nothing else having changed at that junction in the meantime)
- Connect a segment to a junction
- a former "dead-end" node of an existing segment
- convert a bow tie junction to a "H" junction by the following method
- disconnect segment 1 from the bow tie junction
- connect segment 1 to the cross segment to create a new junction
- disconnect segment 2 from the bow tie junction
- connect segment 2 to the new junction.
- convert a bow tie junction to a "H" junction by the following method
- bridge segment 1 to segment 2
- move the joined segment to the new junction location on the cross segment
- reduce the elevation to ground and use the "junction" icon to create the new junction.