What it took for Google to fix our address

When our Art of Living Austin center relocated to a new location one of our over enthusiastic volunteer created a point of interest and in his/her enthusiasm entered the wrong address. Only a couple of days later we realized the mistake and I don't know what that person did but Google started to call our place as permanently closed even though we have been thriving and operating since February 2016. 

Every one searching online used to complain that our address cannot be found. As secretary it became my job to get it fixed. First I tried the crowd sourcing approach and requested multiple people to suggest to google that the place address needs an edit and also indicate that the place is open for business. I can't say that this approach was a complete waste of time and effort for Google had fixed our address and called us open (for couple of days) only to revert back to wrong address and close again.  

It was mind numbing to say the least, I was clueless. Google answered itself and pointed me to mapmaker.google.com and I started proposing edits there only to be rejected in a couple of days after suggesting the edits. But unlike other places, this one has a regional lead and whom you can contact by posting on a forum, the process led to some revelation. 

Per Google guidelines any change to an address would mean that they would call it permanently closed until they some how completely verify the new one and apparently that was what was happening to our location. 

They suggested I remove the present location and create a new poi,  I couldn't get that to happen and again went back to forum. This time the regional lead took mercy on me and looked through the history and after verifying with me that the first entered address was wrong and all we were trying was to get the right address in, he made the change happen and in less than 24 hours after that both Google maps and Google search had our place as open and we were in business. 

The other interesting thing I noticed was that Apple maps uses Yelp for its poi (luckily for me Yelp was an easy beast to handle). 

Ios Maps vs Google Maps India

Recently when we went to Bengaluru, we took our beloved unlocked iPhone 4s with us (idea was to try with an Indian Sim card) to help us with phone access during our vacation. With the data plan we figured we could use the navigation also. Considering the charging of the phone is such a problem in India, I was hoping against hope that the built-in maps of iOS aka Apple maps would work for in US, I have found them to be battery saver and have come a long way since introduction. 

As they say, India is completely different dynamics at play and the Apple maps I was so hopeful about was up to no good. I had to change tactics and rely on Google maps. I wasn't expecting this extreme of a difference but Google maps are a few light years ahead of Apple maps. 

In places where Apple maps was struggling with GPS lock on my location,  Google map was able to give me point to point and turn by turn directions including details on service roads and one way too. 

With the driver we had hired for Bangalore trip, we survived solely thanks to Google Maps.

On the same note, traffic overlays on Google maps is extremely accurate and I admit I have a new found respect for Austin traffic after encountering Bangalore traffic.

So, a piece of advice if you are interested in taking your iPhone to India make sure it has Google Maps.     

  

Not so smart Google maps

I have come to rely on  Google maps for everything related to  travel, so much so that I no longer carry my stand alone trusted Garmin gps with me. It works fairly well in most cases but did utterly bad in one case. The recent example was when Google maps was showing my destination to be in the middle of an elevated freeway, while my actual destination was on the access road of the freeway.

Made me think about the addressing schemes, if the address is something like xxx on yyy freeway, then can I really blame Google for asking me find my destination on an elevated freeway. Another possibility is that the address of the destination existed and the freeways had a make over and became elevated to add more roads underneath. At which point, may be the address ought to have been updated to reflect the change in road schemes but didn’t for some reason, Again benefit of doubt Google. But considering Google is smart and it’s applications like Google maps are one of the best it should realize the destination can't be on an elevated freeway. Yes, I tried both Android and an iOS device with the same result.

All the above being true, the irony was, the blue icon for destination was showing the right location (on the access road) using which I used to reach my destination by manual navigation but the automated routing was telling me to jump off the freeway.

I think its the case of not so smart Google for once :).