Open Source Geolocation: The story & challenges ahead
summary
History of Geoclue, why it was rewritten, and what actually works: a single service now aggregates city-level for IP lookups, cell‑tower coarse fixes, USB/Bluetooth GPS via a new GPSShare bridge, and the best results come from a Wi‑Fi database that yields street-level for Wi‑Fi accuracy; geocoding delegates to OpenStreetMap/Nominatim. Privacy is enforced by a desktop permission agent for sandboxed apps only; system apps lose enforced privacy. Current risks: core maintainership gaps, legacy platform ports, and an ongoing rewrite and contributor drive (GitLab, Flatpak, Outreachy/GSoC) to make the service robust.
AI-written summary · about
chapters (22)
- 0:00Intro
- 1:16The story
- 3:45The concept
- 4:20Typ
- 5:04WiFi
- 5:34GPS
- 6:58Geo Clue
- 8:34Architecture
- 9:10Geocoding
- 9:46Conspiracy concerns
- 10:08Afterposition
- 11:07Sources
- 11:49Modems
- 12:34Challenges
- 13:14Yahoo
- 13:57Android App
- 14:31GPS Share
- 15:24Mitigation
- 16:04Flatpack
- 17:04Challenges ahead
- 18:25Rewriting the service
- 19:27Questions
related talks
24m"Are Geospatial Tools Supposed To Bring Us Closer To Place?"
04mOpen WiFi Geolocation with Geomena
20mOverview of different geo APIs
05mGetting to Know SimpleGeo
26mAffordable & Simplified geolocation asset management solution w/LoRa Edge™
16m"Ubiquitous GeoContext"
17m"Innovation Through Open Location"
14mThe Future of Android Location Services