iOS v3.7 Official Feedback Thread

These forums are specific to the Waze mobile app. Post here if you experienced a problem while using the app, have a question about the app functionality or a feature such as navigation or search.

Moderators: Unholy, Unholy

Re: iOS v3.7 Official Feedback Thread

Postby davipt » Tue Jun 11, 2013 10:06 pm

.5 miles are 800m, that's how it's been working since at least 3.6. I think before there was an announcement at 1km and 500, but now it's 800, 400, 200. This is what in feet?
ImageBruno D. Rodrigues | Global Champ
Coordinator for Portugal | Expert iPhone and others
Forum PT | Wiki PT | Facebook PT | Twitter PT
davipt
Waze Global Champs
Waze Global Champs
 
Posts: 2720
Joined: Tue Nov 02, 2010 8:51 am
Location: Oeiras, Portugal
Has thanked: 271 times
Been thanked: 547 times

Re: iOS v3.7 Official Feedback Thread

Postby unlimitedsounds » Tue Jun 11, 2013 10:24 pm

davipt wrote:.5 miles are 800m, that's how it's been working since at least 3.6. I think before there was an announcement at 1km and 500, but now it's 800, 400, 200. This is what in feet?


but what about it not even said like saying the street name at all? I think it should know the street name as it has it on screen so it should always announce
unlimitedsounds
 
Posts: 89
Joined: Fri Mar 05, 2010 9:07 pm
Has thanked: 0 time
Been thanked: 10 times

Re: iOS v3.7 Official Feedback Thread

Postby sketch » Tue Jun 11, 2013 10:27 pm

Do you remember where this happened on the map? Sometimes, when a segment on the map is not named, Waze will display the name of the next named segment on the route, or the last named segment if there are no named segments remaining, but won't speak a name at all.
ALL US EDITORS READ: New USA road type guidance
new orleans based • detroit enthusiast • usa country manager
2013 ford focus titanium hatchback 5mt • performance blue
Image Image
sketch
Waze Global Champs
Waze Global Champs
 
Posts: 5635
Joined: Sat Aug 08, 2009 6:13 pm
Location: New Orleans, LA
Has thanked: 1199 times
Been thanked: 1654 times

Re: iOS v3.7 Official Feedback Thread

Postby unlimitedsounds » Tue Jun 11, 2013 10:39 pm

sketch wrote:Do you remember where this happened on the map? Sometimes, when a segment on the map is not named, Waze will display the name of the next named segment on the route, or the last named segment if there are no named segments remaining, but won't speak a name at all.


what do you mean by not named? it showed all the street names on the Top left but didn't announce the name. in 3.6 it did. this is trout road in 08012
unlimitedsounds
 
Posts: 89
Joined: Fri Mar 05, 2010 9:07 pm
Has thanked: 0 time
Been thanked: 10 times

Re: iOS v3.7 Official Feedback Thread

Postby sketch » Tue Jun 11, 2013 11:32 pm

unlimitedsounds wrote:this is trout road in 08012

Ah, here?

https://www.waze.com/editor/?lon=-75.01 ... TTTFTTTTFT

I would bet the problem is that Hidden Dr and Trout Rd have the same endpoints. This can cause problems with navigation.

I will leave it like this long enough for you to see it, but I'll fix it afterwards.

When you have a loop like that, where both ends connect to the same segment, navigation can become problematic. The solution is to introduce an "extra" node into Hidden Dr (or Trout Rd) so that no two segments have the same two endpoints.
ALL US EDITORS READ: New USA road type guidance
new orleans based • detroit enthusiast • usa country manager
2013 ford focus titanium hatchback 5mt • performance blue
Image Image
sketch
Waze Global Champs
Waze Global Champs
 
Posts: 5635
Joined: Sat Aug 08, 2009 6:13 pm
Location: New Orleans, LA
Has thanked: 1199 times
Been thanked: 1654 times

Re: iOS v3.7 Official Feedback Thread

Postby unlimitedsounds » Tue Jun 11, 2013 11:36 pm

sketch wrote:
unlimitedsounds wrote:this is trout road in 08012

Ah, here?

https://www.waze.com/editor/?lon=-75.01 ... TTTFTTTTFT

I would bet the problem is that Hidden Dr and Trout Rd have the same endpoints. This can cause problems with navigation.

I will leave it like this long enough for you to see it, but I'll fix it afterwards.

When you have a loop like that, where both ends connect to the same segment, navigation can become problematic. The solution is to introduce an "extra" node into Hidden Dr (or Trout Rd) so that no two segments have the same two endpoints.


it also didn't know exactly house was and 3.6 did
unlimitedsounds
 
Posts: 89
Joined: Fri Mar 05, 2010 9:07 pm
Has thanked: 0 time
Been thanked: 10 times

Re: iOS v3.7 Official Feedback Thread

Postby davipt » Tue Jun 11, 2013 11:53 pm

unlimitedsounds wrote:
davipt wrote:.5 miles are 800m, that's how it's been working since at least 3.6. I think before there was an announcement at 1km and 500, but now it's 800, 400, 200. This is what in feet?


but what about it not even said like saying the street name at all? I think it should know the street name as it has it on screen so it should always announce


Can you please click on the permalink above, click on the two segments where you expected to have an instruction, state the origin and destination?

Looking at these reminded me that there are at least a case where you can see instructions on the screen but get no audio instructions. I'm too tired now to do some math, but if an angle is shallow enough to now trigger a "keep" instruction but open enough to show a visual instruction, also depending on the type of street and names and the phase of the moon, so hence why it would be nice to get the exact spot.


PS: tomorrow I'll split this part of the conversation into a new thread, I'm getting some sleep now.
ImageBruno D. Rodrigues | Global Champ
Coordinator for Portugal | Expert iPhone and others
Forum PT | Wiki PT | Facebook PT | Twitter PT
davipt
Waze Global Champs
Waze Global Champs
 
Posts: 2720
Joined: Tue Nov 02, 2010 8:51 am
Location: Oeiras, Portugal
Has thanked: 271 times
Been thanked: 547 times

Re: iOS v3.7 Official Feedback Thread

Postby jasonh300 » Wed Jun 12, 2013 1:04 am

sketch wrote:When you have a loop like that, where both ends connect to the same segment, navigation can become problematic. The solution is to introduce an "extra" node into Hidden Dr (or Trout Rd) so that no two segments have the same two endpoints.


Not necessary...the only that that's an issue is if a street starts and ends on the same *node*...a loop that starts and ends in the same place. The problem you're describing went away when they came out with Papyrus IIRC.
Image
New Orleans, Louisiana
Regional Coordinator, South-Central Region
Waze FAQ ... Best Map Editing Practice
Ask me about Louisiana or Mississippi Editors Chat in Google Hangouts!
jasonh300
Waze Global Champs
Waze Global Champs
 
Posts: 7451
Joined: Fri Oct 28, 2011 4:26 pm
Location: New Orleans, LA USA
Has thanked: 372 times
Been thanked: 920 times

Re: iOS v3.7 Official Feedback Thread

Postby sketch » Wed Jun 12, 2013 1:04 am

Yeah, now that I think of it, you're right. That was a Cartouche problem.
ALL US EDITORS READ: New USA road type guidance
new orleans based • detroit enthusiast • usa country manager
2013 ford focus titanium hatchback 5mt • performance blue
Image Image
sketch
Waze Global Champs
Waze Global Champs
 
Posts: 5635
Joined: Sat Aug 08, 2009 6:13 pm
Location: New Orleans, LA
Has thanked: 1199 times
Been thanked: 1654 times

Re: iOS v3.7 Official Feedback Thread

Postby unlimitedsounds » Wed Jun 12, 2013 1:05 am

so how do we fix?
unlimitedsounds
 
Posts: 89
Joined: Fri Mar 05, 2010 9:07 pm
Has thanked: 0 time
Been thanked: 10 times

PreviousNext

Return to Waze App

Who is online

Users browsing this forum: rzPhone