|
|
| (16 intermediate revisions by one other user not shown) |
| Line 1: |
Line 1: |
| {{construction
| | Please see the official and maintained version of this page: [[Edits to avoid]] |
| | contact = https://www.waze.com/forum/viewtopic.php?f=276&t=100497
| |
| | contacttype = forum
| |
| | draft = yes
| |
| | open = no
| |
| }}
| |
| | |
| If you were advised to read this wiki, it means another editor believes some of your map edits using the Waze Map Editor (WME) are incorrect. Those edits may already have been modified or deleted. This may be an unpleasant surprise, especially if you put a lot of time and energy into those edits, but rest assured that you are in good company. Every one of Waze's many volunteer editors has made mistakes that required correction or removal.
| |
| | |
| The purpose of this wiki is to help you understand what about your edits may have needed undoing and to offer you suggestions on where your editing energy could do the most good.
| |
| | |
| {{TOC}}
| |
| | |
| == Incorrect edits are a natural part of Waze ==
| |
| | |
| Having edits undone or redone may make you feel like being a Waze editor is not for you. That's a sensible response, but actually, Waze and the volunteer editing community need you.
| |
| | |
| It is so important to Waze to encourage new editors that they deliberately omit any training requirements to get started. Without any information, practice, or tests -- in fact within minutes of discovering Waze -- you can begin modifying Waze's maps. This is exciting, but it also means you will make mistakes. We all do.
| |
| | |
| Incorrect edits are a natural part of Waze. So please don't feel bad! Because these maps are used by your friends, neighbors, and more than 50 million other people, your fellow editors simply must act as soon as they discover the map is not how it should be.
| |
| | |
| === What did I do wrong? ===
| |
| | |
| Incorrect edits include both functional mistakes and misunderstood conventions. Functional mistakes are more serious but both require response.
| |
| | |
| == Functional mistakes ==
| |
| | |
| A functional error introduces wrong or incomplete data or faulty routing. Functional errors must be addressed as soon as they are detected. If your incorrect edit was a functional mistake, the editor who discovered it has probably already taken steps to fix it.
| |
| | |
| === Red roads ===
| |
| [[File:Redroad.png|thumb|right|300px|Example of a "red road".]]
| |
| [[File:Redroad_fixed.png|thumb|right|300px|The "red road" after correction.]]
| |
| Roads that appear bright red in the WME were published before all necessary parameters were set properly. These roads will appear on the Waze client but are useless for routing. Their prominent display calls attention to incomplete edits. See the [[Map_Editing_Quick-start_Guide | Map Editing Quick-start Guide]] for details.
| |
| | |
| <i>Response: Do not automatically delete red roads! They are often the creation of local editors with first-hand knowledge. They may reflect construction that occurred since the satellite and/or street-view imagery was acquired.
| |
| | |
| If the red road appears to indicate a drivable road that will improve routing to adjacent destinations, complete it as necessary and verify turn restrictions. Try to preserve the creator's name out of respect for their having found the omission and attempted to remedy it.
| |
| | |
| If the red road is clearly spurious, or if finishing it would disrupt routing as in the common case of [[#Access_roads_that_distort_routing|unnecessary parking-lot roads, private alleys or driveways]], delete it.</i>
| |
| {{clear}}
| |
| | |
| === Misplaced roundabouts ===
| |
| The WME roundabout tool creates an intersection that gives roundabout-specific routing instructions to drivers. It should only be used for real roundabout intersections with three or more exits! It does not belong at cul-de-sacs or other dead ends, traffic calming circles without roundabout signs, or decorative entrance driveways. It is also inappropriate for large traffic circles with street names of their own. It must never be used for ordinary intersections because the roundabout routing instructions will confuse drivers.
| |
| | |
| <i>Response: If the satellite image leaves doubt, use Street View to verify that no signs suggestive of a roundabout are present. If it is a roundabout, ensure the layout matches the desired roundabout routing behavior, either orthogonal or odd-angle. If it is not a roundabout, delete it and repair any associated connections.</i>
| |
| {{clear}}
| |
| | |
| === Overlapping segments ===
| |
| Except in the case of at-grade connectors, there should be only one segment routing traffic along any given street. Overlapping segments wreak havoc with the routing and house-numbering systems.
| |
| | |
| Sometimes editors create overlapping segments because they don't know how to modify the existing segment, or find it is locked above their editing rank. The correct approach is to seek help, not to add a new segment on top of an existing one.
| |
| | |
| <i>Response: Identify the overlapping segment -- typically the one without house numbering and/or with improper connections to other nearby segments -- and delete it. Repair turn permissions.</i>
| |
| {{clear}}
| |
| | |
| === Disconnected/disjoint segments ===
| |
| Just because segments appear to intersect doesn't mean they really do. A proper intersection will display all turn restrictions if any connecting segment is selected. A segment that only appears to connect will not only fail to route but will also confuse editors trying to understand the failure.
| |
| | |
| <i>Response: If the intersection appears valid and the segment is correct, routable, and complies with conventions, connect the segment and set turn restrictions appropriately. If the intersection is not valid but the segments are correct, space them so it will be obvious to other editors that they do not connect, and consider locking them to be sure they stay that way. Otherwise delete the segment.</i>
| |
| {{clear}}
| |
| | |
| === Corrupted turn restrictions ===
| |
| Sometimes when modifying an intersection an editor will, through accident or lack of awareness, leave important turn restrictions red. This will prevent routing on the affected segments. In the worst cases significant roads may effectively be closed to Wazers, who are instead detoured through adjacent neighborhoods.
| |
| | |
| <i>Response: Correct the turn restrictions as soon as possible.</i>
| |
| {{clear}}
| |
| | |
| === Critical segments missing ===
| |
| It should go without saying that a road will not route if it does not go through, but it happens that editors delete or leave out critical segments.
| |
| | |
| <i>Response: Replace the missing segments and verify turn restrictions as soon as possible.</i>
| |
| {{clear}}
| |
| | |
| === Failed editing due to locked segments ===
| |
| The more significant the road, the more likely it is to be locked so that only higher-ranking editors can modify it.
| |
| | |
| It is impossible for novice editors to attach new segments to a locked road, although they can and do try, leading to disconnected/disjoint segments as described above. Worse, the novice editor may assume that they did indeed correct the problem, and leave the area broken until someone else stumbles across it.
| |
| | |
| <i>Response: Contact an editor of the necessary rank to fix the area.</i>
| |
| {{clear}}
| |
| | |
| === Excess or misaligned geometry nodes ===
| |
| Use only the minimum number of geometry nodes to match the road. Excess nodes slow the display and make the segment harder to edit, while misaligned nodes affect display aesthetics and in extreme cases disrupt Waze's ability to determine what road a driver is on.
| |
| | |
| <i>Response: Remove excess geometry nodes (using mouse-hover and the 'd' key) and correct misaligned nodes.</i>
| |
| {{clear}}
| |
| | |
| === Misunderstanding the "Highway" road type ===
| |
| It is counterintuitive, but in Waze, "highway" does not necessarily mean a road that carries a lot of traffic. It just means a road that carries more traffic than nearby alternatives. For example, a barely-maintained one-lane mountain road may be a "Minor Highway", and a two-lane street serving a small village a "Major Highway". Assessing a road by its significance relative to nearby alternatives is called "functional classification" or FC.
| |
| | |
| Such situations often baffle new editors to whom this application of the word "highway" seems absurd. As a result, some will attempt to put it right by lowering Highways to Streets or Primary Streets, unwittingly ruining the careful and methodical work that was required to set the road type according to national FC standards.
| |
| | |
| <i>Response: Find the government FC map for the affected area and restore the Waze road classifications according to editing-community conventions. Consider locking the affected segments, especially if local convention recommends it.</i>
| |
| {{clear}}
| |
| | |
| === Impulsive road splitting ===
| |
| Just because a road is divided by a median strip in reality is not enough reason to split it in Waze! Splitting roads can cause a great deal of trouble and should not be attempted without care and preparation. Always check with the local Area Manager before splitting a road.
| |
| | |
| <i>Response: Check with the local Area Manager or a Champ. Unsplitting roads can cause as many headaches as splitting them in the first place. Do not automatically assume that a newly-split road is incorrect, even if the split was performed poorly or by a novice editor.</i>
| |
| {{clear}}
| |
| | |
| === Unnecessary and/or connected walking paths ===
| |
| Walking paths are not benign! Waze will route drivers over them! Even when not connected to the drivable road network, walking paths that come too close to drivable destinations can corrupt routing results.
| |
| | |
| In addition to their potential effects on routing, mapped walking paths may encourage people to use Waze while walking or bicycling, a practice that can pollute Waze's traffic-detection data. Editors should not create walking paths for the sole purpose of supporting people using Waze while walking or bicycling. That includes adding segments to respond to automated Map Problem reports (usually of type "missing road") generated as a consequence of people Wazing while walking or bicycling.
| |
| | |
| There are few circumstances that call for the mapping of walking paths.
| |
| | |
| <i>Response: First of all, unless this is one of a tiny handful of cases where a walking path is required to reach a routable destination, disconnect the path from any drivable road segments. If there is any chance the walking path could confuse drivers or distort local routing, delete it.
| |
| | |
| If the path is sufficiently isolated so as not to cause routing problems and it is named (e.g. "Los Gatos Creek Trl"), consider leaving it, particularly near any parking for the path, as its name may be used as a search term. Also consider leaving walking paths used by Wazers that have long parallel stretches alongside roads; if we can't stop people from using Waze while walking or biking, we may as well reduce the likelihood they will corrupt the speed data for adjacent traffic.
| |
| | |
| Unnamed walking paths that do not get used by Wazers and are not required to reach a destination should be deleted even if they don't disrupt local routing. They may not appear to do any harm, but their presence encourages other editors to add to the paths or create new ones.</i>
| |
| {{clear}}
| |
| | |
| === Access roads that distort routing ===
| |
| New editors often believe that if you can drive it, you can map it, and commonly add parking-lot roads, driveways, and private alleys because they are there. Such roads can distort rather than enhance routing! If you add a private road to your house, for example, Wazers visiting your neighbors may find themselves routed up your driveway. If you add a private alley that connects two streets through a warehouse district, a delivery person near the alley may be snapped to that alley and given an impossible route to his next destination.
| |
| | |
| In general, you should map roads because they are necessary for routing and not simply because they are there.
| |
| | |
| <i>Response: If the road does not comply with the wiki for private access roads and driveways, delete it. If it appears to comply but causes routing issues that cannot be improved with additional compliant roads, that calls for deletion as well.</i>
| |
| {{clear}}
| |
| | |
| === Unnecessary at-grade connectors ===
| |
| At-grade connectors are not necessary unless the driver needs advance warning of an upcoming turn. Unnecessary at-grade connectors are more trouble to analyze and maintain, and their close proximity to the through road from which they split can lead Waze to snap drivers to the wrong road. Asking for a route while snapped to the wrong road, for example while waiting at a stoplight too near an at-grade connector, will result in incorrect routing.
| |
| | |
| <i>Response: Delete the unnecessary at-grade connector as well as any newly-unnecessary junction nodes that result, and modify turn restrictions to account for the new routing.</i>
| |
| {{clear}}
| |
| | |
| === Misuse of the Ramp road type ===
| |
| Ramps are appropriate only for limited situations. If a novice editor uses the Ramp road type it is likely to be a mistake.
| |
| | |
| <i>Response: Change to the correct road type and rework if necessary, or delete.</i>
| |
| {{clear}}
| |
| | |
| == Misunderstood conventions ==
| |
| | |
| Misunderstood conventions do not necessarily involve wrong data or faulty routing, but violate editing conventions agreed upon by the local Waze editing community. The damage done by a misunderstood convention is primarily by example; other editors will interpret the error as a model for what they should do, and the mistake will proliferate.
| |
| | |
| If you've been approached regarding misunderstood conventions, you may have been given the opportunity to correct or delete your work. Please do so! It may be the least enjoyable thing you will do in Waze, but if you don't do it, someone else eventually will, and in the meantime the incorrect example may influence other novice editors.
| |
| | |
| === Excessive parking-lot roads ===
| |
| While mapping every lane in a parking lot does not cause functional problems, it does create a busy appearance in the client display that is completely unnecessary for routing.
| |
| | |
| By convention the Waze editing community only maps the minimum number of parking-lot roads necessary to ensure proper routing to and from destinations. In some cases no parking-lot roads are necessary at all.
| |
| | |
| <i>Response: Delete extraneous parking-lot roads and any newly-unnecessary junction nodes that result. Remember that parking-lot roads absorb slow-traffic indications and be sure not to delete lanes that "protect" adjacent thoroughfares from spurious slow-traffic detections.</i>
| |
| {{clear}}
| |
| | |
| === Misuse of Area Places ===
| |
| By design, Area Places (formerly known as landmarks) render in the client and will be seen by drivers as well as editors. As a result, marking everything with an Area Place could lead to an excessively busy display. The resulting sea of unremarkable locations could swallow up the really important landmarks.
| |
| | |
| While controversy persists about the "right" density of Area Places, current guidance leans towards less dense. A detailed table in the [[Places|Places wiki]] lists what is eligible for an Area Place and what should instead be a Point Place.
| |
| | |
| <i>Response: If the Place is otherwise correct and compliant, convert it to a Point Place and adjust its location for best routing. Otherwise, delete it.</i>
| |
| {{clear}}
| |
| | |
| === Misuse of the Parking-Lot Area Place ===
| |
| The Waze Map Editor gives easy and prominent access to the Parking-Lot Area Place directly from the create menu. In most urban or suburban neighborhoods, however, mapping every parking lot would create a vast ocean of parking. To simplify the maps, the Waze editing community only uses the Parking-Lot Area Place for <i>off-street general-purpose parking provided for the general public</i>. See the [[Places/Parking lot|Parking-Lot Area Place wiki]] for details.
| |
| | |
| If you really did map general-purpose parking for the general public, the best way to reduce the chance it will be deleted is to assign the parking lot its documented name. Unnamed Parking-Lot Area Places are much more likely to be deleted.
| |
| | |
| <i>Response: If the parking lot complies with the wiki, ensure that the Name field shows its documented name, e.g. "City Lot #6". If the lot has a name but is for private or dedicated use, you may consider converting it to a Point Place. Otherwise delete it.</i>
| |
| {{clear}}
| |
| | |
| === Closing URs without proper consideration ===
| |
| Waze users file Update Requests (URs) to alert the editing community of problems they experienced. In some cases URs can indicate significant errors in the map, but drivers rarely have time to enter adequate text in the description field. They depend on the editing community to open a conversation with them so they can explain more fully what happened. Handling URs follows a careful process [[Update_Requests_in_Waze_Map_Editor|documented here]] that (a) provides drivers with an adequate opportunity to explain their report and (b) provides editors with an adequate opportunity to work the report once they begin.
| |
| | |
| An editor who closes a UR without following this process commits a serious breach of Waze etiquette! Closing untended URs without due consideration confuses reporters who expected to have their concerns taken seriously and injures their good will towards Waze. Closing URs being actively worked by another editor interrupts the communication, sends a mixed message to the reporter, and frustrates the efforts of the working editor.
| |
| | |
| Update Requests must only be closed by editors following the procedures outlined in the [[Update_Requests_in_Waze_Map_Editor|wiki on Update Requests]].
| |
| | |
| <i>Response: Once closed, a UR will remain accessible for several days. A skilled editor who catches the closure in time and moves quickly may be able to work a closed UR before it disappears. If a dialogue can be established with the reporter, it can be continued using the emailed links to the UR conversation even after the UR has disappeared from the map.</i>
| |
| {{clear}}
| |
| | |
| == What should I edit, then? ==
| |
| | |
| Your energy is best focused on regions you know, but if you live and work in a heavily-populated area, your local neighborhoods may have been edited and re-edited many times. There may be little left to do aside from removing excess geometry nodes, correcting minor misalignments, and verifying turn restrictions.
| |
| | |
| Consider editing less-traveled locations you may have visited recently. Many non-industrial and rural communities have seen little attention since the original base-map import. Such regions often abound with misnamed roads, dirt roads misclassified as streets, improper turn restrictions and street directionality, roads shown as through that do not go through, and so on. Finding good information to correct these issues may take some work, especially in more remote areas, but it is a terrific contribution.
| |
| | |
| If you do choose to focus on a heavily-edited area, be aware that many have come before you. Things that don't seem right at first may have resulted from days or even weeks of careful adjustment. Exercise caution when adjusting other editors' work.
| |
| | |
| === Constructive work for novice editors ===
| |
| | |
| * Verify road names by checking against county GIS and signage viewed in street-view imagery, and ensure road-name consistency within city boundaries.
| |
| * Verify road directionality, particularly one-way roads that Waze may show as two-way.
| |
| * Verify turn restrictions, including timed turn restrictions.
| |
| * Correct streets shown as through on the Waze map but that are blocked in reality.
| |
| * Add recently-constructed roads not yet shown on the maps, or shown incorrectly due to obsolete satellite and street-view imagery.
| |
| * Correct road alignment errors and remove excess geometry nodes.
| |
| * Alert area managers and/or senior editors to problems.
| |
| * Add Point Places.
| |
| | |
| === Examples of work with greater risk of incorrect edits ===
| |
| | |
| * Adding parking-lot roads (risk of overdoing it, of leaving behind corrupted turn restrictions, or of failing to join the roads to adjacent locked segments).
| |
| * Adjusting major intersections, ramps, or highways (highly likely to encounter locked segments, but even if not, risk of disrupting heavily-traveled areas).
| |
| * Responding to user-submitted Update Requests (requires extensive familiarity with UR etiquette and with common problems encountered by Wazers).
| |
| * Adding or modifying roundabouts.
| |
| * Adding Area Places.
| |
