I recently added support for it to my blog (which uses twyne.rtfd.io) so I could more easily geolocate photos (from my non-GPS camera), and it was pretty easy to integrate. I tried GPSLogger too, but found that battery life was much better with Overland, and it also has a better system of queuing points when offline (with GPSLogger I found that it lost data at times such as when there was an internet connection but the server wasn't responding).
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...
Apple applies a set of measures designed to make sure an app can only detect the users location if it has opt-in permission and if it is using Apples location services so they can control it. And if someone finds a way around it they might find it blocked in the next update.
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
[3]: https://github.com/aaronpk/Compass
[4]: https://owntracks.org/booklet/ideas/