Skip to content

OwnTracks may publish low-accuracy location before location services have time to converge #2289

Description

@routersecskisthedude

I have noticed what appears to be a timing issue with location reporting.
On my device, OwnTracks is often the only application actively requesting location updates. When OwnTracks triggers a location update, the operating system initially provides a location estimate that can have relatively poor accuracy, especially when the device is indoors (for example, inside a shopping mall or office building).
It appears that OwnTracks publishes the location to the configured endpoint as soon as the first location is received. However, location accuracy often improves significantly a few seconds later as GPS acquires a better fix and/or Wi‑Fi scanning results become available.
As a result, the reported location can be less accurate than the device's final location estimate shortly afterward.

When a location update is requested, OwnTracks should ideally have an option to:
•Wait briefly for location services to converge.
•Consider the reported accuracy before publishing.
•Prefer a more accurate location fix if one becomes available within a short time window.
•Allow users to define a minimum accuracy threshold before sending an update.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions