DATA FIELD: Lap By Position

Bringing back most of the features of the 310xt/910xt "Lap By Position" function.

!!! Requires GPS signal to function !!! (This may not work well indoors or if VERY poor GPS signal)

This data field uses your "GPS Start Position" as the autolap point. Every time you pass your start position the data field will auto lap and provide Last Lap Pace/Speed Distance and Time. In order to Auto Lap, your watch must be within 30 meters of your starting position and must travel 100 meters from the starting position. This prevents false laps, but is small enough to work on a standard 400m oval track.

NOTE: This does not update your FIT file, by placing laps in your FIT File. At this time Garmin SDK doesn't not allow the recording functions in a data field. This just provides real time lap information on the data field screen.

[URL="https://apps.garmin.com/en-US/apps/56ac6530-5b61-4ed2-9e2f-d682064efeb6"]"Lap By Position" Fields[/URL]
Current Pace/Speed** | Last Lap Pace/Speed **If no GPS Signal, "NO GPS" is displayed.
Current Lap Distance | LAPS | Last Lap Distance
Current Lap Time | Last Lap Time

"Lap By Position Simple" data
Up to 3 data information fits into single field and is configurable

SpeedPace / Laps / Timer (Current or Last)

CLPACE = Current Lap Pace
CLSPD = Current Lap speed
LLPACE = = Current Lap Pace
LLSPD = = Current Lap Speed

Lap = Lap number

CLT = Current Lap Tim
LLT = Last Lap Time

-The Last Lap Fields will update after the first lap.
-Showing of Pace and Speed is configurable through Garmin Express or Garmin Connect.
–All Display settings Metric/Statute are auto adjustable by user watch settings.
-Fields are auto-adjust for all data ranges for maximum readability through out your entire activity.
-Auto background color Black or White background based on app settings

All my Apps

webvan over 9 years ago

Thanks for another complex field and this one is especially interesting because there aren't any complex fields that cater to laps AFAIK ? Due to the GPS accuracy problems on a track though, could there be an option to use it with manual lapping and still keep all the info ?

Also would there be a way to enter a correction coefficient to try to get the actual pace and distance covered on the track ?

I think it would also be nice to have HR, maybe as an option instead of LL DIST as that's normally something you would know ?

Thanks again !

HarryOnline over 9 years ago

Simple data field?

I recently did a race on the track. In the past I used the old FR310XT lap by position, that worked great! So I was quite disappointed to see that this feature was dropped from my new Fenix 3, and considered building a data field for it, until I saw that you did this already, great!

But there is too much data for use in a race--just want to have the last lap time in a quick glance, and my eyes are not that good to quickly get that from so many figures. So what I would need is a simple data field, that just shows the last lap time. Can you make that, or are you willing to share the code for determining the time, so I don't have to reinvent the wheel?

It would also be nice if, after pressing the lap key, that position would be the new position to trigger a lap, instead of the original start position. especially when testing the app.

F3b Software (Brian) over 9 years ago

I recently did a race on the track. In the past I used the old FR310XT lap by position, that worked great! So I was quite disappointed to see that this feature was dropped from my new Fenix 3, and considered building a data field for it, until I saw that you did this already, great!

But there is too much data for use in a race--just want to have the last lap time in a quick glance, and my eyes are not that good to quickly get that from so many figures. So what I would need is a simple data field, that just shows the last lap time. Can you make that, or are you willing to share the code for determining the time, so I don't have to reinvent the wheel?

It would also be nice if, after pressing the lap key, that position would be the new position to trigger a lap, instead of the original start position. especially when testing the app.

Thanks, i'm aware that the data is to much, since I use this. I've reduced the screens all ready and looking to reduce the number of fields again.

Sorry in a data field Garmin doesn't give access to the button presses and position data. :(

Former Member over 8 years ago

Hello

Would it be possible to make the lap counting function into a single data field (as a second entry in the appstore)?
I would love to have it count, but find the complex array in your version a little too much to process towards the end of a track session ... :-)

Former Member over 7 years ago

Great concept but I agree, fontsize too small. Need reading glasses....