Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • A Android-IMSI-Catcher-Detector
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 162
    • Issues 162
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 5
    • Merge requests 5
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • 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
  • CellularPrivacy
  • Android-IMSI-Catcher-Detector
  • Issues
  • #325
Closed
Open
Issue created Feb 16, 2015 by Administrator@rootContributor

Truncate measured and used Lat/Lon GPS coordinates

Created by: E3V3A

There is no reason to have, use or store 16 decimal digits to the Lat/Lon GPS position, ever. Especially since the GPS accuracy is rarely better than 1-10 meters. Thus, because the approximate maximum precision of decimal Lat/Lon GPS values only varies between 11 to 0 meters, when using 4 decimal places, in going from equator to the pole, we can be happy to truncate all our stored and displayed GPS values to 4 decimal places.

Justification: If you're standing on the street and can't see an fake BTS antenna within a radius of 10 meters, you will certainly not see it, even if it's next to you.

Assignee
Assign to
Time tracking