Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • G geoclue
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 32
    • Issues 32
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 11
    • Merge requests 11
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • 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
  • #148

Closed
Open
Created Sep 26, 2021 by Chris McGee@newton688Contributor

Differentiate heading into the course of travel and direction

Currently, geoclue uses the "heading" field to combine both of these concepts even though they are distinct. The device could be pointing at 25 degrees, but moving on a course of 115 degrees. As a result, sometimes the compass is overriding the heading taken from the GPS or from the calculation of the angle of movement between current position and the last known position, which confuses both compass applications and navigation applications, which have different purposes.

Recommendation is to split these two out into new fields (e.g. course and direction) so that application may use the value that suits their task.

Assignee
Assign to
Time tracking