Make non-residential place addresses indexed and routable
Editors spend much time adding RPPs to public places because the addresses in the place points are not indexed/routable and the HNs won't connect to the parking lot roads. Plus if routing uses the Google Maps address we spend more time handling URs because the Wazer got routed to the back of the location rather than the front door. This is an absurd waste of time, and adds untold complexity and clutter to the map. Please expand the place addresses to allow for suite numbers or other identifiable info where businesses share the same basic as GM already does, and then make these addresses indexed and routable. This would eliminate a huge amount of editor frustration, not to mention freeing up a huge amount of time that can be used for other needed editing. If Waze is unwilling to create an indexed and routable database for non-residential place addresses then let's just use GM's database and fix the location errors in it.
I was thinking about how to implement this today as adding an RPP next to a public venue point is highly redundant. I have a few possibilities in mind:
A: add a 'trust this address' property to public places in WME
B: automatically add addresses to the database when a place is edited by a sufficiently trusted editor
C: add addresses to the database when a place is locked to L3 or higher (perhaps configurable by country?)
Curtis Parish commented
Glad you added this suggestion. When I first started editing I was surprised that PPs were not routable. It only makes sense.
Chris Schwarz commented
I totally agree, also, some users are adding photos to the RPP addresses for a place that already is on the map instead of where it should be - for the place! Eventually, the business will change and guess what the photo that was added to the RPP will be wrong. So now we will have more unnecessary work to remove the RPP photos. If you could add what is suggested above it will help all of us, before it get out of control. Thanks