User:Whathappened15/TN View history

The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.

This is a draft page to replace the "To Do List" section of the TN Wazeo. An link to here, and an abbreviated outline of project titles, would exist on the main TN wazeo page.

To Do List

This list is intended to help guide the editing efforts of Editors working in Tennessee, and to help editors identify things to work on. All high-quality edits make the map better and are thus valuable, so please feel welcome to work on whatever you like. This list will hopefully help answer the question of "well, now what can I do?" 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.

Tracked vs Untracked Projects: TN State Managers have developed tracking mechanisms for some projects. These tracking sheets are meant to help editors not waste their time working where work has already been completed, to create lasting resources for editors in the future, and to help keep up with how close to complete we are on each one. The presence of a tracking sheet does not mean that a particular project is more or less important than one without.

Tracked Projects

Functional Classification (FC)

Goal

Review of the latest TDOT 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. Some counties have more than one map published and referenced. We will work 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 work, please make sure to check all of the following details on roads included on the FC maps:

  1. WME road type should match or exceed the TDOT FC.
    1. When you find segments which are mapped in WME above their current FC 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.
    2. If we decide to keep the segments upgraded, please document in the Upgrade Tracking List, found here: XXX
  2. Implement lock levels to match the WME road type.
    1. 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.
  3. Check and add primary and Alternate names for the correct US, TN, and SR numbers, as well as any local names which may be used on signage or addressing.
    1. Numbered routes are generally indicated on the FC maps. The five- and six-digit route numbers shown on the FC maps do not get mapped in Waze.
  4. Check and add city names.
    1. Where inside incorporated city boundaries, the primary and all alternate names should carry the city name.
      1. In rare occasions the USPS city name will be different from the incorporated city name. In that case, the primary name should be the incorporated city name, and alternate names should be included for both city names.
    2. Where outside incorporated city boundaries, the primary city name should be "No City." All alternate names should carry the applicable USPS city name. This includes adding an alternate name of the format [Primary Street Name], [USPS City], TN.

Note: To preserve map connectivity, if you are editing a road that leaves the FC map that you are currently working, 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 Google Sheets document. Please keep the sheet updated as you work.

  1. When you start work on 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 working the same map you are.
  2. When you complete a map, please set the status to "Complete" and update the date to when it was completed.
    1. Please work any "Inset Areas" on the FC map as part of the map you are on. This does not include references to different numbered maps, but just Insets that are printed on the same map.
    2. 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 prior to marking the map as "Complete."
    3. 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 99 TDOT Functional Classification maps. 0% complete.

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). Working 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:

  1. Identify a system entity which needs work. Find their website and try to find a listing of all of their locations.
  2. Work 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.
    1. As needed, please contact TN SMs to discuss naming conventions which may be appropriate.

Recommended Resources and Tools:

  • Script: WME Place Harmonizer (aka WMEPH), which will help guide you through completing place edits to current standards
Tracking Procedure

Our progress on this project will be tracked by this Google Sheets document. Please keep the sheet updated as you work.

  1. When you first identify a system entity, please add it to the list. Note that there are tabs for various system categories. Please:
    1. Fill in the entity name
    2. 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.
    3. Mark as "In Progress" and include your editor name and date. This prevents another editor from spending time simultaneously working the same system you are.
  2. When you complete a system, please set the status to "Complete" and update the date to when it was completed.
    1. 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 prior to marking the system as "Complete."
Status

As of Oct 30, 2017, we have identified 0 systems and completed mapping of 0 of them.

Un-tracked Projects

These are not "less important" than the Tracked Projects above. They are just not currently set up with tracking documents. If we develop a way to track them, they will be moved up to Tracked Projects.

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 working on basemap, please contact other editors for tips and pointers.

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

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.

At this time, when a user searches for an address as their destination, Waze will search the map for "[street name], [city]" in our state. If it does not find that particular combination on any segment in the state, the search will be sent to Google, regardless of the presence of House Numbers (HNs) or Residential Point Places (RPPs) on the Waze map. Google-sourced address pins are often wrong and lead to Update Request (UR) reports.

Waze will only return RPPs and HNs the user as search results if the "[street name], [city name]" combination exists in the state.

Editing Procedure

This is often best worked on in conjunction with other projects, but can be a stand-alone editing effort as well.

  1. Identify the correct USPS city name and the boundaries of that name, which are found at the boundaries of USPS Zip Codes. The script "WME US Government Boundaries" will show the zip code boundaries, and will show the USPS city name at the top of your screen.
  2. Identify if the city name is incorporated, and if so, what the boundaries of the incorporation are. The script "WME TN Cities Overlay" will show these incorporated limits.
  3. Edit all segments to include the USPS city name correctly:
    1. If a segment is inside the incorporated limits and...
      1. the USPS city name matches the incorporated name, then:
        1. Primary name: signed street name/number, USPS city name
        2. Alternate names: secondary name(s), USPS city name. Additional alt names may not be required
      2. the USPS city name is different from the incorporated name, then:
        1. Primary name: signed street name/number, incorporated city name
        2. Alternate name: signed street name/number, USPS city name
        3. Alternate names: secondary name(s), USPS city name. Additional alt names may not be required
    2. If a segment is outside the incorporated limits, then:
      1. Primary name: signed street name/number, No City
      2. Alternate name: signed street name/number, USPS city name
      3. Alternate names: secondary name(s), USPS city name. Additional alt names may not be required

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