Page 1 of 2

Re: [Page Update] Road Names (USA)

PostPosted: Fri Jan 22, 2016 8:25 pm
by karrows
PesachZ wrote:I made the changes to correct the items I mentioned in the OP of this thread and linked to abbreviations page for the cardinal letters in names guidance.


I'm not sure about this because it is written as if it is globally true.
Where road names are the same as cardinal directions (N, S, E, W), no special modification is necessary so that the voice prompt will read the letter and not say it as a direction.

Unless something has changed very recently I didn't think this is true (I will test it). I thought this was only true for the CR-E / CH-E type abbreviations and not globally true. We have a county road that needs to be named "County E" and last time I checked this would say "East". So we use "County E."(with the period) to get it to only say "eee".

Has something changed so that "County E" will not say east?

[Page Update] Road Names (USA)

PostPosted: Mon Jun 15, 2015 9:41 pm
by PesachZ
The Road Names/USA page currently has guidance to use lowercase cardinal letters encapsulated in single quotes to avoid the letter being expanded to a cardinal direction.
Where road names are the same as cardinal directions (N, S, E, W), place the letter designator in single quotes with a lowercase letter (CR-'n' CR-'s' CR-'e' CR-'w') so that the voice prompt will read the letter and not say it as a direction. Double or triple-letter roads with directional letters (e.g. CR-EN, CR-SAL) have not been tested but might be pronounced as if a word.


This has been here for over a year, and was modified last April.

With the new voice Jane these concerns have been eliminated. A cardinal letter is only expanded if it is alone. When it is connected to a hypen such as "CH-S" it will be read as the letter S. Therefore this guidance should be completely removed.


----

The opening text of the county section reads
Text to speech on the client reads CR as "County Road." So "CR-10" is read as "County Road Ten"
there should be a hyphen after CR, making it CR-.

----

There is no other TTS abbreviation for county owned roads in any capacity. For these reasons: that county shields may someday be supported (and a named standard makes this easier to implement), and for brevity's sake in turn instructions and map displays, it is suggested (but by no means required) that individual states adopt the CR- standard.

This paragraph contradicts the following ones which state that CH- TR- and TH- are available where applicable. Therefore this paragraph should be removed as well.


Sent using Tapatalk for Android

Re: [Page Update] Road Names (USA)

PostPosted: Tue Jun 16, 2015 5:01 am
by PesachZ
I made the following change to add a missing space in the name of US-425 W. If this was no the original intent of the page it can be undone.

Sent using Tapatalk for Android

Re: [Update]Road names/USA

PostPosted: Tue Jun 16, 2015 6:23 pm
by PesachZ
No objections to the content, but this should be posted in the public wiki update forum not the WM forum.

Perhaps a forum mod can move it. It can be merged into this thread:
[Page Update] Road Names (USA)

Sent using Tapatalk for Android

Re: [Page Update] Road Names (USA)

PostPosted: Thu Jan 21, 2016 9:44 pm
by PesachZ
I made the changes to correct the items I mentioned in the OP of this thread and linked to abbreviations page for the cardinal letters in names guidance.

Re: [Page Update] Road Names (USA)

PostPosted: Fri Jan 22, 2016 9:16 pm
by PesachZ
karrows wrote:
PesachZ wrote:I made the changes to correct the items I mentioned in the OP of this thread and linked to abbreviations page for the cardinal letters in names guidance.


I'm not sure about this because it is written as if it is globally true.
Where road names are the same as cardinal directions (N, S, E, W), no special modification is necessary so that the voice prompt will read the letter and not say it as a direction.

Unless something has changed very recently I didn't think this is true (I will test it). I thought this was only true for the CR-E / CH-E type abbreviations and not globally true. We have a county road that needs to be named "County E" and last time I checked this would say "East". So we use "County E."(with the period) to get it to only say "eee".

Has something changed so that "County E" will not say east?

"County E" is not following any of the recommended formats in the section, and yes it will say east. This is why I added the link to the abbreviations page which explains to use E. in that case (assuming CH-E or CR-E are for reason inappropriate for that road?)

This is replacing text which suggested using County 'e' which is wrong from any angle.

Sent from Android using Tapatalk

Re: [Page Update] Road Names (USA)

PostPosted: Fri Jan 22, 2016 9:21 pm
by PesachZ
sketch wrote:No, it should be worded more carefully, though—that applies to numbered ("lettered") highways and roadways with the format AB-LLLL such as CR-N and SR-QQQQ, but not to any old road name such as Avenue E or George W Carver.

"Any name using one of the following recommended short format names. For others names see the abbreviations link"

Does that work well (obviously wordsmithed a bit)?

Sent from Android using Tapatalk

Re: [Page Update] Road Names (USA)

PostPosted: Fri Jan 22, 2016 9:18 pm
by sketch
No, it should be worded more carefully, though—that applies to numbered ("lettered") highways and roadways with the format AB-LLLL such as CR-N and SR-QQQQ, but not to any old road name such as Avenue E or George W Carver.

[Update]Road names/USA

PostPosted: Tue Jun 16, 2015 5:53 pm
by voludu2
I made the following changes already -- a small correction bringing the page up-to-date with the latest version of WME -- "none" instead of "no city" or "no name"

https://wiki.waze.com/wiki/Road_names/U ... _red_roads
https://wiki.waze.com/wiki/index.php?ti ... did=110431

Re: [Update]Road names/USA

PostPosted: Tue Jun 16, 2015 6:00 pm
by voludu2
I would like to make the following change to this page:

https://wiki.waze.com/wiki/Road_names/U ... _red_roads
from
Until you do this, your road will not be routable and will not show on the client map. These incomplete segments are colored bright red in WME.

This must be done on all streets created in WME, and on all streets created with the client "Pave" function.

"Paved" streets must also be connected to their adjacent roads, and [[Creating and editing road segments#Set allowed turns .28connections.29 turn restrictions|turn restrictions]] must be set in order to be routable.

to
These incomplete segments are colored bright red in WME. This must be done on all streets, whether they are created in WME or with the mobile app "Pave" function. These streets must also be properly connected to the road system and [[Creating and editing road segments#Set allowed turns .28connections.29 turn restrictions|turn restrictions]] must be set in order for the roads to be routable.

Streets created with the mobile app "Pave" function will not show up in the mobile app and will not be used by the waze router until they are edited in WME.


I want to make this change because the current wording says that red roads created in WME will not be routable and will not show up in the clients. This is incorrect. As long as roads have been edited in WME, they will show up in the clients and used in routing.

If there are no objections, I will aim to make the change by 19 June.