Unexpected behavior comment (handle gaps in logging data)

Hey hi, love your program. Just been playing around with it for about a week now. I'm in the midst of finding good "best practices" uses for it before a lightning talk in my area about NextCloud.

Today I thought of recording personal business mileage for American tax reporting purposes. Most apps that try to address this suck. What I did (and I'm using GPSLogger for no particular reason) was to add a second session on my NextCloud, then reserve names for Commuting and Deductible in that session. On my mobile device, I added 2 new profiles in GPSLogger to accommodate the two types of mileage. I set my device into the Commute profile and went to the first stop. Before leaving the first stop I switched the device's profile to Deductible, then drove to 2 more locations. At the second location, I switched back to the Commute profile and drove home.

When I displayed the days driving, something unexpected happened in the displayed data in PhoneTrack on my NextCloud server. The PhoneTrack software spuriously made a linear connection between the end of the first commute segment and the start of the second commute segment. If I use your stats tool to get summary reporting on my mileage, that extra line boosted my commute by 4.2 kilometers; 10.17 instead of 5.97.

I can easily think of a way around this for daily stats, but it's still a problem for multi-day aggregate statistics. Perhaps a software solution would be a warp speed test function? Like if the line it is going to draw isn't possible for human transportation methods, it doesn't draw the line? Or maybe a timeout test, like the time gap it was connecting was from 14:23 to 15:05.