dead reckoning (when neither data nor GPS available)
There are zero map apps that offer dead reckoning:
continue navigation when neither GPS nor data (mobile or wifi) are available. Useful also when insufficient GPS birds viewable.
* orientation (for fixed mounts)
Given availability of map data those are enough to continue navigation:
. in tunnels
. in parking structures
. in box canyons
This is especially beneficial for those who do not have (no longer have) aGPS [assisted GPS] features.
But dead reckoning will benefit even those with aGPS.
Pascal Six commented
The Bluetooth OBD dongle TomTom LINK 100 can real time stream the actual speed of the car, especially in tunnels, in traffic jams and at road intersections. Allianz France has incorporated that dongle, the TomTom LINK 100 SDK into its Conduite Connectée app. Waze could consider teaming with TomTom on that, at least on a pilot market. Why not ?
It would be already great if Waze was able to take tunnel traffic conditions into account, based on average speed to go through it? I have a long tunnel in my daily commute and the lack of information on the traffic status inside the tunnel often results in long queues that could be avoided.
Average speed between two known positions based on GPS data should not be a major deal?
giovanni pianigiani commented
Please don't link it to data availability. What I notice is that especially in long tunnels Waze believes that I am somewhere in the nearest village outside the tunnel, I presume by taking my location from the data network?
Christopher Grenness commented
4.0 is out (on iOS for a few months, apparently released for Android today however no update available on my phone), still no "tunnel mode"? This pretty important navigation feature was first requested back in 2010... I'm starting to loose my faith in Waze, having missed several exits in Stockholm's tunnels (first time there driving my own car) a few weeks back.
Please, Waze, replace your "tunnel panic mode" with a simple, decent "tunnel mode" where the app just stays on route/road with last known speed until gps signals are available again. How hard can it be? (I really don't know! :-) )
Having read all of your comments you, sir, are obviously EXTREMELY GENIUS.
I wouldn't be surprised if google has hired you.
3 years later CSR has GNSS chipsets with many of these features I hope will be available on SoC in upcoming android flagship phones.
MediaTek also has developed some great gnss chisets with similar features while csr sat on their collective Sirf hands.
I do hope to see dead reckoning implemented in software for those disinterested in flagship phones or unfavorable conditions
Yoshi Josh Portuondo-Dember commented
When I use TomTom on my iPhone it posts estimated location
Andrea Verocio commented
Someone mentioned using FM as a dead reckoning method. I think that would be awesome!
"So waze's only option would be to clamp the car to the street it is driving on and predict the position with the latest speed."
I totally agree. The algorithm I would use is if road elevation < ground level && gps lost then propagate the estimated position along the Waze route at the last known speed. When road elevation returns to ground level or above then freeze the position until gps returns.
Seems such a simple implementation to me for what would be a huge benefit. If there is an exit half along the tunnel you get no guidance. What use is that?
Etienne Durand commented
A company named Movea has a middleware solution that could provider you the solution to do that.
Safely Driven Quickly commented
The gpsritter comment is pure FUD (extrabogus)
Hi all. To give you some background on DR. The difficulty lays still in the Algorithms to correctly read out the sensors and convert it into a correct GPS data stream. The only and best option is to connect it to the car directly, either to the sensors or to the CAN-Bus of the car (which is even more difficult as every car manufacturer has its own flavor of CAN-Bus). But that is not possible for 99,999 % of the Userbase. So waze's only option would be to clamp the car to the street it is driving on and predict the position with the latest speed. Don't know how easy it would be for Waze to integrate that. But generally a good idea.
Actually, GPS Motion X Drive does this quite well, with sufficient caching of map data to carry me through the back of beyond in western Montana.
Andrea Roher commented
The ability to continue "estimating" your progress when you travel through a tunnel or lose GPS due to heavy cloud cover or whatever is one of the very few ways that Waze is inferior to TomTom. The exact mechanics are much less important to me than that some attempt at estimating takes place.
While probably harder, maybe the camera (if it can see out the windshield), could help with this too. If it can find objects in its FOV and then track how they are moving in relation to the phone (also assuming the phone is not moving, e.g. in a car mount), then conceivably you could track position.
Lou Valencia commented
I've been waiting for this feature in an iPhone navigation app for years, but it still hasn't happened. The GPS in my Acura MDX uses this feature for tunnels and such. In order to do this, Waze can, upon losing GPS signal, start taking readings from the accelerometer and average them over a short period of time to estimate changes in speed (speeding up or slowing down) to adjust the speed where GPS signal was lost. The solution is that changes in direction would appear as +/- X values and changes in speed would appear as +/- Z values at a rate of 0.04559g for every mi/h/s change in acceleration. Here is the reference to the UIAccelerometer API regarding this:
I think this feature would make Waze very cutting edge and show that it is a real contender in the navigation app category. I love using Waze and hope that my contribution makes it a better app for everyone.
There needs to be _some_ way for Waze to proceed when GPS goes away. A couple years ago, when I had a phone without GPS, another free nav service would present turn instructions one at a time, and the driver would click "next" (or "back") as he progresses. Waze could do exactly the same thing and solve the client problem.
On the route analysis side, knowing that a road segment is a tunnel could prompt Waze to calculate average speed of tunnel segments.
Caching map tiles of route
dialin down commented
Now dead reckoning is what I call a suggestion. On page one is a vague feature request
I posted dead reckoning there hoping to stir the pot