User:Lakeyboy View history

No edit summary
 
(17 intermediate revisions by the same user not shown)
Line 1: Line 1:
==Dual Carriageways==
==Freeway carriageway naming convention==
The following convention should be followed where possible, although it is acknowledged that you may need to deviate from it in some circumstances.
<span style="color:red">'''This policy was changed in February 2014'''.</span>
 
A road can be split into be 2 one-way roads if '''all''' of the following conditions are met:
# The central reservation is greater than 15m.
# There's a visible gap between the GPS traces.
# It is split by physical barrier (e.g. Grass, raised concrete, jersey barrier etc).
 
Pedestrian refuges and painted road separations (cross hatching that can be driven over) should not normally be split.
 
{| class="wikitable unsortable" style="background:#FFFCB0; font-size:80%; margin: 1em auto 1em auto" border="1"
|-
! Special Note
|-
|
Keep in mind that Waze actually works best when roads are not split, because all reports made in the app for the other carriageway on split roads are in vain, because the app currently doesn't support these kinds of reports. Road splitting used to be more common in the past, so we have since increased the conditions to be met before splitting a road.


If there is a perfectly working split road that does not meet the above stated conditions in the editor, '''don't''' unsplit it. It's a lot of work that can be put into improving other areas of the Waze map, rather than the risk of losing valuable traffic data if editing is not done correctly.
Due to changes that have been made to the Waze App in recent times which has helped improve reporting of incidents on freeways (motorways), '''compass directions <u>in addition to the road name</u> are no longer required''' when mapping any road in Waze.
|-
|}
 
==Freeway / Motorway carriageway naming convention==
<span style="color:red">'''This policy was changed in February 2014'''.</span>


Due to changes that have been made to the Waze App in recent times which has helped improve reporting of incidents on freeways and motorways, '''compass directions are no longer required''' when mapping any road in Waze.
This '''does not''' apply to roads which have a compass direction <u>in their actual name</u>.


If there are existing roads with compass directions on them, please remove them.
If there are existing roads with compass directions on them, please remove them.
Line 31: Line 12:
''Example:'' "M1 - Monash Fwy"
''Example:'' "M1 - Monash Fwy"


==Exit and Entrance ramps (on/off ramps)==
==On and Off ramps==
<span style="color:red">'''This policy was changed in February 2014'''.</span>
<span style="color:red">'''This policy was changed in February 2014'''.</span>
[[File:Melbourne Exit Numbers 1.jpg|right|thumb|250px|Exit Signage along M1 - West Gate Fwy]][[File:Melbourne Exit Numbers 2.jpg|right|thumb|250px|Exit signage along M1 - Monash Fwy]]
[[File:Melbourne Exit Numbers 1.jpg|right|thumb|250px|Exit Signage along M1 - West Gate Fwy]][[File:Melbourne Exit Numbers 2.jpg|right|thumb|250px|Exit signage along M1 - Monash Fwy]]
Line 38: Line 19:
<span style="color:red"><b>PLEASE NOTE:</b>
<span style="color:red"><b>PLEASE NOTE:</b>


<span style="color:red">Naming is only to be used for freeway / motorway style on and off ramps. Please '''do not''' add names to slip lanes on regular roads, as this is unnecessary for directions to work.</span>
<span style="color:red">Naming is only to be used for freeway style on and off ramps. Please '''do not''' add names to forks, splits or slip lanes on other types of roads, as this is unnecessary for directions to work.</span>


===Exit ramps to regular roads===
===Off ramps to non-freeway style roads and freeway to freeway ramps===


* If the exit sign shows a number as well as a street or highway name, the exit ramp should be named "Exit 15: SR16 - Police Rd".
* If the ramp exit sign shows a number as well as a street or highway name, it should be named "Exit 15: SR16 - Police Rd".
** A colon has been added because it adds a pause, which makes the Text-to-Speech directions easier to understand.
** A colon has been added because it adds a pause, which makes the Text-to-Speech directions easier to understand.
* If the exit is not numbered, "Exit to C722 - Donnybrook Rd" will do. The colon is not necessary when there is no exit number.
* If the ramp exit is not numbered, "Exit to C722 - Donnybrook Rd" will do. The colon is not necessary when there is no exit number.
* If a single exit serves multiple roads, use a slash with leading and trailing spaces: "Exit 32: Terminator Blvd / Total Recall Rd".
* If a single ramp serves multiple roads, use a slash with leading and trailing spaces: "Exits 15 / 16: SR16 - Police Rd / M3 - EastLink".
* If an exit number contains one or more letters, include it exactly as displayed on the sign: "Exit W2: ALTNR1 - Kings Way".
"Exit to SR56 - Valley Way / Princeton Rd".
* If an ramp exit number contains one or more letters, include it exactly as displayed on the sign: "Exit W2: ALTNR1 - Kings Way".
 
 
====Off ramps that '''don't have''' a fork along them====
If there is no fork along the off ramp, then place the destination(s) on the off ramp itself.
''Example:'' "Exit to C422 - Koo Wee Rup Rd to Pakenham / Koo Wee Rup"
 
====Off ramps that '''do have''' a fork along them====
For these ramps, some minor additions need to be made to the segment positioning to enable correct TTS (text to speech) instructions from the app.
*Small 90 degree angles are to made to the 2 fork segments which come out of the fork node ''(refer to Detail #1 on image below)''.
*The ramps which join the non-freeway style road need to have straight 0 degree joins at the end ''(refer to Detail #2 on image below)''. That is, the very end of the ramp needs to overlap the non-freeway style road for a few metres - achieved by dragging a geometry node from the ramp directly over the road it is joining.


===Exit ramps to another Freeway / Motorway===
The following naming conventions are to be used:
* If the exit ramp '''does not''' have a fork in it after you exit (no choice of direction after taking the exit), then use this style of naming:
"Exit to M420 - South Gippsland Fwy to Cranbourne and Hastings".


* If the exit ramp '''does''' have a fork in it after you exit (there is a choice of directions after taking the exit), then use this style of naming:
=====For the segment '''before the fork''':=====
=====For the segment '''before the fork''':=====
"Exit to M1 - Monash Fwy".
"Exit to M1 - Monash Fwy".


=====For the segments '''after the fork''':=====
=====For the segments '''after the fork''':=====
"M1 - Monash Fwy to Warragul".
"M1 - Monash Fwy to Warragul". (e.g. for one fork)
"M1 - Monash Fwy to City".


===Entrance ramps from regular roads===
"M1 - Monash Fwy to City". (e.g. for the other fork)


For entrance ramps, use this format. For example:
[[File:Australian_Interchange.jpg|center|700px|]]
* "Entry to M1 - Monash Fwy (NW)"
* "Entry to M39 - Goulburn Valley Fwy (N)"
<div style="clear:both;"></div>


==Roundabouts==
===On ramps from non-freeway style roads===


To aid navigation instructions, roundabouts should typically remain without a '''street name'''
For on ramps, use this format.  For example:
 
* "Entry to M1 - Monash Fwy to Chadstone / City"
* City: enter either suburb/city
<div style="clear:both;"></div>
* Street: Tick "None"


- where the client comes across a segment with no name it will use the next named segment as the next named instruction whilst retaining any turn signals.
===Unique scenarios===
If you encounter a uniquely designed interchange or ramp system, and not sure of the best way to name the ramps, then ask for help from other friendly Australian Waze users over on the Australian Waze Forum: [https://www.waze.com/forum/viewforum.php?f=56]


If the roundabout does have a proper, signposted name, then this can be labelled using a 'Junction/Intersection' type landmark that fills the centre of the roundabout.
===Naming===
Due to the variety of different styles of naming and destination mentioning which is on signs across the country, and due to differences in the way the text to speech in the Waze App works as well as the limited space for ramp names to display until they are cut off, slashes, the word 'and' and the word 'to' may all be substituted for each other at the editors discretion to obtain the best naming result for a particular ramp.


* For further advice, see [[Junctions and Roundabouts (Australia)| Editing Junctions and Roundabouts]]
Suburb and road names should not be shortened unless it's part of a standard Waze text to speech abbreviation. Otherwise, road names and destinations will sound incorrect when they are read out aloud.

Latest revision as of 02:27, 3 March 2014

Freeway carriageway naming convention

This policy was changed in February 2014.

Due to changes that have been made to the Waze App in recent times which has helped improve reporting of incidents on freeways (motorways), compass directions in addition to the road name are no longer required when mapping any road in Waze.

This does not apply to roads which have a compass direction in their actual name.

If there are existing roads with compass directions on them, please remove them.

All that is required is the route number (if applicable) and the name.

Example: "M1 - Monash Fwy"

On and Off ramps

This policy was changed in February 2014.

Exit Signage along M1 - West Gate Fwy
Exit signage along M1 - Monash Fwy

For the best balance between information and screen real estate, the following conventions are used. All ramps will be set as the 'ramp' type in the Waze Map Editor and be locked at the same level as the freeway which joins to them (level 5 in most cases). The route number(s) (if applicable) the name of the road and destination(s) should all be added for clear guidance to be given when using the Waze app.

PLEASE NOTE:

Naming is only to be used for freeway style on and off ramps. Please do not add names to forks, splits or slip lanes on other types of roads, as this is unnecessary for directions to work.

Off ramps to non-freeway style roads and freeway to freeway ramps

  • If the ramp exit sign shows a number as well as a street or highway name, it should be named "Exit 15: SR16 - Police Rd".
    • A colon has been added because it adds a pause, which makes the Text-to-Speech directions easier to understand.
  • If the ramp exit is not numbered, "Exit to C722 - Donnybrook Rd" will do. The colon is not necessary when there is no exit number.
  • If a single ramp serves multiple roads, use a slash with leading and trailing spaces: "Exits 15 / 16: SR16 - Police Rd / M3 - EastLink".

"Exit to SR56 - Valley Way / Princeton Rd".

  • If an ramp exit number contains one or more letters, include it exactly as displayed on the sign: "Exit W2: ALTNR1 - Kings Way".


Off ramps that don't have a fork along them

If there is no fork along the off ramp, then place the destination(s) on the off ramp itself. Example: "Exit to C422 - Koo Wee Rup Rd to Pakenham / Koo Wee Rup"

Off ramps that do have a fork along them

For these ramps, some minor additions need to be made to the segment positioning to enable correct TTS (text to speech) instructions from the app.

  • Small 90 degree angles are to made to the 2 fork segments which come out of the fork node (refer to Detail #1 on image below).
  • The ramps which join the non-freeway style road need to have straight 0 degree joins at the end (refer to Detail #2 on image below). That is, the very end of the ramp needs to overlap the non-freeway style road for a few metres - achieved by dragging a geometry node from the ramp directly over the road it is joining.

The following naming conventions are to be used:

For the segment before the fork:

"Exit to M1 - Monash Fwy".

For the segments after the fork:

"M1 - Monash Fwy to Warragul". (e.g. for one fork)

"M1 - Monash Fwy to City". (e.g. for the other fork)

On ramps from non-freeway style roads

For on ramps, use this format. For example:

  • "Entry to M1 - Monash Fwy to Chadstone / City"

Unique scenarios

If you encounter a uniquely designed interchange or ramp system, and not sure of the best way to name the ramps, then ask for help from other friendly Australian Waze users over on the Australian Waze Forum: [1]

Naming

Due to the variety of different styles of naming and destination mentioning which is on signs across the country, and due to differences in the way the text to speech in the Waze App works as well as the limited space for ramp names to display until they are cut off, slashes, the word 'and' and the word 'to' may all be substituted for each other at the editors discretion to obtain the best naming result for a particular ramp.

Suburb and road names should not be shortened unless it's part of a standard Waze text to speech abbreviation. Otherwise, road names and destinations will sound incorrect when they are read out aloud.