Traffic data: Revision history View history

30 January 2020

• curprev 15:0315:03, 30 January 2020‎ Voludu2 talk contribs‎ m 15,828 bytes +4‎ →‎What traffic data is stored: , and Tag: Visual edit
• curprev 14:5914:59, 30 January 2020‎ HillsSnackBar talk contribs‎ m 15,824 bytes −4‎ Typo correction - removing an unnecessary "the" Tag: Visual edit

21 February 2019

• curprev 00:5100:51, 21 February 2019‎ Kentsmith9 talk contribs‎ 15,828 bytes +12‎ Minor working adjustments

7 February 2019

• curprev 17:4217:42, 7 February 2019‎ Voludu2 talk contribs‎ m 15,816 bytes 0‎ Voludu2 moved page User:Voludu2/Traffic data to Traffic data: Ready for publication Tag: national guidance change
• curprev 17:4217:42, 7 February 2019‎ Voludu2 talk contribs‎ 15,816 bytes −191‎ Ready for publication
• curprev 14:4814:48, 7 February 2019‎ Voludu2 talk contribs‎ m 16,007 bytes +5‎ →‎When is traffic data lost? Tag: Visual edit

31 January 2019

• curprev 20:5120:51, 31 January 2019‎ Voludu2 talk contribs‎ 16,002 bytes +554‎ →‎What happens to traffic data when you make changes to the roads: what happens when you merge two segments. Tag: Visual edit

25 January 2019

• curprev 19:1119:11, 25 January 2019‎ Voludu2 talk contribs‎ 15,448 bytes +33‎ →‎Summary: How to preserve traffic data while editing: be specific about segment IDs and junction boxes
• curprev 19:0819:08, 25 January 2019‎ Voludu2 talk contribs‎ 15,415 bytes +47‎ →‎Junction boxes and traffic data: junction box <-> segment ides

24 January 2019

• curprev 19:2019:20, 24 January 2019‎ Voludu2 talk contribs‎ 15,368 bytes +130‎ →‎What traffic data is stored: short segments
• curprev 19:1819:18, 24 January 2019‎ Voludu2 talk contribs‎ 15,238 bytes +104‎ →‎Summary: How to preserve traffic data while editing: too-short segments
• curprev 18:5618:56, 24 January 2019‎ Voludu2 talk contribs‎ 15,134 bytes +32‎ →‎Why Waze stores traffic data: link to road types for plr
• curprev 18:5418:54, 24 January 2019‎ Voludu2 talk contribs‎ m 15,102 bytes −118‎ →‎What traffic data is stored
• curprev 18:5218:52, 24 January 2019‎ Voludu2 talk contribs‎ m 15,220 bytes −32‎ →‎Why Waze stores traffic data
• curprev 18:5118:51, 24 January 2019‎ Voludu2 talk contribs‎ 15,252 bytes +152‎ mention junction box, link to junction box and routing server
• curprev 18:3518:35, 24 January 2019‎ Voludu2 talk contribs‎ 15,100 bytes +25‎ →‎Junction boxes and traffic data: link to junction box article
• curprev 17:4717:47, 24 January 2019‎ Voludu2 talk contribs‎ 15,075 bytes +233‎ →‎What traffic data is stored: stored even for PLRs (for which it is not used)
• curprev 17:4417:44, 24 January 2019‎ Voludu2 talk contribs‎ 14,842 bytes −34‎ →‎Junction Boxes Tag: Visual edit
• curprev 17:1817:18, 24 January 2019‎ Voludu2 talk contribs‎ m 14,876 bytes −15‎ →‎Traffic data
• curprev 17:1717:17, 24 January 2019‎ Voludu2 talk contribs‎ 14,891 bytes −6‎ →‎Summary: How to preserve traffic data while editing: entry and exit
• curprev 17:1517:15, 24 January 2019‎ Voludu2 talk contribs‎ 14,897 bytes +150‎ →‎When is traffic data lost?: segment changes to junction box entry/exit segments
• curprev 17:1217:12, 24 January 2019‎ Voludu2 talk contribs‎ 14,747 bytes +158‎ →‎Summary: How to preserve traffic data while editing: junction box. But is this correct information? Tag: Visual edit
• curprev 17:1017:10, 24 January 2019‎ Voludu2 talk contribs‎ 14,589 bytes +858‎ →‎Junction Boxes: junction box is like a new node on some of the same old segments
• curprev 16:4616:46, 24 January 2019‎ Voludu2 talk contribs‎ 13,731 bytes +144‎ →‎Traffic data: junction box
• curprev 16:4316:43, 24 January 2019‎ Voludu2 talk contribs‎ m 13,587 bytes +1‎ →‎Traffic data Tag: Visual edit
• curprev 16:4016:40, 24 January 2019‎ Voludu2 talk contribs‎ m 13,586 bytes +1‎ →‎What happens to traffic data when you make changes to the roads Tag: Visual edit
• curprev 16:3816:38, 24 January 2019‎ Voludu2 talk contribs‎ 13,585 bytes −1,345‎ →‎Unanswered Questions: Removed unanswered questions Tag: Visual edit
• curprev 16:3616:36, 24 January 2019‎ Voludu2 talk contribs‎ m 14,930 bytes 0‎ →‎Why Waze stores traffic data

23 October 2018

• curprev 11:3111:31, 23 October 2018‎ Voludu2 talk contribs‎ 14,930 bytes −53‎ →‎What happens to traffic data when you make changes to the roads: segment node at both ends - moved to definitions Tag: Visual edit
• curprev 11:2911:29, 23 October 2018‎ Voludu2 talk contribs‎ 14,983 bytes +808‎ →‎Stored or Calculated Traffic Data: Define segments and nodes
• curprev 11:1911:19, 23 October 2018‎ Voludu2 talk contribs‎ 14,175 bytes +14‎ →‎What happens to traffic data when you make changes to the roads: change the length of segment - speed is retained. cross times change Tag: Visual edit

19 October 2018

• curprev 12:5512:55, 19 October 2018‎ Voludu2 talk contribs‎ 14,161 bytes −8‎ →‎What happens to traffic data when you make changes to the roads
• curprev 12:5512:55, 19 October 2018‎ Voludu2 talk contribs‎ m 14,169 bytes +33‎ →‎What happens to traffic data when you make changes to the roads: indentation.
• curprev 12:5312:53, 19 October 2018‎ Voludu2 talk contribs‎ 14,136 bytes +492‎ →‎What happens to traffic data when you make changes to the roads: Correct what happens to the junction and end nodes when you move the segment end Tag: Visual edit

18 October 2018

• curprev 17:1017:10, 18 October 2018‎ Voludu2 talk contribs‎ 13,644 bytes −135‎ →‎What happens when: eliminated 2 already-answered questions Tag: Visual edit
• curprev 17:0717:07, 18 October 2018‎ Voludu2 talk contribs‎ 13,779 bytes +115‎ →‎What happens to traffic data when you make changes to the roads

16 October 2018

• curprev 19:5119:51, 16 October 2018‎ Voludu2 talk contribs‎ 13,664 bytes +334‎ →‎Why Waze stores traffic data: exception: PLR in NA Tag: Visual edit
• curprev 18:3318:33, 16 October 2018‎ Voludu2 talk contribs‎ 13,330 bytes +905‎ Simple Summary added
• curprev 16:0516:05, 16 October 2018‎ Voludu2 talk contribs‎ 12,425 bytes +8‎ →‎Where does this information come from: generalize. traffic data vs cross times or cross speeds.
• curprev 16:0216:02, 16 October 2018‎ Voludu2 talk contribs‎ 12,417 bytes +68‎ junction node. Tag: Visual edit: Switched
• curprev 16:0016:00, 16 October 2018‎ Voludu2 talk contribs‎ 12,349 bytes −83‎ →‎What happens when Tag: Visual edit
• curprev 15:5915:59, 16 October 2018‎ Voludu2 talk contribs‎ 12,432 bytes +141‎ →‎What happens to traffic data when you make changes to the roads: traffic data Tag: Visual edit
• curprev 14:1614:16, 16 October 2018‎ Voludu2 talk contribs‎ 12,291 bytes +92‎ →‎When is traffic data lost?: when a node is lost.
• curprev 14:1314:13, 16 October 2018‎ Voludu2 talk contribs‎ 12,199 bytes +201‎ →‎What traffic data is stored: nodes are primary.
• curprev 14:0814:08, 16 October 2018‎ Voludu2 talk contribs‎ 11,998 bytes −15‎ →‎Why Waze stores traffic data: caption change
• curprev 13:4113:41, 16 October 2018‎ Voludu2 talk contribs‎ 12,013 bytes −30‎ →‎Calculated Traffic Data: Waze doesn't tell us stored vs calcualted
• curprev 13:4013:40, 16 October 2018‎ Voludu2 talk contribs‎ 12,043 bytes +14‎ →‎Stored Traffic Data: Waze doesn't say which is which.
• curprev 13:4013:40, 16 October 2018‎ Voludu2 talk contribs‎ m 12,029 bytes 0‎ →‎Traffic data: move image to correct section
• curprev 13:3913:39, 16 October 2018‎ Voludu2 talk contribs‎ 12,029 bytes +599‎ Waze doesn't tell us if it is storing segment cross speeds or segment cross times.
• curprev 13:1413:14, 16 October 2018‎ Voludu2 talk contribs‎ 11,430 bytes +232‎ Make clear that we don't know exactly which algorithm Waze uses, let alone what proprietary modifications Waze may or may not have made.