Proper Naming for Roads with Multiple Names

[MGODLEW]

I’d like to bring some attention to road naming issues & get some official clarification. I’m sure other states are like this as well but here in PA we have a lot of roads with multiple names. You might have a US Hwy with an official Hwy number which would be US-22. However, these roads may also have a primary local name such as Main St which is displayed on street signs. On top of that, you might have another US Hwy be part of another, so you end up with US-22 & US-119 being the exact same road. Question is, how exactly should naming be handled for these roads? Which should be set as the Primary street name “displayed name”? And should each road segment contain a separate alternate name of each of the road names, IE: (US-22), (US-119), & (Main St). At this point a lot of editors are left with confusion on what the official street name “displayed name” should be. I know it is established that naming should be done in accordance to what is displayed on the street signs, however, what do you do in the situation where you have a Hwy with 2 primary names. Is it acceptable to use 2 names in the primary street name “displayed name”? IE: (US-22 / US-119) or should it be (Main St / US-22 / US-119) See example below The example below does not have a Main St but lets assume for the sake of this question that it does have 3 names total. Permalink or Permalink 2

[CBenson]

There is some guidance here: https://www.waze.com/wiki/Road_Naming_(USA)#Concurrent_names
That guidance seems somewhat tilted towards limited access highways. For full access roads, if the road is signed with multiple choices I try to use the name that is most likely to be used by the properties on the road when giving directions to their locations or when giving their addresses.

[MGODLEW]

Your post cut off some of the URL, https://www.waze.com/wiki/Road_Naming_(USA)#Concurrent_names

If the local signs change back and forth between the local name and the route number multiple times between intersections, consider making the primary name a combination of the two, something like “Main St / SR-66”.

However, what should one do with 3 names in scenario?

[AlanOfTheBerg]

That 3rd example with the slash character should be removed. Any other names are added as alternates. The primary name should never have more than one name.

[MGODLEW]

@AlanOfTheBerg

That 3rd example with the slash character should be removed. Any other names are added as alternates. The primary name should never have more than one name.

Should the Wiki be updated to have this removed:

If the local signs change back and forth between the local name and the route number multiple times between intersections, consider making the primary name a combination of the two, something like “Main St / SR-66”

[AlanOfTheBerg]

Take it to the wiki forum for discussion.

[MGODLEW]

Post Created: Removal of allowing Multiple Names in Road Naming Wiki

[no1uknow]

(Thread resurrection)

There are many instances of interstates and US highways in my area that have concurrent names (I-84/I-380, US-11/US-15, US-22/US-322). When you look at traditional maps and Google maps, the shields for these roads are combined or shown side-by-side. It would be nice if Waze could do this too…

Also, per https://www.waze.com/wiki/Road_Naming_(USA)#Concurrent_names, how do you determine which is the primary? It’s not always obvious.

https://maps.google.com/?ll=40.234067,-76.931677&spn=0.040559,0.084543&t=h&z=14

I’d like to see a feature for Rank 3 or higher to be able to give these roads two names, not just in the alternate name fields. Or, there should be a way to combine these names in one name field.

[crazycaveman]

@no1uknow

(Thread resurrection)

There are many instances of interstates and US highways in my area that have concurrent names (I-84/I-380, US-11/US-15, US-22/US-322). When you look at traditional maps and Google maps, the shields for these roads are combined or shown side-by-side. It would be nice if Waze could do this too…

Also, per https://www.waze.com/wiki/Road_Naming_(USA)#Concurrent_names, how do you determine which is the primary? It’s not always obvious.

https://maps.google.com/?ll=40.234067,-76.931677&spn=0.040559,0.084543&t=h&z=14

I’d like to see a feature for Rank 3 or higher to be able to give these roads two names, not just in the alternate name fields. Or, there should be a way to combine these names in one name field.

According to the Wiki page you linked, the interstate who’s miles are marked (or used for exits) is the primary interstate and the others should be added as alternate names.

When two or more numbered highways (or interstates) run concurrently (one stretch of road has multiple route numbers), the segment should be named after the primary of the routes. The primary route will usually have one or more of the following attributes:

• The route whose mile markers are used for the concurrent segment
• The route whose exit numbers are used for the concurrent segment
• When the concurrency ends, the route whose path does not get signed as a numbered exit
  The other route number(s) can be entered as alternate names.

I have heard a few champs mention that the waze team is working on a way to get the alternate names to show along with the primary name, but nothing has been released publicly yet. W’ll have to see what they come up with…

[AlanOfTheBerg]

@no1uknow

I’d like to see a feature for Rank 3 or higher to be able to give these roads two names, not just in the alternate name fields. Or, there should be a way to combine these names in one name field.

This is a display issue only. The alternate name fields are the appropriate place for the non-primary-names. It is up to Waze to properly display this information. We will not kludge and bastardize the primary name field just so multiple text versions of the name will appear on the map. It has very little value to actual driving instructions.

[sketch]

It’s been often requested to have multiple-shield-per-road display. Putting multiple names in a single field, however, will not display multiple shields, it won’t display any shields at all. So instead of a lovely I-59 shield, you’d see “I-59 N / I-20 E” and “I-59 S / I-20 W” floating above the length of the concurrency, and that’s gonna look bad.

In short, it’s not something we can accomplish just by editing differently.

Note that there’s nothing to stop from putting multiple names on entrance and exit ramps for freeways. If it’s a ramp “to I-59 N / I-20 E / Birmingham”, put that.

[CBenson]

@sketch

Putting multiple names in a single field, however, will not display multiple shields, it won’t display any shields at all. So instead of a lovely I-59 shield, you’d see “I-59 N / I-20 E” and “I-59 S / I-20 W” floating above the length of the concurrency, and that’s gonna look bad.

In short, it’s not something we can accomplish just by editing differently.

In my experience that will give you an I-59 shield. Although I don’t have a current example as all the interstates named that way around here have changed to comply with the wiki.

[sketch]

I’ve definitely seen “US-90 E / US-98 E” in the client, but that may have been when shield generation was inactive/nonfunctional/not automatic. So I suppose it’s inconclusive.

Either way.

Sent from my iPhone using Tapatalk 2