User:LostInMyMaps/Australia Main Page Rewrite 2020

G'day, Welcome to Wazeopedia Australia!

Please do not edit any of these pages without Country Management permission.

I'm new here...	Mapping in Australia
New editor onboarding wizard (Short Link for URs: http://bit.ly/WazeEditOz) Introduce yourself Australian forums Unlock forums | ACT | NSW | NT | QLD | SA | TAS| VIC | WA Waze Australia Discord server Glossary	Australia's Expectations Revised Waze Editing Philosophy Language and Terminology Unique Australian Guidelines Australian scripts Links sheet to every resource
General Topics	Mapping Topics
Country management team Application for Area Manager Global Wiki Country specific permissions External Data / Third-Party Sources Policy How to use third-party data sources	City Names Duplicate Cities Abbreviations and Acronyms Road Attributes Road Types & Naming Lane Guidance Cameras Railway Crossing Alerts Toll Pricing Project Places Style Guide Update Requests (URs)

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.

Revised Waze Editing Philosophy

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.

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.

Screenshot

Unique Australian Guidelines - working on this

This will be revised and simplified.

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. 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 Mapping Parking Lot Roads.
4. We do not map turn lanes unless they are really needed. See Should the connector be mapped
5. Bike paths, hiking trails or other walkways that do not benefit drivers should not be mapped. 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.