Harry's GPS Suite Forum

I use two different routes home depending on the time of day, and I use Lap Timer to record the drive. I have each route set up with a directional "start trigger" a small distance from the intersection where my two routes diverge. Here's a screenshot:
Recently my drive that involves heading north from the intersection has been triggering the start trigger for the drive that heads west. Here's a screenshot from the lap data showing the issue:
Thoughts? I was thinking about rotating the west-heading trigger another 10-20 degrees so traveling north would hopefully not pick it up. The other option is moving the triggers farther from the intersection, but I already wish the triggers could be closer to the start of my drive to capture more of it.

The trigger we see in the snapshot is not the trigger that started the recording. LapTimer always calculates the starting point by creating the perpendicular projection of the trigger in scope to the current line driven (hope that is understandable English...). So if this trigger would have been the starting trigger, the first point would be to the right of "Leave Work-CB". Please note the track the recording is stored in, is defined by the stop trigger, not the go trigger. So in case the above lap is stored in "Work-CB" track, please check he stop trigger definitions.

- Harry

They're defined by the stop triggers?? That changes everything! I have the stop triggers for both routes home directly on top of each other right by my house because I (wrongly) assumed the start triggers were the pertinent data points.

So in this instance I'm triggering the "leave work-435" start trigger, but crossing the "arrived home-CB" stop trigger (supposed to correspond with the "leave work-CB" start trigger) which is causing the recorded 'lap' to be saved under the "leave work-CB" route as opposed to the "leave work-435" route?

Does this mean I can have both of my start triggers at the same point and split up the stop triggers based on different entrances to the neighborhood? Or do the start triggers AND the stop triggers need to not be overlapping?

Thank you for your help!

The complete truth is whenever a trigger fires, LapTimer looks up which track set it is belonging to and changes the "current track" to this track. This rule applies both for go and stop triggers. Whenever a lap is stopped, it is stored to the current track. These two rules result in a "yes" to your question. As the stop trigger fires later than the go trigger, it will define the current track und thus the track to which the lap is stored. I would consider it a good track set design to separate both the go and the stop triggers - this makes you independent from future design changed

- Harry

Much appreciated! Thanks for making a great app!