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.

And yes, there should be a differentiation between state and US highways.





Sent from my iPhone using Tapatalk

WeeeZer14 wrote: So what would "consistent with the state's approach" mean in TN where State Routes are defined under the State Highway code of law, the DOT puts up signs that say "SR-xx" for detours, and lay people seem to generally use "Highway xx" with no distinction for US vs. state?

Not sure what to tell you there. Agreement among the area AMs I guess... (Might be easier to change local's minds )

For MS, our MDOT has a state highway map that specifically defines them as highways. Guess we are lucky in that regard.

Our locals refer to everything as highway as well, typically with a direction attachment that only makes sense to locals. (I.e. Highway 13S ... And I'm not talking about southbound lane either)




Sent from my iPhone using Tapatalk

Anyone have the scoop from Waze on Shields yet?

I've been doing some fixes around St. Robert MO area. Check this out...

https://www.waze.com/editor/?zoom=2&lon ... s=28432621
This area has since been updated, but "SR-17" + Minor Hwy type = this in the client
The name "I-44 Loop" + Major Hwy type produced the shield icon in the client:
The actual Interstate is set to freeway and named "I-44 E" and "I-44 W" but does not produce the shield icon.

So the "Loop" / "Business" / "Spur" 's are producing the Shields in the client (I assume cause they are set to Major Hwy), but if you set segments to Freeway you don't get them ?

Right now, it appears to me that if you want the shield icon, you have to have the name + type set specifically before they display.

Has anyone else duplicated these results?

txemt wrote:There is no rhyme....or reason.

It sure seems that way. But it's computer code, and there's got to be a work-around. If we can discover it, we can temporarily "game the system" into showing the icons when and where we want.

I'll do some experimentation and see what I can find out. In the mean time if anyone reading this has the "magic line" to the dev's at Waze... Pretty please let us know some info. Be it a work around, or a snipped of the code logic for when to display the shields, etc. Maybe something can be done.

I agree with this proposal for the standard naming of highways when a different local standard is not in effect.

I find that "hwy-xx" looks very unprofessional in the client.

TTS reads "SH-xx" as "state highway-xx" so there is some logic in using that.

In spite of that I have settled on "SR-xx" even though in my area we call everything "highway-xx" inculding interstates. Because it seems to be the most professional and understandable format. I don't like any of the longer formats since for a numbered road shorter is better.

Howdy,

I'm glad I found this thread as I've been wondering why our State Highways up in Northern California are mostly labled SR XX (oddly by Kentsmith9 ) So now I understand the desire to have the TTS sound good & the map look clean. My question is about signage up here in the sticks that calls the roads out as "Highway" or "Hwy"? Many of our grade crossings have little signs that say "hwy 99" or "Highway 70" lots are off private roads but many are when you come up a County or Forest Service road to a "T" intersection it says "Highway 70" at the top, then points a way and gives the town and distance. I've pretty much grown up in "Highway Country" and the term State Route is something from movies, but I guess if the consensus is that people can do the math in their head I'm good with SR.

txemt wrote:

andrewfatcat wrote:

txemt wrote: Take a look at these 4 permalinks:

I-37 S in San Antonio and click on the northbound lane, too.
https://www.waze.com/editor/?zoom=6&lat ... s=62063460

I-45 in Houston
https://www.waze.com/editor/?zoom=3&lat ... s=47488912

I-45 in Madisonville, Tx
https://www.waze.com/editor/?zoom=2&lat ... s=67774082

I-45 in Centerville, Tx
https://www.waze.com/editor/?zoom=2&lat ... s=67774297

If you look at all four of road segments, they're all named differently, with 37 and 45 (Houston) being named the same. 37 and 35 both show shields in San Antonio, but 35 stops showing shields at 1604. After that it's spotty. I haven't seen a shield on 10 or 410 at all. This bug HAS to be a code bug somewhere.

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.

banished wrote:Does adding an alternate name, such as in the old I- xx format, have any impact?

I don't know the answer, either, but perhaps worth investigating.

Yes, in this permalink, the only minor highway shows a shield in the client:

https://www.waze.com/editor/?zoom=3&lat ... TTTFTTTTFT

bigbear3764 wrote:

rottielover wrote:
The actual Interstate is set to freeway and named "I-44 E" and "I-44 W" but does not produce the shield icon.

From what I understand, putting the cardinal directions in I-44 E, it wont produce a shield. They were trying to get Waze to accept the cardinals for shields, but nothing yet.

Not true. Look at the 4 permalinks I provided a few posts ago. I showed 4 different sections of interstates around Texas and all four are labeled differently. Some produce shields and some don't. I can attest that "I-37 S" in San Antonio produces a shield, but "I-37 N" does not.