Hi Doug,

thanks for looking into this. Regarding your questions:

1. The destination field will show "Moved by GG" instead of the plus code.

2. I will try changing my starting location - but for the moment, I did the 
opposite and generated random plus codes ending in "+HM". "H&M" is a 
company with stores all across Europe, so there should be a store nearby 
for many random locations. So far, it seems as if H&M stores are sometimes 
found for my home region (say, a 25km radius around my location and 
"travelmode=bicycling"), but not anywhere else (across Germany, Europe or 
world-wide, with "travelmode=driving" or not specified at all).

Regarding the latter, I wonder if map data cached on my device might 
interfere here, and show the wrong results just within my own home region.

On Friday, May 17, 2019 at 10:46:28 AM UTC+2, Doug Rinckes wrote:
>
> Hi Andreas, that looks like a geocoding bug. Fortunately we sit with that 
> team.
>
> A couple of questions:
>
>    - what does the destination field say - is it still the plus code, or 
>    does it say "Moved by GG"?
>    - if you change your starting location, does it navigate to the 
>    correct location?
>
> If you are willing to share the approximate location you're starting from, 
> email me at (first initial)(surname) at google.com and I'll get someone 
> to look into it. 
>
> Thanks!
>
>
> On Friday, 17 May 2019 00:14:45 UTC+2, Andreas B wrote:
>>
>> This seems to be more of a Google Maps issue than one with OLC - but I'm 
>> really not sure how to condense all of this into an in-product bug report 
>> and still be understood. I hope this reaches the right people anyway. :)
>>
>> Basically, what I'm doing in an Android app is to
>> 1. Generate the plus code for a location,
>> 2. create a Directions URL with that plus code and a travelmode according 
>> to: https://developers.google.com/maps/documentation/urls/guide
>> 3. use this URL to create an Intent that will open the Google Maps app on 
>> the device.
>>
>> This generally works fine, but every once in a while, the destination 
>> will be in a completely different place than it should be. For example, 
>> starting the Maps app for Android with the random plus code *9F4C4R3C+GG* 
>> as destination, instead starts a navigation to a nearby point of interest 
>> named "Moved by GG" (Place ID: ChIJC-gFx1htukcRAwAfwCT0x5s). The fact that 
>> both the plus code and the place name end in "GG" is probably not just a 
>> coincidence - apparently, the random place name is matched before the 
>> destination search string is identified as a plus code?
>>
>> Trying to open the same URL in a desktop browser window doesn't show the 
>> same behaviour, but instead starts a navigation to the correct location as 
>> defined by the plus code: 
>> https://www.google.com/maps/dir/?api=1&destination=9F4C4R3C%2BGG&travelmode=bicycling
>>
>> I assume that the Android app behaviour only works like this if the 
>> user's location itself is somewhere nearby. If a random location between 
>> those two relevant locations won't do, feel free to contact me for a 
>> location that does.
>>
>>
>>
>>

-- 
Public site: http://www.openlocationcode.com/
Github project: https://github.com/google/open-location-code
Demo site: http://plus.codes/
--- 
You received this message because you are subscribed to the Google Groups "Plus 
Codes Community Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to open-location-code+unsubscr...@googlegroups.com.
To post to this group, send an email to open-location-code@googlegroups.com.
Visit this group at https://groups.google.com/group/open-location-code.
To view this discussion on the web, visit 
https://groups.google.com/d/msgid/open-location-code/58ec71ff-25c0-4979-8593-15d31dc9c387%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to