None as default for street and city in new segments
Submitted on behalf of the IL community: Why isn't a default value of "no street", "no city" entered in the address field of a new segment? New editors don't always fill out the address field and it remains "no address", creating a need to contact them and explain to them how to choose "no" for the street name.
-
Paulo Gustavo commented
Indeed, whenever you add a new segment, you are required to fill in the Street Name. Otherwise, the segment remains “bleeding.”
I fully understand that requiring a Street Name may originally have been a strategy to prevent the uncontrolled creation of unnamed segments. This was also the approach used for segments created directly from the app via the Pave tool.
Today, however, this requirement has become an obstacle in the editor’s workflow. The editor has to perform no fewer than four clicks: expand the address box, expand the dropdown for Street Name, select “None,” and then confirm. This is a non-trivial amount of work for every new segment - and it still does not ensure that the editor actually provides a Street Name.
At this point, we already have a much more mature division of labor among editors, as well as several tools (scripts) for tagging and reviewing unnamed segments.
It is also worth noting that the Street Name is the only mandatory field in the address set:
* if you do not fill in the City, WME automatically sets it to “None”;
* State and Country are already prefilled by WME.
I therefore suggest allowing the user to save a segment without entering a Street Name, exactly the same way it already works for the City field.
Also, this idea complies with the C.A.R.™ formula:
* Cheap: easy for Waze devs to implement;
* Aligned: it does not break or undermine the platform’s logic;
* Relevant: it has a significant impact on a real problem faced by editors.