Main Page: Difference between revisions View history

(→‎Speed and Red Light Cameras: Updated per https://www.waze.com/forum/viewtopic.php?f=56&t=256193 and clarified requirements for L4+. Styling changes.)
(Add PH to main page)
 
(65 intermediate revisions by 9 users not shown)
Line 1: Line 1:
= G'day, Welcome to Wazeopedia Australia! =
{{DISPLAYTITLE:<span style="position: absolute; clip: rect(1px 1px 1px 1px); clip: rect(1px, 1px, 1px, 1px);">{{FULLPAGENAME}}</span>}}
This vital resources serves to explain the unique editing rules that apply to all editors working on the Australian maps.
=Wazeopedia Australia=
__NOTOC__
{{mbox
| type      = info
| small      = left
| textstyle  =
| text  = '''Can't find what you're looking for here?''' Check the [[Global:Main Page|Global wiki]], and if it isn't there, check the [[USA:Main Page|USA wiki]]. Still lost? Check with the community on the [https://www.waze.com/forum/viewforum.php?f=56 Australia forums] or [https://www.waze.com/forum/viewtopic.php?f=56&t=257551 Discord] server.
| smalltext  = Text for the top of article sections.
}}
{| style="width: 100%;"
|- style="width: 50%; text-align: center; background-color:#3bcffc; font-weight:bold;"
!I'm new here...
! style="width: 50%; text-align: center; background-color:#31e598; font-weight:bold;" |Mapping in Australia
|- style="font-weight:normal; vertical-align:top;"
|
*[[New Editor Landing Page|New editor onboarding wizard]] (Short Link for URs: http://bit.ly/WazeEditOz)
*[https://www.waze.com/forum/viewtopic.php?f=56&t=50809 Introduce yourself]
*[https://www.waze.com/forum/viewforum.php?f=56 Australian forums]
**[https://www.waze.com/forum/viewforum.php?f=406 Unlock forums] | [https://www.waze.com/forum/viewforum.php?f=408 ACT] | [https://www.waze.com/forum/viewforum.php?f=393 NSW] | [https://www.waze.com/forum/viewforum.php?f=409 NT] | [https://www.waze.com/forum/viewforum.php?f=402 QLD] | [https://www.waze.com/forum/viewforum.php?f=404 SA] | [https://www.waze.com/forum/viewforum.php?f=405 TAS]| [https://www.waze.com/forum/viewforum.php?f=403 VIC] | [https://www.waze.com/forum/viewforum.php?f=396 WA]
*[https://www.waze.com/forum/viewtopic.php?f=56&t=257551 Waze Australia Discord server]
*[[global:Glossary|Glossary]]
|
*[[#Australia's Expectations|Australia's Expectations]]
*[[New technology, new mapping standards#Revised Waze Editing Philosophy|Revised Waze Editing Philosophy]]
*[[#Language and Terminology|Language and Terminology]]
*[[Australian Scripts|Australian scripts]]
*[https://docs.google.com/spreadsheets/d/e/2PACX-1vSePCdQ_a1C-Vgb7wVGqBhIEfOPhzG-Yf9QayPxqsSUJDucT08mtgs1quL9WmvT3X2VpmnfI7HIPMtk/pubhtml?gid=2045175533&single=true Links sheet to every resource]
*[[Mapping videos|Essential skills videos]]
|- style="width: 50%; text-align: center; background-color:#9447f9; font-weight:bold;"
|General Topics
| style="width: 50%; text-align: center; background-color:#fce165; font-weight:bold;" |Mapping Topics
|- style="font-weight:normal; vertical-align:top;"
|
*[[Editing levels and roles#Area manager|Application for Area Manager]]
*[[Community Leaders|Country leadership team]]
*[[Country specific permissions]]
*[[Editing levels and roles]]
*[[External Data / Third-Party Sources Policy]]
**[[How to use third-party data sources]]
*[[Knowledge Sharing|Knowledge sharing]]
*[[Request a text-to-speech (TTS) change]]
*[[The Waze Community|The Waze Community]]
*Wazeopedia: [[global:Main Page|Global]] | [[usa:Main Page|USA]]


Are a you a brand new editor to Waze? Take a look at the [[New Editor Landing Page|Waze Australia onboard process.]]
|
*[[Abbreviations and Acronyms]]
*[[Permanent Hazards]]
**[[Cameras]]
**[[Railway Crossing Alerts]]
*[[Australian City Names|City Names]]
*[[Australian Duplicate Cities|Duplicate Cities]]
*[[EV Charging Stations]]
*[[Footpaths / Walking segments]]
*[[New technology, new mapping standards]]
*[[Australian Place Style Guide|Places Style Guide]]
*'''Roads'''
**[[Road Attributes]]
**[[Australian Road Types & Naming|Road Types & Naming]]
**[[Toll Pricing Project]]
**[[Turn instructions]]
***[[Lane Guidance]]
*[[Update Requests (URs)]]
|}


==About Waze==
{{mbox
{{Global::Main/About Waze}}
| type      = protection
| small      = left
| textstyle  =  
| text  = This wiki should only be adjusted with the permission of the Australia leadership team.
| smalltext  = Text for the top of article sections.
}}


== What The Australian Community Expects From You ==
==Australia's Expectations==
''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.
*Everyone is welcome to contribute to the Waze Australia map, but is required to follow the local rules, mapping standards and terminology as listed here in the Australian Wiki. Any rules/guidelines not covered herein will be available in the global Wiki.
 
*We occasionally make changes to standards which you need to keep apprised of. Changes as well as other announcements are often found in the Australian forums or Waze Australia Discord server.
* 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.
*Any edit made is to improve the quality of the map for the benefit of Waze app users. If your edit is not going to value add, it is not welcome.
 
*If you don’t know or you’re not sure, check out this wiki, ask on the forums or Discord, or approach your editing mentor. Do not make an edit that risks damaging the map.
* 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 volunteer Waze editor needs to acknowledge they are working as a part of a larger team, all working towards the same goal. It is therefore vital we work together, and not against each other.
 
*A component of teamwork is communication - for example, reading and responding to forum messages and emails, visiting the forum to view news and announcements, joining discussions on Discord, providing and receiving feedback, and working with local area, state and country managers.
* 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)
*Do not take over a segment or area already being worked on. Check segment timestamps and look out for map comments (turn the layer on in WME). Reach out to other editors first to ensure you’re not damaging their contributions. You can reach out to them via forum PM or the Discord server.
 
*When you edit a segment, you become responsible for ensuring it is correct and complete. Make sure:
* 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.
**The segment position and angles are realistically mapped
 
**The segment is connected correctly to other segments
* 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.
**A name, city and state is applied, where known
 
**Check turns to other segments are correct
* 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.
**Speed limits are applied
** '''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.
**It is locked to the correct level
 
**Lane guidance is applied, where applicable.
* 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.
*You do not copy external data or information from other data sources (maps, websites, etc.) unless it meets our [[External Data / Third-Party Sources Policy|strict external data policy]].
*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 use the "thank you" on the forums and Discord if someone helps you.


[[Image:sheriff.png|center|400px]]
[[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 />
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:
* 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]
* 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]
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].
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 you can see in the editor or 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].
== Update Request (URs) ==
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
responses to URs. The average person is not going to read beyond the 3rd
<nowiki> </nowiki>or 4th line. In this example:
''"Many drivers think a report shows their destination and route
<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."''
and this example:
''"Please provide more details so we can investigate the "General
error" you reported. Volunteer map editors only fix map problem. We
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
<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:
''"You reported a general error at ______________________ and
______________________ but left no info as to what's wrong. Can you
please elaborate, so we may look into and resolve the issue? Thank you."''
or
''"You reported a missing road, but didn't tell us the name of
the road. Could you please give us the name, so we may add it to the
map? Thank you."''
These are short, simple, to the point, and don't bother the
driver with useless information about satellites, sun spots, the
curvature of Earth's horizon in relation to Mars' gravitational pull, or
<nowiki> </nowiki>other weird explanations from editors which have popped up on URs.
==Speed and Red Light Cameras==
The usual lock level for confirmed cameras of all types should be Level 3. A higher level may be set if necessary to prevent repeated vandalism or incorrect edits.
'''Level 4+ editors:''' are reminded that the map editor currently defaults to "Auto" lock level, which sets the lock to the level of the editor - that is, too high. ''Please check all cameras you see and adjust them to Level 3.''
'''For dual red-light/speed camera / safety cameras:''' These must be configured to camera type red light camera, and set to speed of 0, to ensure that the camera provides a consistent red-light warning. (This convention will be revised if/when the app is changed to provide both warnings for a dual-function camera [https://www.waze.com/forum/viewtopic.php?f=56&t=256193 per forum discussion].)
'''Note that there is no point in adding another camera to produce the speed alert, as a second camera within about 400 metres will not alert.'''
==Recent Imports==
These pages have been recently added and need verification that their links and information are still correct.
Please discuss further in the [https://www.waze.com/forum/viewforum.php?f=56 Waze Australia Forums].
[[Australian City Names]]
[[Australian Duplicate Cities]]
[[Abbreviations and Acronyms]]
[[Australian Road Names]]


== Newly Added ==
Your edits are visible for all to see, in addition to active monitoring by area, state and country managers. If you do not meet these expectations, you can anticipate contact via forum private message or on the Waze Australia Discord server. Rapid improvement is required, or the Australian management team will be forced to take action against your account to remove privileges, rank, editing area, and editing abilities. Sanctions against your account will follow you in any country you edit in.
These pages are new to Australian Guidance. Please remember that Australian Guidance if it exists takes precedence over all others when editing in Australia.


[[Australian Place Style Guide]]
==Language and Terminology==
When editing in Australia, please ensure your Waze Map Editor (WME) settings are configured to '''metric units''' and the '''English (Australia) language.''' Other settings illustrated below are also highly recommended.
[[File:Wme-settings-for-australia.png|alt=|center]]

Latest revision as of 04:26, 17 February 2024

Australia's Expectations

  • Everyone is welcome to contribute to the Waze Australia map, but is required to follow the local rules, mapping standards and terminology as listed here in the Australian Wiki. Any rules/guidelines not covered herein will be available in the global Wiki.
  • We occasionally make changes to standards which you need to keep apprised of. Changes as well as other announcements are often found in the Australian forums or Waze Australia Discord server.
  • Any edit made is to improve the quality of the map for the benefit of Waze app users. If your edit is not going to value add, it is not welcome.
  • If you don’t know or you’re not sure, check out this wiki, ask on the forums or Discord, or approach your editing mentor. Do not make an edit that risks damaging the map.
  • Every volunteer Waze editor needs to acknowledge they are working as a part of a larger team, all working towards the same goal. It is therefore vital we work together, and not against each other.
  • A component of teamwork is communication - for example, reading and responding to forum messages and emails, visiting the forum to view news and announcements, joining discussions on Discord, providing and receiving feedback, and working with local area, state and country managers.
  • Do not take over a segment or area already being worked on. Check segment timestamps and look out for map comments (turn the layer on in WME). Reach out to other editors first to ensure you’re not damaging their contributions. You can reach out to them via forum PM or the Discord server.
  • When you edit a segment, you become responsible for ensuring it is correct and complete. Make sure:
    • The segment position and angles are realistically mapped
    • The segment is connected correctly to other segments
    • A name, city and state is applied, where known
    • Check turns to other segments are correct
    • Speed limits are applied
    • It is locked to the correct level
    • Lane guidance is applied, where applicable.
  • You do not copy external data or information from other data sources (maps, websites, etc.) unless it meets our strict external data policy.
  • 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 use the "thank you" on the forums and Discord if someone helps you.

Your edits are visible for all to see, in addition to active monitoring by area, state and country managers. If you do not meet these expectations, you can anticipate contact via forum private message or on the Waze Australia Discord server. Rapid improvement is required, or the Australian management team will be forced to take action against your account to remove privileges, rank, editing area, and editing abilities. Sanctions against your account will follow you in any country you edit in.

Language and Terminology

When editing in Australia, please ensure your Waze Map Editor (WME) settings are configured to metric units and the English (Australia) language. Other settings illustrated below are also highly recommended.