Get a sneak peek at whats next for Permanent Hazards on our April 7th Office Hours!
Post by Daknife
Can we talk about how at this current time Waze is handling interstate shields exactly opposite from what the Wiki says.

What I mean is that until recently the guidance was for an Interstate segment to be labeled as I- 15 N or I- 10 W etc with a space after the hyphen. Then the guidance came out and the wiki was changed telling us to label the segments as I-15 or I-10 with no space. Fine, no problem I've spent the time and have most the freeways in Utah updated to match the wiki, but I was seeing very few shields. After careful watching and checking of the couple areas I am seeing shields at I find it's on the few segments I've missed that are labeled the old way.

Thus the Wiki is currently giving the wrong instructions on how to name interstates. At least that is how I'm seeing it actually working, but I've seen no discussion of this, particularly in this thread about that very topic.
Daknife
Posts: 1685
Has thanked: 451 times
Been thanked: 229 times
Send a message
https://waze.com/wiki/images/3/3c/Waze_ ... 00k_6c.png
Former AM in Utah; FormerCM USA
Utah Forum: Utah Forum
Google Pixel 5 on Sprint

Post by Daknife
jasonh300 wrote:The change was made nearly a year ago. Most of the southeastern US has been updated to have the spaces removed and the shield display is very consistent. When you make the change, the shields will go away for a little while, but eventually will come back.

The old convention with the space will still show a shield also.


Via my iPhone 3GS.
How long is a little while? Much of my local freeway network was re-named to remove the space last summer, but the only segments that get a shield are those with the space, be it because I missed those segments when I was making the name edits months ago or because I changed em last week to test the hypothesis.

I put the space in on a couple segments last week and with the last update those segments are now showing shields, where-as the surrounding segments that were named to the no space version months ago just show as I-15 N or I-15 S. My point is, and CBenson just confirmed it in his area; it does appear to work as described in your area, but not in others. So the question is why is it working in some areas and not in others. I've looked at segments in the NOLA area and can't see anything different in how mine are labeled versus yours. So what is the difference? Why won't my properly labeled Interstates show shields?

I will continue experimenting, I've got much of the freeway locked where I noticed little of the NOLA area freeways seemed to be locked, so I just unlocked a couple segments and I'll see what happens after the next update. Perhaps the locks are preventing the shields from generating.
Daknife
Posts: 1685
Has thanked: 451 times
Been thanked: 229 times
Send a message
https://waze.com/wiki/images/3/3c/Waze_ ... 00k_6c.png
Former AM in Utah; FormerCM USA
Utah Forum: Utah Forum
Google Pixel 5 on Sprint

Post by Daknife
I totally agree with Jason, My concern is purely with the Interstates, and the fact that the only segments in my area that are showing shields are those named in the old format versus the format given in the Wiki. I know it is entire under Waze's control at this time, and that they haven't been 100% clear on what does versus what should work. My point for this discussion was that the naming instructions in the Wiki are not working universally as they should.

Jason's Interstates are named I-10 with no space and the shields show correctly. My Interstates named I-15 with no space do not show the shields and segments named under the old format I- 15 do generate and display shields correctly in the Client. The shields are pretty, I want shields to show in the client, but I also want to know that I can point newer editors to the Wiki and if they follow the given naming guidelines it will work.

Other than the time, I don't mind another mass of points to rename my interstates yet again, I just want them to work right.
Daknife
Posts: 1685
Has thanked: 451 times
Been thanked: 229 times
Send a message
https://waze.com/wiki/images/3/3c/Waze_ ... 00k_6c.png
Former AM in Utah; FormerCM USA
Utah Forum: Utah Forum
Google Pixel 5 on Sprint

Daknife
Posts: 1685
Has thanked: 451 times
Been thanked: 229 times
Send a message
https://waze.com/wiki/images/3/3c/Waze_ ... 00k_6c.png
Former AM in Utah; FormerCM USA
Utah Forum: Utah Forum
Google Pixel 5 on Sprint

Post by Daknife
Yep it's basically hit or miss. I see shields more often where there is a space after the hyphen (I- 15) but I see the occasional shield where there is no space. And all the segments in my state have a direction coded after the number. (I-15 S) (I- 15 S) (I-15 N) (I- 15 N) A while back I thought it had reverted entirely to needing the space but now I've found segments with both, that generate shields and segments in both formats not having shields.
Daknife
Posts: 1685
Has thanked: 451 times
Been thanked: 229 times
Send a message
https://waze.com/wiki/images/3/3c/Waze_ ... 00k_6c.png
Former AM in Utah; FormerCM USA
Utah Forum: Utah Forum
Google Pixel 5 on Sprint

Post by harling
AlanOfTheBerg wrote:I'm kinda okay with this. In Oregon, all routes are referred to verbally as "highway" though.
In MA, state and US highways are differentiated only by shield; both types are simply referred to as "route nn" by locals. I had hoped to be able to use (e.g.) "US-1" and "MA-2", so that each state can use its own verbal highway designation. Visually, "US-1" would make sense, but nobody around here is going to have the foggiest idea what "SR-2" is all about.

Isn't it enough that you call rotaries "roundabouts"? ;-)
harling
Posts: 1736
Has thanked: 9 times
Been thanked: 101 times
Send a message
https://www.waze.com/wiki/images/a/ad/W ... os-sig.png
Area Manager, Eastern MA & Southern NH. Country Manager, USA.

Post by harling
WeeeZer14 wrote:...I would love to see some intelligence in the client to know that SR-2 is in the state of MA, so therefore render the name as "Route 2" and make TTS say "Route 2".
When we eventually get independent "shield" control, the exact text of the highway name may be less important, and the audible can be selected by the state field of the segment. In the meantime, though, I would rather depend on a low-tech naming method, than wait for signs of "intelligence". ;-)
harling
Posts: 1736
Has thanked: 9 times
Been thanked: 101 times
Send a message
https://www.waze.com/wiki/images/a/ad/W ... os-sig.png
Area Manager, Eastern MA & Southern NH. Country Manager, USA.

Post by harling
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". ;-)]
harling
Posts: 1736
Has thanked: 9 times
Been thanked: 101 times
Send a message
https://www.waze.com/wiki/images/a/ad/W ... os-sig.png
Area Manager, Eastern MA & Southern NH. Country Manager, USA.

Post by harling
There is also legibility. Around here, we don't distinguish (verbally) between US and state highways (both are "Route nn"), but while "US-nn" is intuitive, people around here would be scratching their heads wondering where "SR-nn" came from!
harling
Posts: 1736
Has thanked: 9 times
Been thanked: 101 times
Send a message
https://www.waze.com/wiki/images/a/ad/W ... os-sig.png
Area Manager, Eastern MA & Southern NH. Country Manager, USA.

Post by jasonh300
All US highways in Louisiana and Mississippi (and I believe throughout Banished's realm) have been converted to the US-## format for nearly a year. It works well. But it won't generate shields. When we talked about it, we were told that they could add that naming convention to the existing shield generator, which never happened. Then there was talk of a way of manually generating shields in the editor which also never happened.


---------
Via my iPhone 3GS.
jasonh300
EmeritusChamps
EmeritusChamps
Posts: 7568
Has thanked: 131 times
Been thanked: 530 times
Send a message