PhantomSoul wrote:It seems also that, with divided roads, when we put the N, S, E, or W suffix in the name to indicate direction, the iPhone client does not produce a shield. Also, dual-signed roads: "I-95 / NJ Turnpike" does not produce a shield in the iPhone client as well.
txemt wrote:I was noticing, the other day, that the route shields are wrong, in the State of Texas. I know it's been said that the shields are FUBAR, but will they be fixed in the not so distance future? If that's the case, will they be set to their respective states?
Nacron wrote:Any word on shields being added to future editors?
Panther37 wrote:So how did you get this done? I'd like to to see Waze recognize at least SR-XXXX in the USA. Also I wish it would look into the alternate names for shields.
AlanOfTheBerg wrote:It is unlikely we will get state-specific shields any time soon or at all. The method used now is the same as most other online map providers such as gmaps or bing, where all states get the same shield style.
PhantomSoul wrote:Hopefully Waze will expand its shield pattern recognition to include these in the near future.
It's absolutely logical to do it this way - changing the streetnames would be much more work.PhantomSoul wrote:matching the 2-letter abbreviations of any of the states or American territories, since many prefer to go by that.