So, how do the DETAILS work? Need MUCH more detail!
Hey all,
Maybe it's because I'm an Engineer, but I never trust anything I don't understand the inner workings of, which has made it difficult to trust Waze's recommendations for which routes to choose in order to avoid traffic.
I have been searching for DETAILED information regarding the client, and its behaviors, but found it very lacking.
Does anyone know if information like the following is documented anywhere?
1.) Does the client use only real time data, or does it also use historic data to predict current traffic conditions for roads that are not as frequently traveled?
2.) How is real time traffic data accumulated and reported to the client so it can choose how to avoid it? What algorithms are used? How often is data sampled? Once a second? Once a minute? What are the benefits and potential pitfalls of this method.
3.) If data is trended and forecast where real time data does not exist, what algorithms are used, what data is included, what data is excluded? and how does it all make its way from the reporting clients to the Waze trending database and then out to the navigating client? What are the benefits and shortcomings here?
4.) How are reports of traffic assessed? Standstill is easier to understand, but what about moderate and heavy? Do they have an approximate speed value associated with them? Are they factored into the traffic algorithms for other clients to navigate, or are they just FYI, leaving actual vehicle movement data to take care of this?
5.) How is data reported from the client to Waze? Is it real time? Is it based on periodic polling? Does it report once at the completion of every length of road between two points? Does it wait until the end of the drive and report all at once?
6.) What happens if you lose data connection? As far as:
a) Navigation is concerned
b) Reporting is Concerned
7.) If there is no data connection and the client or phone is shut off, does the client keep a local cache and report data when it is turned back on?
8.) How does the client/database determine the difference between a client sitting still intentionally and a client stuck in traffic? There has to be some sort of rule set to determine this, as if it reported any still client as stuck in traffic the entire system would be chaotic useless. Presumably, once the parking space button is pressed, no more traffic data is reported, until more movement is reported. Presumably, also, if a client is turned on, no traffic data is reported, until it sees movement, but are there other rules as well? We users need to know these things so we can be conscientious and not pollute the system with fake results.
This is just a start, I can think of many more questions, none of which I found in the wiki manual, or in any of the instructional videos.
Only when I understand the answers to questions like these do I feel comfortable enough to trust wave to direct me a different route than I normally drive to avoid traffic, and know what its shortcomings are so I can choose to ignore it when I know better.
After all, the devil's in the details!
Maybe it's because I'm an Engineer, but I never trust anything I don't understand the inner workings of, which has made it difficult to trust Waze's recommendations for which routes to choose in order to avoid traffic.
I have been searching for DETAILED information regarding the client, and its behaviors, but found it very lacking.
Does anyone know if information like the following is documented anywhere?
1.) Does the client use only real time data, or does it also use historic data to predict current traffic conditions for roads that are not as frequently traveled?
2.) How is real time traffic data accumulated and reported to the client so it can choose how to avoid it? What algorithms are used? How often is data sampled? Once a second? Once a minute? What are the benefits and potential pitfalls of this method.
3.) If data is trended and forecast where real time data does not exist, what algorithms are used, what data is included, what data is excluded? and how does it all make its way from the reporting clients to the Waze trending database and then out to the navigating client? What are the benefits and shortcomings here?
4.) How are reports of traffic assessed? Standstill is easier to understand, but what about moderate and heavy? Do they have an approximate speed value associated with them? Are they factored into the traffic algorithms for other clients to navigate, or are they just FYI, leaving actual vehicle movement data to take care of this?
5.) How is data reported from the client to Waze? Is it real time? Is it based on periodic polling? Does it report once at the completion of every length of road between two points? Does it wait until the end of the drive and report all at once?
6.) What happens if you lose data connection? As far as:
a) Navigation is concerned
b) Reporting is Concerned
7.) If there is no data connection and the client or phone is shut off, does the client keep a local cache and report data when it is turned back on?
8.) How does the client/database determine the difference between a client sitting still intentionally and a client stuck in traffic? There has to be some sort of rule set to determine this, as if it reported any still client as stuck in traffic the entire system would be chaotic useless. Presumably, once the parking space button is pressed, no more traffic data is reported, until more movement is reported. Presumably, also, if a client is turned on, no traffic data is reported, until it sees movement, but are there other rules as well? We users need to know these things so we can be conscientious and not pollute the system with fake results.
This is just a start, I can think of many more questions, none of which I found in the wiki manual, or in any of the instructional videos.
Only when I understand the answers to questions like these do I feel comfortable enough to trust wave to direct me a different route than I normally drive to avoid traffic, and know what its shortcomings are so I can choose to ignore it when I know better.
After all, the devil's in the details!
Re: So, how do the DETAILS work? Need MUCH more detail!