I'm android and always up for helping to test anything.

As a side note, the way the current TTS says 'Henrietta' is hilarious and/or scary, take your pick.

What's ironic, sketch, is around here we don't call them state route or state hwy. We just call it '291.' MAYBE 'highway 291' and very, very rarely 'route 291.' But it's usually just '291.'

I've even caught newbie editors around here changing it to say that as well. =/

Look at the road.

Point at it.

Begin the sentence: "That is a..."

If your sentence ends with 'interstate' make sure that's in the name. If your sentence ends with 'state highway' or 'state route' make sure that's in the name. Etc.

Would you really say "that is a forest service"? I would think the sentence would make more sense by saying "That is a forest service road."

Essentially, the standard is for the type of road to be fully given, and THEN the number. Is it a 'forest service' or is it a 'forest service road'?

It's like the difference between saying 'state highway 291' and 'state 291'.

I personally vote the 'road' as being necessary for standardization purposes. Do I think it'd work fine without it? Yup. I think '291' is all that's needed and we could drop the 'state hwy' part. But for standardization purposes, I don't think it harms anything to have the couple extra words.

I-80-whatever is 'an interstate' and so it includes interstate in the name (abbreviation I).

I don't know what broadway is. It could very well be 'a broadway' and therefore broadway's in the name.

If the forest service roads are as bad as you say and shouldn't be used for through-driving, perhaps marking them 'private road' could be considered. This would prevent routing through them unless the destination requires it. And definitely 'dirt road' for the ones that aren't paved.

And to me, the key part of the instruction is not the number, it's the 'turn right' part. If I know I need to turn right, the name of the road I'm turning onto almost isn't even important at all, unless it's an intersection with unusual geometry, at which point I typically just look at my phone to see where it wants me to go.

I named the road into the parking lot where I live 'Really long name of absolutely no significance except for testing.' I then named another road in the parking lot 'another name of absolutely no significance but is still of use for testing.' It didn't have any pauses or abbreviations in there so they didn't take as long to say as I had originally expected (about 2 seconds each) but it had no problem announcing them in time. Particularly the 'turn right' instruction.

So again, I personally don't really care either way. I think 'forest service' is just fine. But as far as matching the standard, I think 'forest service road' is more consistent with other abbreviations.

I was talking with txemt about this issue in another thread. Personally I would want to label where ramps split even if it's only 100 feet or so to the next turn and the label would be rather long.

Because I feel like the key portion of the instruction "keep right" is the very first thing said, and the rest is just gravy. Therefore the TTS is relatively unimportant semi-beneficial information but if it cuts itself off to give the next instruction, that's okay with me. In the meantime, the on-screen information is accurate and matches the sign at the split exactly.

If it doesn't cut itself off and fails to give the next instruction because the previous one is still going, that's a problem, and potentially worth shortening or removing the names of short-length ramps. Txemt was saying that's what happens and that's what I was trying to test. But I couldn't find an instruction long enough that it needed to be interrupted, even when I was trying to manufacture one. =(

Based off the picture, I would name that "to I-80 Bus E / SR-99 S / Reno / Fresno"

While I wouldn't object to doing columns first, I'd probably eventually come along and rename it that way, just because I agree that I care more about SR-99 S being on this split (especially if I'm going that way) than I do about Reno being on the split.

Essentially, I follow the column idea that you advocate except I prioritize numbered roads over cities. In my opinion, cities are a bonus to give extra detail, the name of the road you'll actually be driving on is more important.

Then I'd name the following ramps "to I-80 Bus E / Reno" and "to SR-99 S / Fresno"

Even if the original split has a long name, it would have enough time to spit out the vital 'keep right' or 'keep left' beginning of the next instruction, especially if it interrupted itself to do so, which I believe it should if it doesn't already.

Plus, if the user is actually using the visual indicators on the device as well, there shouldn't be any doubt about which way to go.

Plus, if the segment really is that short a distance in time to travel, the instructions should say "keep right and then keep left" 500 feet out from the first split. Perhaps upping the minimum distance before an 'and then' prompt could be useful as well, especially when traveling at high speeds.

If none of the above was accurate and users were not getting the vital 'keep left' or 'keep right' in time then I'd change the name of the first split into "to I-80 Bus E / SR-99 S" and see if that worked, and if that still didn't work then I'd remove the name and leave that segment unnamed so that the name of the next split they're taking would populate to the first split.

I would, however, prefer to name signs accurately and let the TTS handle it, interrupting itself if need be, and/or giving the instructions further out so it has time to speak them. Only if it's a confirmed TTS fail from like a UR or something would I start simplifying or removing names.

The main bug I have is that the TTS given of a destination when you've reached it seems to use a different TTS than the TTS of turn instructions.

As a turn instruction, 'Ave' is always Avenue, but as a destination, it rhymes with 'have.' =/

The one with the at is the turn instruction, I would assume. The one without the at is the destination.

MGODLEW wrote:I discovered an issue with TTS the other day for this "Place" Magisterial District Court 11-3-07 Its official name is Eleven Three Zero Seven however waze pronounces 11-3-07 as Novermber 3rd, 2007. "Arriving Magisterial District Court Novermber 3rd, 2007"

....You were driving a DeLorean, weren't you?

jasonh300 wrote:

MGODLEW wrote:It is with a heavy heart, I am sad to report, I was not in the Delorean that day. The flux capacitor needed some fine tuning so I was forced to use my hoverboard.

Mi aerotabla está lleno de anguilas.

Hey McFly, que Bojo! Esas juntas no funcionan en el agua!
A menos que tengas PODER!