mapcat wrote:Realistically, there is no way to do that regardless of whether it's the right thing to do. If Bing says this is where the marker goes, and another company using Bing's data thinks that the marker should be somewhere else, it's the other company's responsibility to work around that. Moving the marker to where it works for Waze isn't the right thing to do if it goes against Bing's best practices, and eventually someone from Bing is just going to move it back anyway.
Are we sure that is also Bing's policy for correct street addresses? Although I believe that data can't be corrected at all in the Bing interface and needs to be corrected by their
provider of data, NAVTEQ. And based on AlanOfTheBerg's past experiences with that, it is less than ideal getting a response or getting the data updated.
In any case it's probably fruitless and beyond the scope of Waze map editing to be dealing with correcting data with the external providers. It's a limitation of using external data (which is necessary or Waze wouldn't route to street addresses or POI's at all). Wazers just will have to deal with it.
In my area of San Diego, since the most of the San Diego metro area has been fully edited (every street, junction, etc) most of the Update Requests now are related to:
* External data that does not play well with the Waze map (street address, POI, etc)
* External data that has the POI or street address in the wrong location
* Turn restrictions that are being disregarded due to their low penalty and not another feasible lower cost routing option. Typically happens coming out of dead ends, Parking Lots, Private areas or areas that don't have other ways to route out.
* Client or other issues that get reported as Update Requests
* Wazers incorrectly using the Update Request function to navigate
* Wazers playing...
I'd say less than 10% of the Update Requests that are being submitted in San Diego are something that can be fixed with a map edit.