Main Page: Difference between revisions View history

VisualWikitext
(Commencing major redevelopment of the home page)
(Part two of major rewrite)
Line 55: Line 55:
}}
}}


==What The Australian Community Expects From You==
==Australia's Expectations DRAFT==
''This paragraph serves as a guideline for all Wazers, willing to contribute to the Australian map.''
*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 [[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.


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.
[[Image:sheriff.png|center|400px]]


*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:Main_Page|global Wiki]].
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.
 
*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]]
 
*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.
 
[[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:
==Revised Waze Editing Philosophy DRAFT==
The community is leading the upgrades to the Waze map to facilitate the new snapper technology. These are the revised principles we need to keep in mind whenever we make a change to the map:


*extra clutter on the map as seen in the app
====Usability====
*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
The Waze map is '''intended for navigation purposes only;''' it is not a general-purpose mapping application. We only make changes to the map that will add value to a driver using the app.
*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.
====Representative of Reality====
The map needs to be as accurate as possible and representative of reality: '''the position of the segment on the road, and the direction / angle of intersecting segments.''' Segments that do not meet these new principles could make the snapper hiccup, switch the arrow to another segment/route, and cause a poor user experience.


There are a number of guidelines that have been developed to meet these goals:
====Only a Map====
We are '''moving away from using the map as a way to control the app.''' A map should be a map; it should be accurate and represent the world.


#We do not represent roads as parallel one-way sections unless it's really needed. See '''[[australia:Road_Attributes#Dual_Carriageways|Dual Carriageways]]'''
====Retention====
#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''']
The map stores an average time / speed it takes a driver to traverse a segment, for every 30 min block in a day, for seven days a week. This data is used for route optimisation and selection. When a segment is deleted, this data is lost. '''Given a choice between deleting or reusing a segment, it is better to "recycle" it.'''
#'''DON'T''' map every lane of a parking lot. Only map the parking-lot roads necessary to ensure proper routing to and from destinations, and the perimeter lane when necessary so that parking lot traffic will not be detected as slow traffic on an adjacent road. See [https://wazeopedia.waze.com/wiki/Australia/Talk:Australian_Road_Names#Mapping_parking_lot_roads '''Mapping 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''']
#Bike paths, hiking trails or other walkways that do not benefit drivers should not be mapped. 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].
====Simplicity====
We should '''avoid unnecessary complexity and clutter''' because it increases the risk of introducing errors, maintenance, and the learning curve (making it harder for new editors to get involved).


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.
====Communication and Documentation====
An edit made one day, may not be clear a year later through the eyes of another editor. All editors are strongly encouraged to '''add map comments to explain unique or complex scenarios.''' E.g. increasing the lock level of a road, adding a plus intersection (+) where the satellite and street view images show a roundabout.


==About Waze==
==About Waze==
{{Global::Main/About Waze}}
{{Global::Main/About Waze}}

Revision as of 00:58, 28 August 2021

G'day, welcome to Wazeopedia Australia!

I'm new here... Mapping in Australia
General Topics Mapping Topics
This wiki should only be adjusted with the permission of the Australia leadership team.

Australia's Expectations DRAFT

  • 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.

Revised Waze Editing Philosophy DRAFT

The community is leading the upgrades to the Waze map to facilitate the new snapper technology. These are the revised principles we need to keep in mind whenever we make a change to the map:

Usability

The Waze map is intended for navigation purposes only; it is not a general-purpose mapping application. We only make changes to the map that will add value to a driver using the app.

Representative of Reality

The map needs to be as accurate as possible and representative of reality: the position of the segment on the road, and the direction / angle of intersecting segments. Segments that do not meet these new principles could make the snapper hiccup, switch the arrow to another segment/route, and cause a poor user experience.

Only a Map

We are moving away from using the map as a way to control the app. A map should be a map; it should be accurate and represent the world.

Retention

The map stores an average time / speed it takes a driver to traverse a segment, for every 30 min block in a day, for seven days a week. This data is used for route optimisation and selection. When a segment is deleted, this data is lost. Given a choice between deleting or reusing a segment, it is better to "recycle" it.

Simplicity

We should avoid unnecessary complexity and clutter because it increases the risk of introducing errors, maintenance, and the learning curve (making it harder for new editors to get involved).

Communication and Documentation

An edit made one day, may not be clear a year later through the eyes of another editor. All editors are strongly encouraged to add map comments to explain unique or complex scenarios. E.g. increasing the lock level of a road, adding a plus intersection (+) where the satellite and street view images show a roundabout.

About Waze

301 Moved Permanently

301 Moved Permanently

nginx

Retrieved from ‘https://www.waze.com/wiki/Australia/index.php?title=Main_Page&oldid=11541’