Google and others do an impressive job of providing geolocation information based on WiFi signals only, possibly aided by mobile phone cell tower information. WiFi geolocation is based on MAC address information of WiFi hotspots in sight.
While this works great with stationary WiFi hotspots there are issues with ever increasing numbers of mobile WiFi hotspots, including Google’s own Android “Wi-Fi Hotspot” feature turning ordinary cell phones into mobile hotspots.
If one happens to be connected to one of these “migratory/roaming” hotspots the geolocation algorithm is defunct and appears to put this device into whatever place it has been for a prolonged amount of time in recent history. This leads to that e.g. my location jumps back and forth between my actual location and a previous one, depending on if some other signals dominate and allow the current location to be correctly identified or only the WiFi hotspot signal is available, placing me into wherever this roaming hotspot happened to be over the past weeks.
Obvious solution: identify “roaming” MAC addresses and create a special case in geolocation algorithms for those. Do not determine current location based on historic locations of roaming MAC addresses only. In particular Android knows already the MAC address of its own cell phone. Do tell the Google algorithm this is not a trustable geolocation source based on the fact it is a mobile device.
Stretch target solution: provide an active “push notification” mechanism by which mobile devices (opt-in) can report their current location to geolocation algorithm sources in an anonymous way that does not allow tracking of the user/device but just provides correct correlation between MAC address and location. Then the algorithms would work again correctly that use the MAC address only for geolocation.
Too long…