jdeyoung wrote:As I indicated, that leaves us at a bit of an impasse. I've lived in/around Chicago all of my life, and can look at addresses on a street and know they've all been mass-imported (like little toy soldiers all lined up) and placed too close to the alley. I'm not suggesting waze itself have this knowledge and do so automatically nor does it make sense to wait for each and every resident along the street to report a UR that their address is incorrectly too close to the alley. Should we wait for the hundreds of thousands of these to be reported? A better approach to solving these ad-hoc after a user reports a wrong location for the umpteenth time would be to solve these for entire streets at a time with a proper tool. It was a massive effort to mobilize editors in the area to attack the problem of alleys created from basemap as streets. Now multiply that by 40-50 addresses per block of all the residential streets and you get an idea of the amount of effort needed.
I don't think we have to be an an impasse, though, necessarily.
A single process that would make some users' lives a lot easier but that would also mess things up really badly for other users simply cannot be employed.
I'm not against a tool that would allow an editor, upon verifying that the house numbers on a particular street are correct, to confirm a large series of address points with one click. That would make your lives a lot easier without confirming a bunch of bad imported data.