LiveTracking in MapMyTracks

[kbz]

Hi support ^^



I setup OruxMaps to connect with MapMyTracks for real time live tracking (username password & public activities), when I record a trace I can't anything on my mapmytracks account ?



Is there any thing I am missing ?

[orux]

Hi support ^^



I setup OruxMaps to connect with MapMyTracks for real time live tracking (username password & public activities), when I record a trace I can't anything on my mapmytracks account ?



Is there any thing I am missing ?

Hi;



you have to enable live tracking under 'tracks' button after starting recording a track,



orux

[Uli]

Just one additional question to the topic:

I notice that I do not lose any data when livetracking

on mapmytracks, even when there is a short interruption

to the internet while biking.

That happens when I cross boarder and have roaming

switched off sometimes fot hours.

How long will Oruxmaps store the gps data and later

send it to mapmytracks when there is an internet connection

again?

Uli

[kbz]

Ho Orux,



You advice was OK it work like a charm.



Thank you.



Uli > Make a test, cut you sim & wifi, record a track & enable wifi after 1/2 1h 2h ...



bye

[orux]

Just one additional question to the topic:

I notice that I do not lose any data when livetracking

on mapmytracks, even when there is a short interruption

to the internet while biking.

That happens when I cross boarder and have roaming

switched off sometimes fot hours.

How long will Oruxmaps store the gps data and later

send it to mapmytracks when there is an internet connection

again?

Uli

Hi;



Wait as long as necessary, but sends only 50 points, so it is eliminating intermediate points if there are many.



For example, if you have accumulated 200 points without sending, OM will send the points at positions 0, 4, 8, 12, 16, ...





orux

[Uli]

Ok, thank you very much for explaining.

So it means when I increase gps interval time,

I could stay offline for a longer time without losing

data.

Thank you again.

Uli

[Uli]

Sorry, I cant find where I can shorten the time when data is send to

mapmytracks for livetracking.

I was told that MapMyTracks stops livetracking when there was no

incoming data for 60s. That means the track on the browser screen freezes and the

has to be started new.

Is there a solution or is it that I just cant find the parameter?

Uli

[orux]

Sorry, I cant find where I can shorten the time when data is send to

mapmytracks for livetracking.

I was told that MapMyTracks stops livetracking when there was no

incoming data for 60s. That means the track on the browser screen freezes and the

has to be started new.

Is there a solution or is it that I just cant find the parameter?

Uli

Hi, Uli;



Could you confirm, with any of your tracks, that mapmytracks stops live tracking after 60 seconds? Current version sends the data each 120s, so all the tracks should be broken.



Anyway I am going to reduce that value to 20s. Please note that sending a pack of 50 coordinates each time, in two minutes could be sent almost a coordinate every 2-3 seconds, which is an acceptable value for any type of activity.





orux

[Uli]

ok, Jose,

Nick from MapMyTracks told me that MMT needs gps data in less then 60s.  Otherwise livetracking would stop. I see on my browser that other users (using mmt?) hitch every few seconds a bit further. My friends (using OM) linger on one spot for a long time and then the liveblinking stops. That doesnt mean that new gps data isnt stored there. The tracks are always compleat.

It would be great to give it a try with 20s.

[orux]

ok, Jose,

Nick from MapMyTracks told me that MMT needs gps data in less then 60s.  Otherwise livetracking would stop. I see on my browser that other users (using mmt?) hitch every few seconds a bit further. My friends (using OM) linger on one spot for a long time and then the liveblinking stops. That doesnt mean that new gps data isnt stored there. The tracks are always compleat.

It would be great to give it a try with 20s.

Thanks, Uli;



Next beta will use 20 seconds,





orux

[Uli]

Thanks in advance.

Although it would be more sensible when MMT would prolong

the timeout.

But I dont think they will do that because they want their app

to be used.

I think, some time ago there was an OM version, where one could

choose the data send time to MMT?

To me 20s seems to be a bit fast because data cosumption might

suffer a bit.

But anyway, me and my friends would be happy to try 20s.

Uli

[orux]

Thanks in advance.

Although it would be more sensible when MMT would prolong

the timeout.

But I dont think they will do that because they want their app

to be used.

I think, some time ago there was an OM version, where one could

choose the data send time to MMT?

To me 20s seems to be a bit fast because data cosumption might

suffer a bit.

But anyway, me and my friends would be happy to try 20s.

Uli

Hi, Uli;



Yes, there was a version where you could select a time interval, but it could cause problems of overhead to the servers.



Do not worry about data consumption, we are talking about very small data packets, and if the time interval is short, then also the data packets will be smaller.







orux

[Uli]

I suppose you didn't get around to a version with

increased frequency of data update to mapmtracks

for livetracking?

Or did I overlook something?

Uli

[orux]

I suppose you didn't get around to a version with

increased frequency of data update to mapmtracks

for livetracking?

Or did I overlook something?

Uli

Hi, Uli;



changed in last beta10 to 20 seconds.





orux

[Uli]

Thanks a lot.

I`ll give it a try tomorrow morning and let you know.

Uli