Track me map setting

Just as for any activity, you can select to have one or two data fields overlayed on the map in the Track Me activity as well. When I tried doing that, the watch refused to show any other data item than speed. Why?

Top Replies

apersson850 over 3 years ago in reply to Ɛpsilon +1

Yes, you're right. Today it works for me too. Now I'm on 19.78. When I tried last time I was on 19.77. If that's the difference I don't know.

When I tried last time I could get the speed…

All Replies

0 Ɛpsilon over 3 years ago

Isn't "Track Me" just a basic, "here you are" type tracking so there are probably very few data fields it has?

0 apersson850 over 3 years ago in reply to Ɛpsilon

It's described as a tracking activity, where the only difference is that it doesn't update your physical data evaluation. Thus it doesn't change your VO2-max, training status and such. It can be used to track a trip in a car, for example, if you want to save the track, but it's not training.

I can't see any reason why you wouldn't want to see the distance or elevation or whatsoever, overlaid on the map, just because you use Track Me.

0 Ɛpsilon over 3 years ago

what I did was in the Track Me activity go to the map and then held down the menu button. Selected data screens. Changed the layout to 2 data fields then selected the first. Up and down changes the data fields category. Then select. This then enables you to choose a data fields type

0 apersson850 over 3 years ago in reply to Ɛpsilon

Yes, you're right. Today it works for me too. Now I'm on 19.78. When I tried last time I was on 19.77. If that's the difference I don't know.

When I tried last time I could get the speed data field (one field), and I could change the content to something else, but as soon as I confirmed my choice, it went back to displaying the speed.

0 Ɛpsilon over 3 years ago in reply to apersson850

AH,,, Now I HAVE seen that happen before - where it wouldn't let me put a certain field on that screen and would default to the original choice. This was much earlier than 19.20 - so it's possible there's a weird bug that appears....