harling wrote:Isn't it enough that you call rotaries "roundabouts"?
AndyPoms wrote:That's why I suggest using "CT-##" or "MA-##" and the "CT-" or "MA-" triggers the translation, NOT the state field... That way the ramp that is in CT that leads to MA-## will trigger the MA- lookup...WeeeZer14 wrote:* I perviously mentioned using "SR-xx" and doing a translation/lookup based on the state the segment is in. But I later had the thought that near borders you will have ramps leading to highways in other states. So we can't rely on the state field of the segment to give us the proper translation.
rbthomp76 wrote:My statement was one against using route in place of highway in states where they are officially know as highways. I realize that some states use routes and some use highways. I think that Waze should use the naming that is consistent with the state's approach and not a overall national approach.
jasonh300 wrote:harling wrote:I've been saying it since the topic first came up, and I'll keep saying it: use the standard two-letter state code for state routes/highways rather than a generic "SR-", and translate it for the speech processor according to local custom. For example, MA-nn would be "Route nn", which would make sense to the locals both visually and audibly. ["SR-"anything is almost as foreign as calling rotaries "roundabouts". ]
I see your point. That would be easier than having to do
- Code: Select all
IF road=SR-## AND state=Alabama THEN say State Highway ##
for every state.
jasonh300 wrote:A route was something that trucks and buses, or the paper boy followed.
Users browsing this forum: No registered users