Comment Re:Is this how they can do wifi location detection (Score 1) 237
There's a ton of misunderstanding here about what's going on. The quick answer is that yes, you degrade it if you're the only BSSID in the area (or the majority, eg bringing two BSSIDs into an area with only one).
First off, Google is trying to build out its own WiFi augmented location services so they don't rely on SkyHook's (currently larger and more robust) offering. Keep in mind, the iPhone/iPad/iPod Touch OSes are the major SkyHook clients, and recently Motorola announced they were ditching Google's smalller/less reliable location service for this very reason on their own Android devices.
Both implementations are dynamic and self-repairing. That means that if a client reports back that one BSSID isn't in the locale as two other BSSIDs it knows -are-, SkyHook/Google will immediately know that something has changed. If the majority of BSSIDs match a given location, but another has changed or appeared, it'll eventually be incorporated with time and if clients continue to report consensus. If a client comes in with GPS and WiFi is turned on, it's given priority and reports back to SkyHook the current visible BSSIDs for updating their database with the GPS data as well. Obviously, because the client has a GPS fix, it'll be given a higher weight and update that database pretty quickly.
The cool part here is that mobile devices are building out the location services data each time they use it - it's in fact evolving, healing, and getting better. Fire up Maps on any of the major platforms, and you're helping Google and SkyHook both.
I recently experimented with this myself. I moved from one location to another across town, and brought along my two wireless APs (one of them dual band N, so a total of 3 BSSIDs) and fired up location services in my new location. On the iPhone and Android clients, the initial quick fix showed me in the old location. Trying with locate me on google maps also showed me at the old location. Then cellular data came in and showed me roughly across town where I was. Then GPS got a fix, and put me very close to my real location indoors. This is how it's supposed to work. At this point, the device reports back the BSSIDs visible with the GPS fix to whatever service is in use.
I tested over the course of a few days and noticed that the iPhone client had updated the SkyHook database within a day and was now identifying - from WiFi - that I was in the right place. You can test that with an iPad (no 3G, just WiFi) or iPod Touch with location services. The Android client has taken about a week which is more surprising. You can immediately see where (based on WiFi) the google database puts you by going to maps.google.com and clicking the location button.
Both SkyHook and Google likely use a similar architecture - it's essentially two big companies wardriving and finally doing some math armed with signal strength and GPSes. Except now *everyone* is wardriving on their smartphones, and they don't really realize it.
First off, Google is trying to build out its own WiFi augmented location services so they don't rely on SkyHook's (currently larger and more robust) offering. Keep in mind, the iPhone/iPad/iPod Touch OSes are the major SkyHook clients, and recently Motorola announced they were ditching Google's smalller/less reliable location service for this very reason on their own Android devices.
Both implementations are dynamic and self-repairing. That means that if a client reports back that one BSSID isn't in the locale as two other BSSIDs it knows -are-, SkyHook/Google will immediately know that something has changed. If the majority of BSSIDs match a given location, but another has changed or appeared, it'll eventually be incorporated with time and if clients continue to report consensus. If a client comes in with GPS and WiFi is turned on, it's given priority and reports back to SkyHook the current visible BSSIDs for updating their database with the GPS data as well. Obviously, because the client has a GPS fix, it'll be given a higher weight and update that database pretty quickly.
The cool part here is that mobile devices are building out the location services data each time they use it - it's in fact evolving, healing, and getting better. Fire up Maps on any of the major platforms, and you're helping Google and SkyHook both.
I recently experimented with this myself. I moved from one location to another across town, and brought along my two wireless APs (one of them dual band N, so a total of 3 BSSIDs) and fired up location services in my new location. On the iPhone and Android clients, the initial quick fix showed me in the old location. Trying with locate me on google maps also showed me at the old location. Then cellular data came in and showed me roughly across town where I was. Then GPS got a fix, and put me very close to my real location indoors. This is how it's supposed to work. At this point, the device reports back the BSSIDs visible with the GPS fix to whatever service is in use.
I tested over the course of a few days and noticed that the iPhone client had updated the SkyHook database within a day and was now identifying - from WiFi - that I was in the right place. You can test that with an iPad (no 3G, just WiFi) or iPod Touch with location services. The Android client has taken about a week which is more surprising. You can immediately see where (based on WiFi) the google database puts you by going to maps.google.com and clicking the location button.
Both SkyHook and Google likely use a similar architecture - it's essentially two big companies wardriving and finally doing some math armed with signal strength and GPSes. Except now *everyone* is wardriving on their smartphones, and they don't really realize it.