| The new Waze Wiki, aka Wazeopedia, is now live at Wazeopedia.waze.com! While this legacy wiki will remain accessible for the time being, it is no longer updated by the community. For the most up-to-date guidance, please visit your local Wazeopedia.
Please do not make any more updates to these legacy wiki pages, all future updates should be made in your country's local Wazeopedia.
Please follow general worldwide guidelines for mapping Places.
A Place can be locked at 3 once it minimally has the following information:
- Correct Category
- Name - Formatted with Title Case (Use capital letters for the first letter in each word)
- Area or Point as appropriate with Destination Point in the correct location
- Address - House number and correct street name
Please try to fill in all information available, but those items are the minimum.
Airports and hospitals should be locked at 5. Other important places such as major tourist attractions prone to editing and major parks can be locked at 4 or 5 as necessary to protect their integrity.
Place Update Requests
When moderating Place Update Requests (PURs), please be aware that they are not added to the map until the Wazer hits Done. This means that a passenger of a car may take a great photo of a business, but be a block or two down the road before it is added. Zoom into the map where the Place was added and ensure they are where they are supposed to be, moving the point if necessary.
Chain Name Harmonization
In an effort to keep common Places the same across the region, the South Atlantic wiki page now has a list to reference. The list includes Names, Alt Names, Categories, and Websites of Chain companies across the region. If you do not see a Chain listed and feel it should be added, please fill out this form to submit it for review.
Team UR Handling
For best practices and etiquette, see the Update request wiki page.
Tennessee editors encourage teamwork in handling URs. URs are not owned by the first responder. If another editor has first hand knowledge of the issue and can make the necessary corrections to the map to solve the reported issue, they are free to do so. Editors must comment on a UR when closing them, even if the editor is the original reporter.
When a UR does not contain enough information or the fix is not obvious, we have found that a 1/4/8 system works well for generating a response from the reporter. For example:
Within 24 hours (1 day) after an Update Request has been submitted, an editor should provide a response to the Update Request to get the process started. This starts a seven day clock.
If the reporter has not commented after 3 days (4 days since initial comment) a second message is sent reminding the reporter that we need more information about the problem they encountered to fix the issue.
"Just a reminder: We have not received a response on your report. If we don't hear back from you soon we will infer everything is okay and close the report. Thanks!"
Note - While the 4 day reminder is not required in the South Atlantic region, we have seen a large number of responses from them and encourage their use.
If the reporter still has not commented after 4 more days (8 days since initial comment) a message should be sent telling the reported that we were unable to fix the problem and this report is being closed. The Update Request then needs to be closed as Not Identified.
"The problem was unclear and volunteers didn't receive a response so we are closing this report. As you travel, please feel welcome to report any map issues you encounter. Thanks!"
Old User Reports
The 1/4/8 rule has been very successful in our busy areas with editors maintaining them. There are some areas outside of our reach and occasionally as we venture off the beaten path, we come across a report that has been there for quite some time. We feel these reports are as valid as the reports opened yesterday and they should be given the same courtesy of response as new reports. Give the reporter at least 7 days to respond before closing as Not Identified.