|
|
| (One intermediate revision by the same user not shown) |
| Line 2: |
Line 2: |
| ------ DO NOT MODIFY ABOVE THIS LINE -------- DO NOT MODIFY ABOVE THIS LINE ------> | | ------ DO NOT MODIFY ABOVE THIS LINE -------- DO NOT MODIFY ABOVE THIS LINE ------> |
|
| |
|
| This list is intended to help guide the editing efforts of Waze Editors in [[Tennessee]], and to help editors identify areas to focus their efforts. All high-quality edits make the map better and are thus valuable, so please feel welcome to edit as you see fit, but this list will hopefully help answer the question of "what can I do now?" Please check back here frequently, as this list will change as projects are completed and new ones added. Announcements of changes will be made in Discord.
| | Tennessee maintains a "To-do" list to help editors guide their efforts and figure out "what can I do next?" That list can be [[Tennessee/To do|found here. ]] |
| | |
| '''Rank Recommendations:''' Projects here have been sorted by recommended Editor Rank. This is intended only as a guide. Please feel welcome to pursue any project that interests you, regardless of your Editor Rank. Editing above your current Rank, with the help of a higher-rank editor is always a good way to learn new skills.
| |
| | |
| '''Tracked vs Untracked Projects:''' [[Tennessee#Area Managers|TN State Managers]] have developed tracking mechanisms for some projects. These tracking sheets are meant to help editors not waste their time editing where the project has already been completed or is in progress, to create lasting resources for editors in the future, and to help keep up with how close to complete we are on each project. <u>The presence of a tracking sheet does not mean that a particular project is more or less important than one without.</u>
| |
| | |
| === Rank 1+ Recommended Projects ===
| |
| | |
| ==== USPS Alternate City Names ====
| |
| '''Goal'''
| |
| | |
| Edit all segments which have destinations on them (generally speaking, types Major Highway and below) to include an alternate name which lists the city name assigned by the United States Postal Service. These edits are critical to address searching for users.
| |
| | |
| '''Editing Procedure'''
| |
| | |
| This is often best completed on in conjunction with other projects, but can be a stand-alone editing effort as well. This is an untracked project.
| |
| | |
| Tennessee follows the current USA guidance for USPS City Names, which can be [[Road names/City names|found here]].
| |
| | |
| Recommended Resources and Tools:
| |
| * Script: ''WME US Government Boundaries'', which will show you the USPS city name and the zip code lines
| |
| * Script: ''WME TN Cities Overlay'', which will show you the boundaries of incorporated cities
| |
| | |
| ==== System Based Area Places ====
| |
| '''Goal'''
| |
| | |
| Identify and map area places associated with "systems" or other entities which operate multiple locations. This includes school systems, fire departments, police/sheriff departments, municipal parks, etc. In addition to being common destinations, these are often community landmarks which are well known to local users. Their presence displayed as areas on the map helps users orient themselves when they look at the Waze app.
| |
| | |
| '''Editing Procedure'''
| |
| | |
| These "system" entities usually maintain a web page which lists all of their properties. Often this resource will include addresses and phone numbers for each location as well, and in many cases the URL is the same for all locations (schools typically will have a dedicated site for each location). Editing system-by-system helps maintain consistency across all locations of the system, and helps make sure we don't miss one. Our proposed procedure is:
| |
| # Identify a system entity which needs review. Find their website and try to find a listing of all of their locations.
| |
| # Edit each location to completion. Where existing places are already mapped, please upgrade them. Otherwise make new places. This includes fixing the polygon and stop point, as well as data including the address, URL, phone number, services and hours. Places should be at WMEPH "green" when you move on. When a place was already existing, please check the pictures for any which may need to be deleted.
| |
| ## As needed, please contact TN SMs to discuss naming conventions which may be appropriate.
| |
| <u>NOTE:</u> ''Please pay very close attention to the correct use of [[Using external sources|external data sources]].''
| |
| | |
| Recommended Resources and Tools:
| |
| * Script: ''WME Place Harmonizer (aka WMEPH)'', which will help guide you through completing place edits to current standards
| |
| * Script: ''WME Place Interface Enhancements (aka WME PIE)'', which streamlines the place interface
| |
| '''Tracking Procedure'''
| |
| | |
| Our progress on this project will be tracked by this [https://docs.google.com/spreadsheets/d/1_nSL1g-DiQwx8DIf3KvmNpJQQN3bMwPBswK9ogBBIWE/edit?usp=sharing Google Sheets document]. Please keep the sheet updated as you edit.
| |
| # When you first identify a system entity, please add it to the list. Note that there are tabs for various system categories. Please:
| |
| ## Fill in the entity name
| |
| ## Post a link to the URL of the list of locations (this is not likely to be the URL you are setting on the WME places). If there is not a concise list, please include a note of how to best use the website to find the locations.
| |
| ## Mark as "In Progress" and include your editor name and date. This prevents another editor from spending time simultaneously editing the same system you are.
| |
| # When you complete a system, please set the status to "Complete" and update the date to when it was completed.
| |
| ## If your editing area prevents you from making necessary edits to complete a map, or if your rank prevents you from implementing the correct lock levels, please reach out to other editors to get those edits made <u>prior to</u> marking the system as "Complete."
| |
| '''Status'''
| |
| | |
| As of Oct 30, 2017, we have identified 0 systems and completed mapping of 0 of them.
| |
| | |
| ==== General Place Clean-up ====
| |
| '''Goal'''
| |
| | |
| Complete editing and verification of user-added places throughout the map. User-added places are located at the spot where the user added the place, not necessarily where the place actually is. Cleaning these up improves routing to that destination for future routes.
| |
| | |
| '''Editing Procedure'''
| |
| | |
| Cleaning up places involves multiple steps. This is an untracked project. Regardless of the order you choose, please address the following issues when processing existing places on the map:
| |
| # Move to the correct location and adjust the stop point as needed for best routing.
| |
| #* Use StreetView, GIS, and the business's website as resources as needed to identify the correct location. Existing photographs associated with the place may also be helpful in finding the right spot.
| |
| # Correct errors and complete the Name, Category, and Address fields.
| |
| # Correct issues related to improper use of Area or Point types. Verify area geometry matches the location's boundaries.
| |
| # Add or verify the location's telephone number and website.
| |
| #* Use the business's website to verify the phone number.
| |
| # If the business's website lists hours, update the hours to match.
| |
| # Rank 3+ Editors: Add the correct External Provider link(s).
| |
| # Lock to regional standard. For most places, this is L3 in SAT.
| |
| #* Rank 1 and 2 editors should lock as high as you can.
| |
| <u>NOTE:</u> ''Please pay very close attention to the correct use of [[Using external sources|external data sources]].''
| |
| | |
| Recommended Resources and Tools:
| |
| * Script: ''WME Place Harmonizer (aka WMEPH)'', which will help guide you through completing place edits to current standards
| |
| * Script: ''WME Place Interface Enhancements (aka WME PIE)'', which streamlines the place interface
| |
| | |
| ==== Speed Limits ====
| |
| '''Goal'''
| |
| | |
| Add speed limit values to all public road segments in the state.
| |
| | |
| '''Editing Procedure'''
| |
| | |
| This is often best completed on in conjunction with other projects, but can be a stand-alone editing effort as well. Please use personal experience as well as StreetView images to identify posted speed limits and add them to the appropriate segments.
| |
| | |
| Recommended Resources and Tools:
| |
| * Extension: ''WME Toolbox'', which will show you color-coded speed limits set on segments
| |
| * Script: ''WME Speedhelper', which adds clickable speed limit buttons to your WME interface
| |
| | |
| '''Tracking Procedure'''
| |
| | |
| This project is tracked statistically by state managers. Editors do not need to do anything to track their progress.
| |
| | |
| '''Status'''
| |
| | |
| As of November 1, 2017ː
| |
| * {{Freeway}}ː100 percent complete
| |
| * {{Major Highway}}ː 100 percent complete
| |
| * {{Minor Highway}}ː 99.7 percent complete
| |
| * {{Primary Street}}ː 74.8 percent complete
| |
| * {{Street}}ː 35.2 percent complete
| |
| | |
| | |
| === Rank 2+ Recommended Projects ===
| |
| | |
| ==== Functional Classification (FC) ====
| |
| '''Goal'''
| |
| | |
| Review of the latest TDOT [[Tennessee#Functional Classification|Functional Classification]] maps to ensure proper implementation in the Waze map. Implementing TDOT FC on the Waze map helps steer traffic to routes which are planned to handle the extra traffic, and hopefully are in better condition and better marked.
| |
| | |
| '''Editing Procedure'''
| |
| | |
| The TDOT maps are published county-by-county in PDF format. Many counties have more than one map published. We will review the TDOT data map-by-map to verify that the FC has been properly implemented in the Waze map. We recommend that you print off the map so you can highlight your progress between editing sessions, or use a digital means to do so. As you edit, please make sure to check all of the following details on roads included on the FC maps:
| |
| # WME road type should match or exceed the [[Tennessee#Step 1: Classification via TDOT Generated Functional Classification|TDOT FC-indicated type]], and also the type indicated by [[Tennessee#Step 2: Classification upgrades via highway type|highway type]].
| |
| ## When you find segments which are mapped in WME above their minimum levels, please contact TN SMs for review. Many roads were downgraded by TDOT in the last round of maps, but some have been deliberately upgraded.
| |
| ## If we decide to keep or add an FC exception, please document it in the [https://docs.google.com/spreadsheets/d/1IGNrrU-FhGIAgxuqj2BVZ3xTW0WvzWxqfVwX8v9M3RM/edit?usp=sharing FC Exceptions Tracking List].
| |
| # Implement [[Tennessee#Road Locking|lock levels]] to match the WME road type
| |
| ## If a segment is deliberately upgraded above FC, please lock to +1 above its normal lock level. i.e. if a segment is marked on FC as PS, and we agree to upgrade it to mH, please lock at 4. That sends a message to future editors that this upgrade was deliberate.
| |
| # Check and add Primary and Alternate names for the correct [[Tennessee#Highway Numbering|US-##, TN-##, and SR-## numbers]], as well as any local names which may be used on signage or addressing
| |
| ## Numbered routes are typically indicated on the FC maps. The five- and six-digit route numbers shown on the FC maps do not get mapped in Waze.
| |
| # Check and add city names
| |
| #* More on this above.
| |
| Note: To preserve map connectivity, if you are editing a road that leaves the FC map that you are currently reviewing, please check with the map it moves onto and carry your edits on to the end of the road. Don't just upgrade out to the county line and stop.
| |
| | |
| Recommended Resources and Tools:
| |
| * TDOT FC Map PDFs
| |
| * PDF mark-up software, or the ability to print out and mark by hand
| |
| * Script: ''WME Counties Tennessee Census 2014'', which will show the boundaries of TN counties on your WME interface
| |
| '''Tracking Procedure'''
| |
| | |
| Our progress on this project will be tracked by this [https://docs.google.com/spreadsheets/d/1yt55QAzGT2tW4uVuGlFIrMQCn90cSx5gNLo2PMQ3xxk/edit?usp=sharing Google Sheets document]. Please keep the sheet updated as you edit.
| |
| # When you start reviewing a particular map, please set the status to "In Progress," and include your editor name and date. This prevents another editor from spending time simultaneously reviewing the same map you are
| |
| # When you complete a map, please set the status to "Complete" and update the date to when it was completed
| |
| ## Please review any "Inset" areas on the FC map as part of the map you are on. This does not include "SEE map" references to different numbered maps, but just insets that are printed on the same numbered map.
| |
| ## If your editing area prevents you from making necessary edits to complete a map, or if your rank prevents you from implementing the correct lock levels, please reach out to other editors to get those edits made <u>prior to</u> marking the map as "Complete."
| |
| ## Remember, once you mark a map as "Complete," it will likely be a long time before another editor deliberately reviews the FC for that map's area.
| |
| '''Status'''
| |
| | |
| As of Oct 30, 2017, we have completed the review of 0 out of 181 TDOT Functional Classification maps. 0% complete.
| |
| | |
| ==== Basemap Cleanup ====
| |
| '''Goal'''
| |
| | |
| Basemap is the result of maps which Waze purchased access to in the early days. These segments often have incorrect names, missing connections, unknown directions, unconfirmed turns, and other issues. Many segments do not belong on the WME map at all. These can obviously create routing issues.
| |
| | |
| '''Editing Procedure'''
| |
| | |
| If you are unfamiliar with editing basemap, please contact other editors for tips and pointers. This is an untracked project.
| |
| | |
| Recommended Resources and Tools:
| |
| * Extension: ''WME Toolbox'', which will help you identify unconfirmed turns and other issues
| |
| * Script: ''WME Magic'', which will help highlight additional map issues.
| |
| * Script: ''WME GIS'', which will give you quick links to state and local GIS data sources
| |
| | |
| ==== Parking Lot Areas (PLAs) ====
| |
| '''Goal'''
| |
| | |
| Parking lots are a new feature in Waze. Their presence on the map allows the app to recommend nearby parking options to users as they approach their destination. More uses are on the way, so we are actively working to map all parking lots in WME.
| |
| | |
| '''Editing Procedure'''
| |
| | |
| Please carefully read the current Wazeopedia Page for [[Places/Parking lot|Parking Lot Places]]. This guidance is subject to change, so please return to it often. This is an untracked project.
| |
| | |
| We recommend that PLAs be added as you process the associated places. Clearing Map Problems related to missing PLAs is also a good way to locate areas to edit, but please tackle the places in addition to adding the PLA.
| |
| | |
| Recommended Resources and Tools:
| |
| * Script: ''WME Place Harmonizer (WMEPH)'', which will help guide you through completing place edits to current standards
| |
| * Script: ''WME Place Interface Enhancements (WME PIE)'', which streamlines the place interface and adds several useful features for working PLAs.
| |
| | |
| === Rank 3+ Recommended Projects ===
| |
| | |
| ==== Places and Parking Lots, reprised ====
| |
| Please refer to the sections General Place Clean-up and Parking Lot Areas (PLAs) above for details . This is listed again under Rank 3+, as you have access to the External Provider Links options and to the standard lock level for most places. Please help lower-rank editors in their efforts to complete places.
| |
| | |
| === Rank 4+ Recommended Projects ===
| |
| | |
| === Rank 5+ Recommended Projects ===
| |
| | |
| ==== Freeway Exit Review ====
| |
| '''Goal'''
| |
| | |
| Review of ramp names to ensure consistency with current standards for geometry, location of exit point, and naming to match posted signage.
| |
| | |
| '''Editing Procedure'''
| |
| | |
| Follow along Freeway routes, checking exit-by-exit. This is an untracked project. Please coordinate with other editors where Freeways leave your editing area.
| |
| | |
| Check signage wording versus latest StreetView, and verify ramp geometry with both StreetView and Satellite view. Pay close attention to TN-## versus SR-## as used on signage. Check FC maps for secondary route numbers which may need to be added to Freeways and Ramps.
| |
|
| |
|
| <!---- DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ---- | | <!---- DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ---- |
