500ft TTS notification?

by **AlanOfTheBerg** » Fri Dec 21, 2012 6:37 am

I started getting 500ft notifications today instead of .1mi. The problem is that the notification comes at .1mi and not 500ft.

EDIT (added after several posts): The notification is coming at near .2 miles (.19 miles actually) instead of the intended .1/500ft mark.

by **AndyPoms** » Fri Dec 21, 2012 9:52 am

AlanOfTheBerg wrote:I started getting 500ft notifications today instead of .1mi. The problem is that the notification comes at .1mi and not 500ft.

I'm seeing (hearing) this as well - BUT I've also lost TTS, so I'm just getting "In 500 feet, turn right" instead of "Turn right on Main Street"

by **jasonh300** » Fri Dec 21, 2012 11:03 am

I noticed this also. What exactly did it say before? I can't remember.

Also, realize that .1 mile is 528 feet. By the Waze method of conversion, this is much closer than 500 ft = 500 m that they've used in the past.

Via my iPhone 3GS.

by **cdombroski** » Fri Dec 21, 2012 2:44 pm

I noticed a few changes this morning as well.

In one half mile, prepare to exit right -> In one half mile, exit right

In zero point six miles, prepare to exit right -> In oh point six miles, exit right

I also think the timings have changed for the final prompt (turn right at X); it seems to come sooner than before.

by **AlanOfTheBerg** » Fri Dec 21, 2012 4:02 pm

Okay, so this is what I found. In .1 miles it does say 500 feet instead of .1 miles. For the 1 mile mark and the quarter-mile mark, it says to make the turn, it has dropped the "get ready" part. I would imagine, that for other speed notifications, that the .5 and .6 mile mark also have had their TTS changed.

by **AndyPoms** » Fri Dec 21, 2012 5:06 pm

On my return trip I got full TTS, but with the 500 foot instead of .1 mile warnings...

by **AlanOfTheBerg** » Fri Dec 21, 2012 10:28 pm

Oh, so I did a typo in my OP. The 500ft warning is coming as soon as the app shows .1 miles, which is really .19 miles. So, this 500ft warning is coming very near the .2 mile mark instead of the actual 500ft mark.

by **jasonh300** » Fri Dec 21, 2012 11:30 pm

AlanOfTheBerg wrote:Oh, so I did a type in my OP. The 500ft warning is coming as soon as the app shows .1 miles, which is really .19 miles. So, this 500ft warning is coming very near the .2 mile mark instead of the actual 500ft mark.

Maybe it's giving you extra time to "get ready".

by **ncc1701v** » Fri Dec 21, 2012 11:39 pm

Good: 0.1 miles is 528 feet. You probably pass 500 feet in the middle of the announcement.

Bad: oops, 0.19 miles is not 0.1 miles. :-)

by **WeeeZer14** » Sat Dec 22, 2012 2:26 am

I think the developers need a refresher on math (or maths for the INTL people):

- Client speed knots to mph/kph rounding causes some values to never appear
- Segment length shown in the map editor causes confusion about U-turn surpression (less than or equal to x will surpress, but x.9 is shown as x so what happens then?)
- NA client showing feet/meter mix up for distance to hazards
- 500 feet warning at close to 0.2 mile instead of 0.1 mile.
- UR in the editor - Today? Yesterday? Who knows?

Makes you wonder what bugs are hiding in the routing code...