New Topic

Locus Map - help desk Topic Idea Locus Map (Android)

Category Locus Map (Android)

Tags laps, statistics

Comments 8

Subscribers 4

Votes 3

Add stage distance & average speed statistics

Andrew Heard shared this idea ago

Gathering feedback

I participate in long distance cycling events where each stage/ leg may desire a different target average speed - eg. hilly/ steep stages slower average. At present I use Locus to display the overall (recorded track) moving and elapsed average speed, and use my dedicated Cateye cycle computer to display the stage distance/average speed by clearing the cycle computer distance at the start of each new stage - sometimes forgotten. These new statistics (stage distance/ stage average speed) could be chosen as fields to be displayed in the dashboard or custom screen. There would need to be a button that could be added to the dashboard to clear the stage distance. They needn't be displayed elsewhere (not relevant to recorded track statistics). There would be no impact, or even be visible, to any user not using a dashboard or custom screen. "behind the scenes" there could just be stage distance and stage elapsed time counters.

I like this idea 0

Replies (1)

Michael Bechtold ●

Relates somewhat to earlier requests to turn the fixed 5km lap stats into something useful ...

Reply URL

Andrew Heard ●

Michael - any link to that topic? I've always ignored the track Laps tab but after your comment I've just had a look. A fixed 5km "lap" makes no sense at all to me - eg. I have a 100km track and there is a row in the table every 5km. Weird.

URL

Michael Bechtold ●

Hi Andrew, these are the links I found:

http://help.locusmap.eu/topic/mark-a-section-of-a-track-and-get-statistics-for-it

http://forum.locusmap.eu/index.php?topic=4748.0

http://help.locusmap.eu/topic/manual-lap-times

It is not exactly the same as asked in above, but it falls into the same bucket.

1) laps should be applicable to the track currently being recorded

2) dashboard should be relative to a chosen starting point, i.e. a lap boundary; relative values are time elapsed, distance, any averages, etc.

Current dashboard becomes a special case of #2, relative to the start of the first lap.

Cheers

Michael

URL

Andrew Heard ●

Thanks Michael. I voted in the 1st link. As you observe my proposal is similar to a single "lap". I don't really like the term lap though, it implies going around a simple loop course. I used the term stage to imply each lap/ stage/ leg/ (section) could be completely independent. I still find it hard to believe a fixed 5km lap could be of any use to anyone.

URL

Michael Bechtold ●

100% agree - any fixed distance is useless.

And I am happy to learn from a native speaker :-)

URL

Andrew Heard ●

>And I am happy to learn from a native speaker :-)

I've had to coordinate translations in my own Windows software which had very technical terms. A very difficult business to get precisely correct in each language.

URL

Menion ●

Hi guys, just a short note ...

"stage" sounds good
distance is not fixed to 5km, it may be freely defined in top toolbar
I use it almost every day for may small running trainings, where I check my speed over 400 m long "laps". It's anyway my use-case ...

EDIT: btw "track laps" idea is made based on this request: http://help.locusmap.eu/topic/kfiph8nrhsk2j

URL

Michael Bechtold ●

FIXED is the fundamental issue.

In the same track one may be 500m, the next 3km, then 300m, etc.

URL