Routing/address lookup bug...

by **gettingthere** » Wed Feb 22, 2012 5:00 pm

AlanOfTheBerg wrote:I'm dense this morning, so I'm not getting what the problem is exactly? The only difference I see is the road is unmunched in one view and not the other. Is there a difference in routing or pin location?

Ave 21 vs. Ave 21 1/2 - PIN location is different when searching for the POI. Bing PIN is incorrect. Google PIN is correct.

If BrianCanFixIt is actually searching for a street address - the street address is not being located in the Waze Search Results and it's finding Bing and Google results via POI lookup - match to the address vs. the POI name.

by **gettingthere** » Wed Feb 22, 2012 4:58 pm

Simple explanation, Bing Search has the GPS coordinates incorrect. You will have to submit a request to Bing to get this corrected. It's not a Waze issue - they are returning the coordinates that Bing is providing.

Bing does have the address correct. Just the GPS coordinates are incorrect.

Go to http://www.bing.com/maps and search for:

fossil discovery center chowchilla, ca

Bing Maps has the location of the PIN correct if you search for the street address vs the POI:

19450 Avenue 21 1/2, chowchilla, ca

by **CBenson** » Wed Feb 22, 2012 4:49 pm

They're returning pin locations on different roads. The waze result is on Ave 21. The google result is on Ave 21 1/2.

by **BrianCanFixIT** » Thu Feb 23, 2012 1:15 pm

I was searching for the POI name. I had added the street numbers directly into waze & searching for the address directly works (it was not found before).
Bing's POI GPS location is still incorrect... I reported it to Bing. Thanks for helping.

by **BrianCanFixIT** » Wed Feb 22, 2012 4:42 pm

As far as I can tell, when the following street name is parsed, the last part of the street name is ignored by the the client:
19450 Avenue 21 1/2, chowchilla, ca
When the address is parsed from bing directly (no GPS point, but the actual address) the following is returned:

As far as I can guess, this is caused by the last part of the street's name being chopped off somewhere in the code...

Can anyone confirm is this happens in android or the beta version of the client when using Bing's address lookup (google search does not have this problem as it returns the GPS point... see below)

by **AlanOfTheBerg** » Wed Feb 22, 2012 4:45 pm

Are you looking this up by name or by full address?

I'm dense this morning, so I'm not getting what the problem is exactly? The only difference I see is the road is unmunched in one view and not the other. Is there a difference in routing or pin location?