We're building an open-source back office for small ministries and missionaries, and we'd like to use Traccar Client for their mileage. Our server takes the OsmAnd positions, adds up each drive, and keeps only the miles and times.
I read the client source and found two ways to set the app up without typing anything: scanning a QR code that holds an https URL (with id, interval, distance and the rest as query parameters), and opening an org.traccar.client:// link with a url parameter, which asks the person to confirm. Two questions:
Can we count on the org.traccar.client:// link and those parameter names staying stable? A link the person taps on their own phone is easier for us than a QR code they'd need a second screen to scan.
For mileage on iOS, what settings would you use so a drive isn't undercounted when the phone's in a pocket with the screen off? We add straight lines between positions, so a long gap on a winding road loses miles. Is distance-based reporting (say every 100 m) more dependable in the background than a time interval, and does stop detection help or hurt here?
Thanks for the app. It's the right shape for what we need.
We're building an open-source back office for small ministries and missionaries, and we'd like to use Traccar Client for their mileage. Our server takes the OsmAnd positions, adds up each drive, and keeps only the miles and times.
I read the client source and found two ways to set the app up without typing anything: scanning a QR code that holds an https URL (with id, interval, distance and the rest as query parameters), and opening an org.traccar.client:// link with a url parameter, which asks the person to confirm. Two questions:
Can we count on the org.traccar.client:// link and those parameter names staying stable? A link the person taps on their own phone is easier for us than a QR code they'd need a second screen to scan.
For mileage on iOS, what settings would you use so a drive isn't undercounted when the phone's in a pocket with the screen off? We add straight lines between positions, so a long gap on a winding road loses miles. Is distance-based reporting (say every 100 m) more dependable in the background than a time interval, and does stop detection help or hurt here?
Thanks for the app. It's the right shape for what we need.