Our great sponsors
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
The OSS build of the Android app doesn't depend on Google Play Services, and is currently available from the github release page: https://github.com/owntracks/android/releases (and has been since v2.4.0 released last year).
> Whats the point of half measures like this
Personally, I don't care about Google knowing my location. I care about having my location data on a system I control so I can do useful things with it.
The ownTracks docs for beacons is at [1,2], whereas there an open issue on the Overland repo suggesting something similar [3].
I think that getting a location [4] and detecting the presence and proximity of beacons [5] use different parts of the Core Location API.
[1]: https://owntracks.org/booklet/guide/beacons/
[2]: https://owntracks.org/booklet/features/beacons/
[3]: https://github.com/aaronpk/Overland-iOS/issues/93
[4]: https://developer.apple.com/documentation/corelocation/getti...
[5]: https://developer.apple.com/documentation/corelocation/deter...
I can't recommend other than https://gpslogger.app/
An alternative is the Overland app for iOs [1] or Android [2], logging to compass [3]
Each has features that the other doesn't: OwnTracks can apparently determine a location using iBeacons, whereas Overland can't (though it can detect WiFi networks). Overland lets you record your mode of travel (e.g., driving, cycling, walking), whereas this still seems to be an unimplemented "idea" for OwnTracks [4]. Compass is also designed for tracking a single person, whereas OwnTrack can handle multiple.
[1]: https://github.com/aaronpk/Overland-iOS
[2]: https://github.com/OpenHumans/overland_android
An alternative is the Overland app for iOs [1] or Android [2], logging to compass [3]
Each has features that the other doesn't: OwnTracks can apparently determine a location using iBeacons, whereas Overland can't (though it can detect WiFi networks). Overland lets you record your mode of travel (e.g., driving, cycling, walking), whereas this still seems to be an unimplemented "idea" for OwnTracks [4]. Compass is also designed for tracking a single person, whereas OwnTrack can handle multiple.
[1]: https://github.com/aaronpk/Overland-iOS
[2]: https://github.com/OpenHumans/overland_android
As far as I know, owntracks doesn't actually store location history, it only defines a protocol for exchanging current location info between programs. If you're using their "official" recording server, writing a script to import history looks super easy [1].
[0] https://github.com/owntracks/recorder/blob/master/doc/STORE....
I work on the OwnTracks Android client.
There is a build (the "OSS" flavour) that doesn't use any of the Google dependencies, and it's currently waiting to get merged into the F-Droid repo (https://gitlab.com/fdroid/fdroiddata/-/merge_requests/10698). If you can't wait for that, you can grab the APK from the releases on github.
If you'd like to contribute the OpenStreetMap community, I suggest OSMTracker. https://github.com/labexp/osmtracker-android/wiki
It keeps your traces local until you choose to share them. Uploading GPS traces helps with quality control in terms of road speeds and discovering trails.