Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • G geoclue
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 33
    • Issues 33
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 16
    • Merge requests 16
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Terraform modules
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • geoclue
  • geoclue
  • Issues
  • #64
Closed
Open
Issue created Mar 01, 2016 by Bugzilla Migration User@bugzilla-migration

Use WiFi geolocation for CITY-level accuracy

Submitted by Sebastian Keller

Link to original bug (#94352)

Description

GeoIP lookup with city-level accuracy, as used by gnome-weather, always gives a wrong city with my ISP. This is not just a slight inaccuracy, but sometimes the cities are several hundred kilometers away. Using the exact-level accuracy on the other hand gives the right location. This is due to it using WiFi information to determine the location.

So using the WiFi information by default when city-level accuracy is requested would do the right thing in more cases. However this also has privacy implications since it means sending more user data to the lookup service and giving the application a more accurate location than it actually requested. While there is no way of avoiding the former, the latter can be mitigated by slightly randomizing the location if just city-level accuracy was requested.

Edited Mar 05, 2019 by Bastien Nocera
Assignee
Assign to
Time tracking