[mynameisvlad]

You didn't explain how they knew about the PH/BP, which makes people assume it was due to location data (like your first example).

However, as for comment #1, Google doesn't use the SSIDs to determine locations on mobile, they use the [MAC Addresses](http://static.googleusercontent.com/media/www.google.com/en/...). They do have a database that also includes SSIDs for these MAC addresses, but there could be a dozen SSIDs around you at any given time, and you could be at any one of those businesses. I have already explained that Google uses coarse location to determine your location, not fine because of battery issues (and you can check this in Android, it's listed under the lower-power location use). Coarse doesn't use GPS, and its accuracy is generally 100+ meters because of this. It will know the general area you were at (and, no, it won't know you were there for 10 minutes, as it only picks up your location at fixed intervals which IIRC is above 10 minutes), but it won't know, specifically, where you were in that area.

I will concede on the Pizza Hut location, but it would have only known you were there because of the review, not because of the location (for the same reason as above).

[nick_riviera]

I purposely avoided explaining it to demonstrate a point: the average user doesn't know this or understand it. They understand the outcome only.

Sorry, you are 100% correct with the SSID vs MAC. If I'm in my car with the handset externally powered, does it use course location or does it use all three sources because on KitKat on my Moto G, it gives me the option to use all three at cost of battery life?

I disagree with your assessment of the location ability. It's definitely better than you explain it. I can go through at least 100 previous data points in my history and it's spot on each time.

[MertsA]

The way Google gets your approximate location is not as simple as just sending Google a list of visible access points and figuring out where the Google Maps car was when it saw that access point, it also passes along the signal strength of every access point and because the Street View car is recording signal strength and GPS location for every measurement as it's driving by it allows for a much finer resolution than just a binary "can I see this access point".

Basically, even though there was a dozen access points visible, that increases accuracy, not decreases. Like if your phone reported that it's got the same signal strength for BP and PH it will estimate that you are in between them with other access points helping to conclude that you aren't off to the side otherwise the signal strength to xyz access point would be higher.

In other words, Just sending a list of access points and signal strengths to Google gives them a rather accurate guess as to where you are in the world, much greater than just 100+ meters.

Also, Android can also figure out when you are in a car moving at highway speeds thanks to the accelerometer and is quite accurate at telling when you're walking, jogging, biking, or driving. Enable Google Now on your phone and it will send you a summary of how many miles of what activity you've done in the last month with rather surprising accuracy for me personally.

[threeseed]

You haven't explained why Google wouldn't know about PH/BP.

In Apple's implementation which I do know well the WiFi triangulation is enabled even at the coarsest resolution. Which is obvious since it is low cost. So if indeed there is one SSID/MAC in the area and it is coming from BP why would Google not know this ?

[mynameisvlad]

The presence of a SSID isn't indicative that you went to said business. If I lived above a McDonalds, Pizza Hut, and Subway, all with their respective SSIDs, that doesn't mean I am at any of the businesses. So sure, Google could know that there's a Pizza Hut near you, but they have no way of knowing whether you're actually at the Pizza Hut, or, say, the Tesco next door.