Autofit confusing control 1 and the Start

[michael-77]

When adding a track to https://www.elo.routegadget.co.uk/rg2/#166 and using "Autofit" the track is moved to start at control 1 rather than near the actual start leading to an unusual looking track.

For testing purposes here is the GPX file for Emily Atkinson on the Green course: https://drive.google.com/file/d/1shuyGp6Gt0UAiuncgzGCwKsc6iJMgt_Q/view?usp=sharing

[Maprunner]

I've never seen this exact behaviour before but now I understand what is going on I'm surprised it doesn't happen more often. It does require a very short first leg to make it show up like this.

The autofit function assumes that the GPX track starts at the time the runner starts. This GPX file starts just over a minute before the actual start time, during which time the location is essentially stationary (in the start lanes). You can see this by doing a replay of the unadjusted track. The dot doesn't start moving until about 68 seconds in. The first leg only took 45 seconds, at which time the location in the GPX file was still at the start which is why that is where the track starts after autofitting.

My standard advice is that you need to make sure you start your watch at the start, or edit the GPX file to remove any extra time. There is no easy solution that I can add to Routegadget itself.

I'll add some more detail to the Routegadget UK User Guide to explain this a bit better.

[michael-77]

I've just also identified the 1 minute early start!

I had tried to use the offset but it seemed to max out at 10 seconds which clearly wasn't enough.

Thanks