Mozilla is going to be dumping their “Mozilla Location Services” users. Retiring the Mozilla Location Service · Issue #2065 · mozilla/ichnaea · GitHub
This is a very big deal. the geoclue service it enabled is at the heart of most linux-based location services. Every distro, and the firefox browser itself, will need a replacement. Google Location Services, the runner up, is exactly what most MLS users want to avoid.
Wigle.net has a database of SSID sightings. I think OSM could work with Wigle to merge that data in to reduce shared costs and make it available for users to geolocate.
The idea is when your computer needs to know where it is to search for restaurants, etc, ip-lookup based geolcoation is very rough, and entirely useless if you’re using a vpn. Instead, your device can observe what SSIDs are around it and how close they are.
Then it can search for those SSIDs on a map, and make a very good guess of the laptop’s location if the map knows the SSIDs are all within a certain area your device is probably in the middle of it.
I have not noticed SSIDs on OSM though. Is there a rule against it?
I know there’s a point object for ‘wifi hotspot’ But it doesn’t have an SSID or mac address field, which it would need for this. A hotspot also doesn’t need to be open to help geolocate. if it’s merely visible/broadcasting then you can infer your location from it.
And if users are allowed to download/cache large areas of the map, then they can keep their exact location secret from the server itself.
Perhaps using geoiplocation or a prompt “what metro area or state are you in” you download all tiles of wifi/bluetooth ssids within 100 miles. Then your device can internally figure out where it is on those tiles! A laptop could reasonably cache all of a continent.