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.
jondrush wrote:WeeeZer14 wrote: * Any thoughts on what to do with Primary vs. Secondary routes? For part of PA they are using "PA-xx" for primary and "SR-xxxx" for the secondaries. In TN there are primary and secondary and less of a distinction between them. And the same numbered route may change between primary and secondary along its path.
I think it comes down to expectations of a shield in the client. In PA, SR-xxxx roads do not get shields in real life and are almost always referred to by another name.
How about we let them implement it first (at least in WME Beta) - what we think they will be doing could change between now and then...AlanOfTheBerg wrote:Now that we know how Waze will be implementing shields based on data objects, should this be untabled again?
I've been saying the same thing in various posts...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". ]
txemt wrote:This was a private conversation I was having with another manager about the shields around Texas. I can confirm shields are displayed for the first permalink and the two on I-45 outside of Houston. In te editor, I-37 S shows the shield in the name, but not I-37 N. Same with I-35 through San Antonio, but when 35 get to the outside loop of San Antonio, the shield disappears all together, both in the client and in the editor.
Users browsing this forum: No registered users