Main Page: Difference between revisions View history

(Clarify copyright wording)
(39 intermediate revisions by 8 users not shown)
Line 1: Line 1:
Welcome to Australia!
= G'day, Welcome to Wazeopedia Australia! =
This vital resource serves to explain the unique editing rules that apply to all editors working on the Australian maps.


Here you will find information on local Australian application and editing rules.
Are you a brand new editor to Waze? Take a look at the [[New Editor Landing Page|Waze Australia onboard process.]]
 
==About Waze==
{{Global::Main/About Waze}}


== What The Australian Community Expects From You ==
== What The Australian Community Expects From You ==
''This para serves as a guideline for all Wazers, willing to contribute to the Australian map.''
''This para serves as a guideline for all Wazers, willing to contribute to the Australian map.''


Basically we follow general practicies, and as an english speaking country we don't need translation of general content. Nevertheless we  
Basically we follow general practices, and as an English speaking country we don't need translation of general content. Nevertheless we here in Australia decided to state, how we would like to see the work done.
here in Australia decided to state, how we would like to see the  
work done.


* Every Wazer, regardless of their rank or origin, is encouraged and welcome to contribute to the Australian map. Nonetheless everyone is  required to act in the here-stated manner and to follow the rules as  stated in the Australian Wiki. Any rules/guidelines not covered herein  will be available in the global Wiki.


* Contributers to the Australian map are also welcome to add the  graphic to their (forum) signature to show their affiliation to the  Australian Waze Community.[[image:AuSig.png|center]]


* Every Wazer, regardless of their rank or origin, is encouraged and  welcome to contribute to the Australian map. Nonetheless everyone is  required to act in the here-stated manner and to follow the rules as  stated in the Australian Wiki. Any rules/guidelines not covered herein  will be available in the global Wiki<br><br>
* We expect all map editors to regularly visit the Australian forum.  Though we would appreciate a post from you too, you're not required to  participate in the forum, but to keep in touch with the thoughts and  various projects running in our community (i.e Servos, that's what we  call a Petrol/Gas station here)
 
* Contributers to the Australian map are also welcome to add the  graphic to their (forum)signature to show their affiliation to the  Australian Waze Community<br><br>
 
* We expect all map editors to regularly visit the Australian forum.  Though we would appreciate a post from you too, you're not required to  participate in the forum, but to keep in touch with the thoughts and  various projects running in our community (i.e Servos, that's what we  call a Petrol/Gas station here)<br><br>


* Always keep in mind, that everyone of us is voluntarily giving  their time to Waze. No-one is a Waze employee, so please respect that  everybody has a private life too and consider this when expecting an  answer - be it in the Forum or PM.
* Always keep in mind, that everyone of us is voluntarily giving  their time to Waze. No-one is a Waze employee, so please respect that  everybody has a private life too and consider this when expecting an  answer - be it in the Forum or PM.


* Work together and not against one another. Always look at the time  stamp, when considering to change existing elements. If it has been  edited recently, it might still be under construction by the last  editor. If you think, something has to be done immediately please get in  contact with the last editor via PM.
* Work together and not against one another. Always look at the time  stamp, when considering to change existing elements. If it has been  edited recently, it might still be under construction by the last  editor. If you think, something has to be done immediately please get in  contact with the last editor via PM.


* Don't leave "loose ends". The last editor of a segment is  responsible for it. So if you choose to create a new segment or edit an  existing make sure that you make it ready by adding street- and city  name, proper label, turn restrictions. We don't expect you to do all at  once - sometimes you will have to look for additional information or a  feedback from the editor before you, but ensure to make all necessary  adjustments at least within a month. Just performing slight geometry  changes to snap off some points and edits is not our style here.
* Don't leave "loose ends". The last editor of a segment is  responsible for it. So if you choose to create a new segment or edit an  existing make sure that you make it ready by adding street- and city  name, proper label, turn restrictions. We don't expect you to do all at  once - sometimes you will have to look for additional information or a  feedback from the editor before you, but ensure to make all necessary  adjustments at least within a month. Just performing slight geometry  changes to snap off some points and edits is not our style here.
** '''Special note:''' Special note: In accordance with the  implementation of Google search and to get a working road grid as soon  as possible, guest editors, wide area managers and country managers may  choose to use the "no name" option when naming a street (or lower) to  make them routeable. To prevent smudged cities the city names are to be  applied all times. Local editors are encouraged to add the proper street  names as they see able to.
** '''Special note:''' In accordance with the  implementation of Google search and to get a working road grid as soon  as possible, guest editors, wide area managers and country managers may  choose to use the "no name" option when naming a street (or lower) to  make them routable. To prevent smudged cities the city names are to be  applied all times. Local editors are encouraged to add the proper street  names as they see able to.
 
 


* We expect that all activities concerning Waze in Australia are  carried out in a spirit of mutual respect and we want you to show it. So  keep the wording nice and friendly - and don't be shy using the "thank  you"-button if you get an answer to a question or help with a problem.
* We expect that all activities concerning Waze in Australia are  carried out in a spirit of mutual respect and we want you to show it. So  keep the wording nice and friendly - and don't be shy using the "thank  you"-button if you get an answer to a question or help with a problem.


[[Image:sheriff.png|center|400px]]
== Waze Editing Philosophy ==
It's important to understand the purpose of Waze. Waze is NOT a general-purpose mapping application. It is designed specifically to assist drivers of motor vehicles to navigate to their objectives and to avoid traffic. In other words, it is a NAVIGATION app. The Waze map is not a topographic map; it is a specialised diagram providing navigation information. Edits to the map that do not support these goals in some way are strongly discouraged. Edits that detract from these goals, even unintentionally, do not belong at all. (See [https://wazeopedia.waze.com/wiki/USA/Edits_to_avoid#Misunderstanding_Waze.27s_purpose. Misunderstanding Waze's purpose]).


This is hinted at in the first two [https://wazeopedia.waze.com/wiki/Global/Best_map_editing_practice#Overall_Goals goals of Waze map editing] - '''usability''' and '''simplicity'''. The map has to work for navigation, and it has to be no more complex than is needed to achieve that. Every extra road segment carries with it a number of costs:
* extra clutter on the map as seen in the app
* extra processing in the mobile device to determine which of many segments best matches the current position estimate, and to display the segments, resulting in extra heat and shorter battery life
* extra bandwidth needed to transfer the data to the app
* the big one: extra complexity for the routing server, potentially causing it to be unable to find a route in the time available<br />


== Update Request (URs) ==
The cost for a single extra segment may not be significant, but when there is a high proportion of unnecessary segments, the cumulative cost becomes a concern.
As it turns out to be a matter on constant annoyance:
 
Pay particular attention to the etiquette of adding to the  
conversation, closing a UR that another editor is working on, and so on.


In the past, there have been a rash of editors giving long winded
There are a number of guidelines that have been developed to meet these goals:
responses to URs. The average person is not going to read beyond the 3rd
# We do not represent roads as parallel one-way sections unless it's really needed. See [https://wazeopedia.waze.com/wiki/Australia/Australian_Road_Names#Dual_Carriageways '''Dual Carriageways''']
<nowiki> </nowiki>or 4th line. In this example:
# We do not split roads into a Y-shape where they meet a roundabout. See [https://wiki.waze.com/wiki/Junctions_and_Roundabouts_(Australia)#Roundabouts '''Roundabouts''']
# We do not map every lane of a parking lot. See [https://wazeopedia.waze.com/wiki/USA/Edits_to_avoid#Excessive_use_of_Parking-Lot_Roads '''Parking Lot Roads''']
# We do not map turn lanes unless they are really needed. See [https://wazeopedia.waze.com/wiki/Global/At-grade_connectors#Should_the_connector_be_mapped.3F '''Should the connector be mapped''']
# Most hiking and bicycling paths should not be on the map at all. See [https://wazeopedia.waze.com/wiki/USA/Pedestrian_path '''Pedestrian Paths''']
# In general, there is no reason to have multiple rail lines mapped. See [https://wazeopedia.waze.com/wiki/USA/Road_types#Railroad '''Railroads''']
# We don't map small loops at the end of dead-end segments. See [https://wazeopedia.waze.com/wiki/Global/Junction_Style_Guide#Cul-de-sacs '''Cul-de-sacs''']
# We don't map short driveways. See [https://wazeopedia.waze.com/wiki/USA/Driveways '''Driveways''']
# Don't fiddle with angles or distances near intersections until you thoroughly understand [https://wazeopedia.waze.com/wiki/Global/Routing_penalties/Controlling_U-turn_penalties '''U-turn prevention'''] and [https://wazeopedia.waze.com/wiki/Global/How_Waze_determines_turn_/_keep_/_exit_maneuvers '''How Waze determines turn instructions''']. The details at those references are more complex than they appear at first, and even a small change (for example, to align the road segment on the map with the road shown on the aerial photography) can cause Waze to issue misleading turn instructions or even direct the driver though an illegal turn.
A good rule to bear in mind is: will the map generate the right instructions without the change I'm thinking of? If you are uncertain, ask for advice in the [https://www.waze.com/forum/viewforum.php?f=56 Australia forums].


''"Many drivers think a report shows their destination and route
New editors are often keen to add as much as possible to the map. The reality is that the established metro areas have been pretty comprehensively mapped, and you're unlikely to find much that needs doing. Focus on new housing developments, where the Waze map hasn't caught up. Oh, and remember that you mustn't copy information from other maps, only from what Waze provides in the map editor or you see in real life. See [https://wazeopedia.waze.com/wiki/Global/External_sources External Sources] and [https://wazeopedia.waze.com/wiki/Global/Waze_Map_Editor#Using_External_sources_.28such_as_Google_Imagery.29 Map Editor - External Sources]. We have permission from Waze to use Government announcements of road closures when updating the map.
<nowiki> </nowiki>information, it doesn't. It doesn't even tell us who filed the report.
We volunteer map editors only see where you are when you start your
report and short pieces of the recommended and driven routes. We need
more information to fix your problem. Thank you for the report and all
the WAZE you help. If you respond to my query and I do not acknowledge
within 1 day, please e-mail me at xxxxxxxxx@waze.com with a repeat of  
the information.
This report will be closed as 'not identified' if there is no response
within 7 days."''


== Topic List ==


and this example:
=== Waze General ===
* [[Country Managers|Who are your country managers in Australia?]]
* [https://www.waze.com/forum/viewtopic.php?f=56&t=268601 Country management roles (under development)]
* [[Global:Area Manager|Application for Area Manager]]
* [[Global:Glossary|Glossary]]


=== Roads and Cities ===
* [[Australian City Names|City Names]]
** [[Australian Duplicate Cities|Duplicate Cities]]
* [[Abbreviations and Acronyms]]


''"Please provide more details so we can investigate the "General
* [[Road Attributes]]
error" you reported. Volunteer map editors only fix map problem. We
** [[Australian Road Names|Road Names]]
don't see what you see on your screen. We only see where you were
located when you started your report and a short segment of the WAZE
recommended route and a short segment of the route taken.
To test the routing, we need to know the approximate start and end
points of your route.
Your routing options are important. Do you Avoid toll roads? Avoid major
<nowiki> </nowiki>highways? Dirt roads allow/don't allow/avoid long ones?
Have you selected 'fastest route' or 'shortest route'?
Thank you for the report and all the WAZE you help.
If no response within 7 days, this report will be closed as 'Not
identified'."''


the user will most likely either not get beyond the "We need more
* [[Cameras]]
<nowiki> </nowiki>information to fix your problem" or they will skim through it and not
pay attention to what is being asked of them. Please keep responses to
URs at a minimum. Asking someone to explain more information about their
<nowiki> </nowiki>issue does not require a novel, it should read like the box score to a
game in the newspaper.


A shorter, more to the point response should suffice. An example:
=== Places ===
* [[Australian Place Style Guide|Places Style Guide]]


''"You reported a general error at ______________________ and
=== Update Requests (URs) ===
______________________ but left no info as to what's wrong. Can you
* Global [[global:Update Requests in Waze Map Editor|Update Requests in Waze Map Editor]] Policy
please elaborate, so we may look into and resolve the issue? Thank you."''
* [[UR Management]]


or
=== New Editor Induction Material ===
* [[New Editor Landing Page|New Editor Onboarding Wizard]] (Short Link for URs: http://bit.ly/WazeEditOz)


''"You reported a missing road, but didn't tell us the name of
=== Scripts ===
the road. Could you please give us the name, so we may add it to the
* [[Australian Scripts]]
map? Thank you."''


These are short, simple, to the point, and don't bother the
=== Communication Platforms ===
driver with useless information about satellites, sun spots, the
* [https://www.waze.com/forum/viewforum.php?f=56 Australia Forums]
curvature of Earth's horizon in relation to Mars' gravitational pull, or
** [https://www.waze.com/forum/viewforum.php?f=406 AU Unlock Forums]
<nowiki> </nowiki>other weird explanations from editors which have popped up on URs.
* [https://www.waze.com/forum/viewtopic.php?f=56&t=257551 Waze Australia Discord Server]

Revision as of 01:27, 21 March 2019

G'day, Welcome to Wazeopedia Australia!

This vital resource serves to explain the unique editing rules that apply to all editors working on the Australian maps.

Are you a brand new editor to Waze? Take a look at the Waze Australia onboard process.

About Waze

301 Moved Permanently

301 Moved Permanently


nginx


What The Australian Community Expects From You

This para serves as a guideline for all Wazers, willing to contribute to the Australian map.

Basically we follow general practices, and as an English speaking country we don't need translation of general content. Nevertheless we here in Australia decided to state, how we would like to see the work done.

  • Every Wazer, regardless of their rank or origin, is encouraged and welcome to contribute to the Australian map. Nonetheless everyone is required to act in the here-stated manner and to follow the rules as stated in the Australian Wiki. Any rules/guidelines not covered herein will be available in the global Wiki.
  • Contributers to the Australian map are also welcome to add the graphic to their (forum) signature to show their affiliation to the Australian Waze Community.
  • We expect all map editors to regularly visit the Australian forum. Though we would appreciate a post from you too, you're not required to participate in the forum, but to keep in touch with the thoughts and various projects running in our community (i.e Servos, that's what we call a Petrol/Gas station here)
  • Always keep in mind, that everyone of us is voluntarily giving their time to Waze. No-one is a Waze employee, so please respect that everybody has a private life too and consider this when expecting an answer - be it in the Forum or PM.
  • Work together and not against one another. Always look at the time stamp, when considering to change existing elements. If it has been edited recently, it might still be under construction by the last editor. If you think, something has to be done immediately please get in contact with the last editor via PM.
  • Don't leave "loose ends". The last editor of a segment is responsible for it. So if you choose to create a new segment or edit an existing make sure that you make it ready by adding street- and city name, proper label, turn restrictions. We don't expect you to do all at once - sometimes you will have to look for additional information or a feedback from the editor before you, but ensure to make all necessary adjustments at least within a month. Just performing slight geometry changes to snap off some points and edits is not our style here.
    • Special note: In accordance with the implementation of Google search and to get a working road grid as soon as possible, guest editors, wide area managers and country managers may choose to use the "no name" option when naming a street (or lower) to make them routable. To prevent smudged cities the city names are to be applied all times. Local editors are encouraged to add the proper street names as they see able to.
  • We expect that all activities concerning Waze in Australia are carried out in a spirit of mutual respect and we want you to show it. So keep the wording nice and friendly - and don't be shy using the "thank you"-button if you get an answer to a question or help with a problem.

Waze Editing Philosophy

It's important to understand the purpose of Waze. Waze is NOT a general-purpose mapping application. It is designed specifically to assist drivers of motor vehicles to navigate to their objectives and to avoid traffic. In other words, it is a NAVIGATION app. The Waze map is not a topographic map; it is a specialised diagram providing navigation information. Edits to the map that do not support these goals in some way are strongly discouraged. Edits that detract from these goals, even unintentionally, do not belong at all. (See Misunderstanding Waze's purpose).

This is hinted at in the first two goals of Waze map editing - usability and simplicity. The map has to work for navigation, and it has to be no more complex than is needed to achieve that. Every extra road segment carries with it a number of costs:

  • extra clutter on the map as seen in the app
  • extra processing in the mobile device to determine which of many segments best matches the current position estimate, and to display the segments, resulting in extra heat and shorter battery life
  • extra bandwidth needed to transfer the data to the app
  • the big one: extra complexity for the routing server, potentially causing it to be unable to find a route in the time available

The cost for a single extra segment may not be significant, but when there is a high proportion of unnecessary segments, the cumulative cost becomes a concern.

There are a number of guidelines that have been developed to meet these goals:

  1. We do not represent roads as parallel one-way sections unless it's really needed. See Dual Carriageways
  2. We do not split roads into a Y-shape where they meet a roundabout. See Roundabouts
  3. We do not map every lane of a parking lot. See Parking Lot Roads
  4. We do not map turn lanes unless they are really needed. See Should the connector be mapped
  5. Most hiking and bicycling paths should not be on the map at all. See Pedestrian Paths
  6. In general, there is no reason to have multiple rail lines mapped. See Railroads
  7. We don't map small loops at the end of dead-end segments. See Cul-de-sacs
  8. We don't map short driveways. See Driveways
  9. Don't fiddle with angles or distances near intersections until you thoroughly understand U-turn prevention and How Waze determines turn instructions. The details at those references are more complex than they appear at first, and even a small change (for example, to align the road segment on the map with the road shown on the aerial photography) can cause Waze to issue misleading turn instructions or even direct the driver though an illegal turn.

A good rule to bear in mind is: will the map generate the right instructions without the change I'm thinking of? If you are uncertain, ask for advice in the Australia forums.

New editors are often keen to add as much as possible to the map. The reality is that the established metro areas have been pretty comprehensively mapped, and you're unlikely to find much that needs doing. Focus on new housing developments, where the Waze map hasn't caught up. Oh, and remember that you mustn't copy information from other maps, only from what Waze provides in the map editor or you see in real life. See External Sources and Map Editor - External Sources. We have permission from Waze to use Government announcements of road closures when updating the map.