| Start: 14 April 2018 (subject to change) | End: April 2019 (approximately) |
Every UR is a golden nugget of information for improving the map, and every UR reporter is a partner in map editing. There are more open URs in New York City than in most of the rest of the USA combined. These URs are a gold mine of information about things that need to be fixed on the map. The streets are complicated and ever-changing in New York City, the number of wazers is high, and the percentage of wazers editing the map is not quite high enough. The New York City UR Project aims to bring together a few editors with a variety of experiences to mine that gold, improve the map, and learn from each other.
This project will work on one borough at a time, spending several weeks in each. The project team will individually analyze, answer, and act on every UR in the borough. More experienced editors will teach newer editors how to confidently follow guidance and etiquette to get the most of URs. New and visiting editors will experience editing some of the most interesting street systems in the US. Editors of all ranks will learn from those who are familiar with the streets.
Goals
- Use URs to find and fix the map
- Analyze, answer, and act on every open UR in NYC
- Learn, practice, and teach NY state guidelines and best practices for working URs
- Look for and fix other issues in the general vicinity of the URs
- If all the URs are currently dealt with (closed, or in a "waiting period"), address PURs and MPs in the current borough.
What is NOT a Goal of this Project
- Any edits not required to solve URs, such as parking lots or other basic edits.
- Speed Limits.
- Locking standards.
Hosts
All Local NY State Managers and A/RCs
Communication
- We will communicate primarily using the Northeast Region Waze Editors Discord Server. Special channels will be reserved for this project.
- We may also use Waze's official but limited chat within WME
- Please set yourself visible in WME chat and turn on the Users layer
Borough Sub-Projects
Guidance
=== URs ==- The project will follow New York State guidelines for working URs.
We will use 1-4-10 system.
When you can solve an UR without any user input:
- You OPENED an UR.
- IDENTIFIED the problem,
- you were able to SOLVE it...
- LEAVE A COMMENT and click MARK as SOLVED and CLOSE IT
URs that are not clear and that we need users' input:
Day 1:
- You OPENED an UR.
- CANNOT IDENTIFY the problem,
- ASK user for clarification
- Wait for 4 days and send a REMINDER
Day 4:
- SEND a REMINDER note to the user
- Wait for user's response from for 10 days
- if no answer comes from the user, CLOSE the UR (see below)
Day 10:
- It's been 10 days since you sent the reminder.
- LEAVE A COMMENT and click MARK as NOT IDENTIFIED and CLOSE IT
Summary:
- UR reporters and other editors are all respected members of the community and partners in closing URs. We treat everone with respect and courtesy. Even when they are wrong or make an unpleasant response. :)
- Always thank the UR reporter for helping with the map.
- We work as a team. Anyone may send a first response or reminder notice. If the problem is not identified and the reminder time has expired, anyone may close it. If we have a new idea, we discuss it with the other editor(s) working the UR.
- If editors need to discuss the analysis or approrpriate response to the reporter. We do not discuss in the UR.
- We always analyze a UR and all available clues before making our first response
- We prefer targetted, customized responses. No automated responses
- If it is immediately apparent how to fix the problem and solve the UR, you may make the fix, notify and thank the reporter, and close the UR.
- If a response is needed, follow the "wait time" guidelines - this means that there will be at minimum 3 comments from reporters before closing a UR.
- After making a first response to a UR or after responding to the reporter's comment, wait 4 days before sending a reminder.
- If there has been a reminder, and the reporter has not responded after 14 days from the first response, evaluate whether the UR is ready to close.
- When closing a UR, always use an appropriate closing comment.
Before you edit
Settings
|
|
|
|
Places
Adding places will be required to solve some of the URs. New York follows USA guidance on places except for .... The WMEPH tool for place harmonization is a useful way to check that you have followed guidance on completing places.
Update pending Places
You can proceed with places that are pending updates (enable the "Places" checkbox in Issues layer of WME).
- Please wisely approve new photos of places. Check the place exterior with StreetView if possible.
- New parking lots should only be area places.
Locking Standard
Follow the New York City Locking Standard
Project Tools
Editing Resources
Allowed sources:
- WME Satellite Imagery and WME Street View (do not copy street names from WME Street View)
- Websites from businesses
- New York State sources
- New York State scripts
NOT allowed sources:
- Google Maps
- Google Street View within Google Maps
- Street names which appear in WME street view images (these come from Google Maps, and are sometimes wrong)
- Other external sources, such as OpenStreetMaps, Bing, etc.
Warning: If you copy information from unauthorized sources, you may be removed from this project team. Also, every segment you edited may be removed from the map. Copying information from copyrighted sources is illegal!
Highly recommended scripts
These tools are all scripts that will help you make better use of the information available to you in WME. For this Project, the following are highly recommended. You are responsible for learning what they do and using them appropriately.
- Can load address points and parcel boundaries
- Select the GIS-L tab, then under the GIS Layers Settings, check NY state and under Layers choose "State - Adress points" and "State - Parcels"
- Requires Tampermonkey
- A powerful script that will help you spot map problems more quickly. Ask group leaders for the best settings for the types of problems you are working on
- Install for Chrome only (Requires Tampermonkey).
- An extension that removes the layer settings and insert the "missing" / in URLs
- Helps you spot 2-segment loops, segments with undefined direction, and "soft nodes" with unconfirmed turns, and has other tools available for higher-ranked editors.
- An extension that shows junction's angles. Essential for knowing what the default Waze turn instructions will be.
- Install for Chrome or Firefox
- (Requires Tampermonkey for Chrome or Greasemonkey for Firefox)
- Install for Chrome or Firefox
- A script that shows where Street View imagery is available in WME segments and places.
- Install for Chrome or Firefox
- (Requires Tampermonkey for Chrome or Greasemonkey for Firefox)
- Install for Chrome or Firefox
Please remember that you are responsible for edits made through the use of scripts. Always understand what the script does before using it! There are a wiki page and a forum with more information.