Local caching for live tracking when out of data signal

daylightgambler shared this idea 4 years ago
Collecting votes

Would it be possible to add local caching to the live tracking so locations are sent from when the phone is out of data signal?


For implementation I envisage it working something like:


- In a live tracking profile, users can opt to use caching


- Caching is unavailable for GET requests (as data length is limited and you do not want to poll a url multiple times in a short time)


- For POST requests, Locus sends (if data available) a cache variable which is an array of locations (in the same format as the live beacon).


On the receiving server:


- any local authentication etc.


- process live location


- check for cache variable


- if present and supported, process cached locations


As an extra bonus, Locus could detail how many cached locations are stored in notifications (with where it currently reports successes and failures), and provide a way of manually sending the data to the server (example is when you finish a walk out of signal - you stop the tracking, but want to share the outstanding locations when you are back in signal.)

Comments (7)

photo
0

Yes please! Then I can use Locus Pro exclusively when going on hikes instead of relying on Viewranger (has out of signal caching) which chews up device memory and adds to battery drain.

photo
0

Caching live tracking locations would be very useful because when I`m out hill-walking it is rare that I have data signal on my phone for the whole walk (which potentially results in large gaps in transmitted locations), so I`m very much in favour of this idea :-)

photo
1

I don`t see the problem with GET, you can absolutely pull a url multiple times in a short period. And if it is a problem, make it up to the user to pick the proper way to send the data.

photo
1

I would also appreciate live data caching while offline. But keep it simple in Locus... just hammer the server with multiple URLs in short order. Cant see any problem with that really, as long as you keep them in sequence.

photo
1

If you add a timestamp in Locus, you can send them in "parallel" (at least you won't have to care in the client).


Aggregation would be nice though, so that you don't DOS your own server.

photo
1

there could always be some throttling, e.g. 1 sec delay between multiple live-tracking requests for cached positions, once network is available again.

photo
photo
1

I travel alone in deserted areas, often without a network. It would be great if the live tracking was cached. When the network is available, all cached data should be uploaded.So that my route is visible and one can guess which way I follow.