I was hoping that a tool was available. That seems counter productive…
What do you mean an island of roads?
Sent from my SGH-I747M using Tapatalk
Is that really how we’re supposed to do it? cringe
Before doing that, please PM GizmoGuy411 – he has been handling a lot of the TTS list maintenance and may be able to give you some tips.
Having talked to directly to hmarian about this very topic, a while ago, he went that way because that is what the signs say. They say Pkwy not Pky, so as to not confuse anything he went with “Pkwy”. While each character, say the “w” is 8 bytes and 1000’s of these does add to up to quite a bit, I believe he has the right attitude on this and I think it should be what the sign says. Now both abbreviations give the same TTS output, but I would leave them as per the signage.
Greg
I mean yeah, but again I go back to the wiki saying that we’re supposed to use what Canada post is using for some reason, and didn’t see a directive that changed that.
I agree, we should be per the wiki, or we should change the wiki.
“Pky” and “Pkwy” give the same TTS output, so why not use the the shortest short form. Since by law you are not supposed to be looking at your GPS, what is the usefulness of the extra “w”? So we should use “Pky”, right? But it should also be as per the signage. So I dunno?
When I read Pkwy, there is no doubt in my mind as to what it means. Pky is not as intuitive, IMO.
Generally, we should follow the CanadaPost abbreviations, because they’re a documented standard that goes beyond anything we could develop as a standard here.
That said, there are exceptions. Since they both pronounce correctly by TTS, we should probably follow the signs.
There are exceptions to this. I think that “Trl” is the CanadaPost abbreviation for Trail. But Calgary uses “Tr” – and I’m not sure that “Tr” has been verified to work correctly in the TTS.
I don’t know that we need to change the standard away from CanadaPost’s list – except to perhaps document that there may be some exceptions.
Yes I could. Just stumbled on this, so I am chiming in.
The TTS issues are on-going. As far as testing, I’ve suspended it until I get better answers from Waze. After I discovered some issues during TTS testing, that may require a complete restest of EVERY item in the list, it made no sense to continue testing until the questions were answered. Those questions I asked at the Global Meetup last fall in Israel are still unanswered. Maybe doctorkb and I can tag team them in Las Vegas to finally get those answers.
Information is already available in the forum thread on how to test TTS. For a more detailed explanation I can be contacted via PM.
Information on some of the questions for Waze are there as we’ll.
The biggest concern is that there may be TWO possible results for TTS. One while in route and another when the destination is reached. All to often these are NOT the same. Initially the list was tested under the assumption that one one result was given for any given item. As you can see, that somewhat invalidates the testing results for entire list as it now stands.
https://www.waze.com/forum/viewtopic.php?f=339&t=83745&p=726716#p726716
More interesting TTS stuff:
“The Esplanade N” is pronounced “The Esplanade Enn”