Minimum viable product:

- there’s no gps signal (tunnel), and you know it from the map
And car is on a highway with no way out, and you know it from the map
Then
maintain the last position (under the tunnel) Until the end of tunnel where gps works well

Please find a solution to avoid the non stop recalculation of the route when under a tunnel to any nearby road. Why not have a function based on estimated speed in the tunnel ? Would be really useful in France in Fourviere tunnel or a86 duplex or Monaco with all those underground roads! Thanks

I remember this feature on Sygic installed on my Nokia N95…15 years ago!

Dear Sirs.

You know Tunnels are a problem for us wazers while navigating. Location is innacurate inside tunnels of course and no matter what you do to estimate location, navigation can be innacurate and confusing. But the tunnel exit the driver needs to use to leave the tunnel is FIXED and clear since the time the vehicle enters the tunnel.

I suggest you to indicate the EXIT the driver needs to use since the time of entering the tunnel and keep it until the driver has left the tunnel.
As sometimes the GPS signal is unnacurate and sometimes it seems that the vehicle is outside the tunnel while it really remains inside, the app may ask the following confirmation: Did you exit the tunnel?
Thanks.

Please add it also in Italy! Italian alps ski area and main highways on Apennines have many long tunnels, in Milan there are few but very congested and dangerous! Thank you!

While navigating tunnels GPS signal is often lost and route (wrongly: Waze often places the vehicle position on a nearby street) recalculated, or worst the position updating stops completely. The former case is a bit annoying but the latter is worst because you can easily lose the exit if it’s right after the tunnel end, since Waze recalculate the correct position only when the tunnel is over and the GPS signal restored.

Despite the GPS positioning difficulty, I noticed that very often the speed indication is still right.

By delimiting on the map the tunnels beginning and end Waze would know when the vehicle is entering a tunnel.

When GPS signal is lost or week: I would suggest to lock the rerouting option when inside a tunnel, unless the GPS signal is fully restored, and use the detected speed (if available), the last available position and the tunnel length to estimate the position of the vehicle.

This way it would stop to reposition the vehicle on a nearby street and rerouting when inside a tunnel, and if speed is available it would be able to estimate the position.

When GPS or data reception is poor, Waze starts crazy and irrelevant navigation instead of stopping and declaring a problem.

Much information about how this could be done in https://waze.uservoice.com/forums/59223-waze-suggestion-box/suggestions/2360157-dead-reckoning-when-neither-data-nor-gps-availabl

I guess the "WIP" note is related to Falcon. I guess Falcon makes use (at least) of the cellphone acceleration information. This could be used to match position with curves on the road, at least when those curves are steep, and/or separated.
The biggest problem happens when (somehow) you get spurious GPS samples (this happens in a major tunnel in Madrid, ie. M-30) which takes you OUT of the tunnel. This shouldn't be possible unless you have an exit, and the rest of input (acceleration, again) matches somehow. This breaks any Falcon improvement (once you are taken out the tunnel, road geometry can't obviously be matched).

Most ODB2 dongles present speed data, etc. In a standardized format. Together with acceleration sensors, etc., this should be feasible

The problem is, a device using the sensors you mentioned cannot determine whether you are moving, only accelerations or rotations on 3 axis.

Please start first with navigation based on speed entering tunnel (as mentioned very often in the past). A simple calculation. Later on you can improve every detail you want.

And be able to report a problem even if you are offline or you have a weak signal or none at time of reporting problems.

Very interesting to have those beacons butI I don't foresee in the near time to get them in Spain. In the meantime a simple speed Base could be implemented.

Cannot wait for beacons worldwide please. Add tunnel navigation as gmap at least, with simple speed based prediction

Implemented in Google maps but why not in Waze?

Note that "Here we go" and "Google" have the navigation in tunnels available for a very long time! And it's very useful!

En effet cala manque. Ca fonctionne très bien avec Here we go et Google maps. Nous avons de nombreux tunnels à Paris, avec des embranchements à l'intérieur et c'est absolument indispensable.

Driving in from the western suburbs to downtown Chicago, it loves to use Lower Wacker Drive and then turn onto Lower Michigan avenue. This is kind of great, except you're pretty much on your own once in the tunnel and Android Auto is trying to keep things simple and you can't really look at the next turns, like I can if I unplug. Generally, on emerging, there's a period where things are very confused, and the next few turns are kind of crucial, and suddenly very crowded, so it will drop you in the middle of crowdedness multiple lanes, and then give you bad advice long enough to where you're committed to going one way and really should have gone the opposite way. (For example, tell you to turn left, and you get in the left lane and it switches you to turn right and you're never going to recover in time).

However, if I had a list of turns that would come up on entering the tunnel and a turn or two after it for a bit as the GPS gets more solid, it would help immensely.

Now there is an IC package to accomplish this, lazy google hoard:

U-blox ZED-F9K
"
Continuous lane accurate positioning under the most challenging conditions

. Decimeter level accuracy for automotive mass markets
. Turnkey multi‑band RTK solution with built‑in inertial sensors
. Low latency position update rate of up to 30 Hz
"