Shields

[txemt]

I took a look just for kicks, and found that a lot of I-86 in my area is now shielded again, but parts of it aren't; also, I-390 isn't showing shields here. Again, due to the awesome communication we always get from Waze , we really don't know what's going on ... but any return of shields is better than none, I suppose.

I've noticed that some highways are labeled and some aren't. It also varies on the zoom level, I've noticed.

[vectorspace]

I don't see any shields in northern New Mexico!

[txemt]

I don't see any shields in northern New Mexico!

Looks like a shield to me!!!

[vectorspace]

I don't see any shields in northern New Mexico!

Looks like a shield to me!!!

That's interesting. Perhaps it's a client issue. I was using an iPad and saw no sheilds in Central NM around Albuquerque on I25 and I40 or any of the other highways.

[txemt]

I'm trying to make a liar out of you.

[vectorspace]

I'm trying to make a liar out of you.

Join the club!

I could post images, too, from my iPad, that show only "I- 25" and no shield. Woonder why the iPad client is not showing shields?

[txemt]

Join the club!

I could post images, too, from my iPad, that show only "I- 25" and no shield. Woonder why the iPad client is not showing shields?

*shrugs*

[invented]

Zero shields in Ontario.

[PhantomSoul]

I've noticed in New Jersey for the iPhone client, we get shields for some of the US routes that are labelled "US Hwy." Most of the state routes I've seen on the map do not produce shields as they seem to be labelled "State Rte" (instead of "State Hwy," maybe?). This is a problem because all numbered roads in New Jersey are referred to as "Routes" and not "Highways" and really should be reflected as such in any regionally savvy navigation system. This is because many of these routes are simply marked out over old, local urban roads and calling them highways misleadingly implies that they're some kind of fast way to get somewhere.

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.

[WeeeZer14]

I've noticed in New Jersey for the iPhone client, we get shields for some of the US routes that are labelled "US Hwy." Most of the state routes I've seen on the map do not produce shields as they seem to be labelled "State Rte" (instead of "State Hwy," maybe?). This is a problem because all numbered roads in New Jersey are referred to as "Routes" and not "Highways" and really should be reflected as such in any regionally savvy navigation system. This is because many of these routes are simply marked out over old, local urban roads and calling them highways misleadingly implies that they're some kind of fast way to get somewhere.

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.

As previously mentioned, shields are somewhere between unreliable and totally FUBAR. We just have to live with it until we are given control over shields that is not tied to specific naming conventions.