500ft TTS notification?

Moderator: Unholy

Re: 500ft TTS notification?

Postby 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. :-)
... and the "v" is for Volvo.
Beta tester
Beta tester
Posts: 548
Joined: Thu Jun 07, 2012 6:08 pm
Location: Ithaca, NY USA
Has thanked: 49 times
Been thanked: 44 times

Re: 500ft TTS notification?

Postby PhantomSoul » Mon Jan 07, 2013 7:48 pm

As far as I know, a TTS system that is savvy in imperial distances should probably read out distances of less than a mile as follows:

1 or more miles = # of miles
0.5 = half a mile
0.2-0.3 = quarter of a mile
0.1 or less = # of feet, starting with 500 (0.1 miles = 528 ft; the 28 ft over 500 is really insignificant on the road when approaching a turn) and counting down.

Typically, highways signs, at least here in New Jersey - and this is most evident on construction signs, starting counting down feet at 1500, suggesting that really anything less than a quarter mile should just be measured in feet. I realize 1500 ft is a little more than a quarter mile, but I guess it's more obvious and concise - and probably easier to print - on a sign than a quarter mile.

Something is definitely funky with the distances to roadside alert pins. I don't think it's showing metric figures instead of imperial, because that would make things appear on the Waze map closer than they really are. Rather the effect is opposite; I drive about half a mile and it only counted off a couple hundred feet.
MENTOR, CM: United States, AM: Northern NJ, Upstate NY
Waze Editing Manual | USA Road Types | USA Forum
Verizon iPhone 6 / iOS 9.1 / Waze
Country Manager
Country Manager
Posts: 1354
Joined: Wed Oct 10, 2012 4:00 am
Location: Union, NJ USA
Has thanked: 243 times
Been thanked: 419 times

Re: 500ft TTS notification?

Postby 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...
iPhone 5s (AT&T) • iOS 7.0.3 • Waze
✰ Mega Driver ✰ Mega Mapper ✰ 1M Points ✰
Country Manager: USA • Regional Coordinator: USA South Atlantic (KY, TN, NC, SC)
Navigation/Routing ExpertForum Moderator
Waze Global Champs
Waze Global Champs
Posts: 3761
Joined: Sun Apr 11, 2010 3:27 pm
Location: Knoxville, TN, USA
Has thanked: 46 times
Been thanked: 313 times


Return to Navigation & Routing

Who is online

Users browsing this forum: No registered users