iOS Beta 3.1.99.17 Feedback thread

[AlanOfTheBerg]

When your stop-point is within a parking lot, because the parking lot roads are unnamed, the turn from a named road into the unnamed parking lot inherits the name of the next turn out of the parking lot, even though that turn is for when you are done with your stop.

This can be quite confusing, especially for people unfamiliar with the area. As you can see in this screenshot, Waze is directing me to turn into a parking lot to get to Safeway. However, it says turn onto "N Springbrook Rd" which is both the turn I would take out of the parking lot after my stop, but it is also the name of the street at the next intersection. Waze will show this and Waze will tell me to "Take a right at north springbrook road" which is incorrect routing instructions.

Turning into parking lot, not Springbrook Rd

IMG_1724.PNG (152.17 KiB) Viewed 421 times

In the next screenshot, you can see that it still says the name of my next turn and you can see here where N Springbrook Rd intersects the previous road I was on, and why this would be confusing to drivers.

IMG_1725.PNG (117.96 KiB) Viewed 421 times

[Shorty-CM]

Blame that on the *great* decision to not name exit ramps.

[gettingthere]

When your stop-point is within a parking lot, because the parking lot roads are unnamed, the turn from a named road into the unnamed parking lot inherits the name of the next turn out of the parking lot, even though that turn is for when you are done with your stop.

Yet another reason not to map Parking Lot roads until Waze re-works the way that these work:

* Implement transition penalty for Parking Lot roads (similar to the way Private roads have recently been changed but with suppression of traffic jams)
* Remove current 'non-routable', high penalty system
* Not advance the street name announcements when navigating unnamed parking lot roads or private roads (what you are reporting that also occurs in the non-beta versions of Waze)

[Shorty-CM]

Or just name the road, heh.

Yet another reason not to map Parking Lot roads until Waze re-works the way that these work:

* Implement transition penalty for Parking Lot roads (similar to the way Private roads have recently been changed but with suppression of traffic jams)
* Remove current 'non-routable', high penalty system
* Not advance the street name announcements when navigating unnamed parking lot roads or private roads (what you are reporting that also occurs in the non-beta versions of Waze)

[AlanOfTheBerg]

* Not advance the street name announcements when navigating unnamed parking lot roads or private roads (what you are reporting that also occurs in the non-beta versions of Waze)

Yes, I imagine this could happen, but it is unlikely due to the penalty associated with private and parking lot roads. Waze would never route you through a parking lot like this, from one road to another, unless no other route existed. I do get what you mean, however. Waze does route you out of a parking lot using the next named segment repeatedly.

[gettingthere]

How are the gas station and category functions going to impact the performance of Waze when these features are rolled out to the masses? Is this going to create server timeouts on a massive scale?

[RallyChris]

Since I can reproduce it in the beta, think I will post it here in the hopes that it will be looked at (even though I think this is not a beta induced issue).

Volume issue.

My personal opinion is that the volume for TTS is too low, despite have all the sliders to full, and the application volume (by the volume buttons when TTS is active) turned all the way up also.

I noticed the other day while switching between apps, that the volume is perfect when the application is backgrounded. Only when it is in the foreground does the volume get too soft again.

[AlanOfTheBerg]

I noticed the other day while switching between apps, that the volume is perfect when the application is backgrounded. Only when it is in the foreground does the volume get too soft again.

I've also had this happen, though cannot reproduce reliably.

The other issue with the app volume being way too low despite the slider showing 100% persists, though I cannot figure out how to reproduce it either. What happens, though, is that if you bring up the Sound settings and it shows 100%, when it plays a sound, it will auto-adjust the volume down to what it really is and then it will stick there, giving me the opportunity to adjust it to 100% where I want it.

[tibble]

I see way too many no name turns in the navigation list. Is it not using next segment name for unnamed roads? or maybe it's using next segment but not working if it's two unnamed in a row?

[gettingthere]

Issues with the NAV list had been reported with a previous version/beta. It appears that Waze is not using the same methodology that it is using for ramp names and route instructions in the NAV list. In the case of only ramp segments, Waze should not show no name in the NAV list.