Split (automatic?) session

Yesterday, when I was sailing, a squall passed by… and naturally, the wind “slightly” changed direction during the squall’s passage.

I also do long navigations (80km) where the wind at one end of the route is not the same as at the beginning.

As a result, the wind calculation displayed by the application is incorrect.

It’s flattering at times, as I must sometimes sail at less than 10° to the wind :smiling_face_with_sunglasses:, but it’s not very realistic.

Could you implement “segments” and calculate the wind and sailing angles for each of these segments? This could be a calculation that the user launches manually or that the software performs if the distance traveled exceeds X km or Y time? If the segments are consistent, they can be merged. If there are inconsistencies within a segment (if automatic calculation is used), the system can split it further in search of inconsistencies.

I’m fully aware:
1/ that a calculation on the entire track can quickly become very resource-intensive (3 hours at 1 point/second makes ~11k points to analyze)
2/ that these ideas… must require a lot of lines of code during which you’re not sailing :open_mouth:

Cheers!

Hi,

I know this pain — at my home spot the wind regularly shifts direction from both sides of the beach.

A few things that can help right now:

Manual wind direction adjustment — you can edit this on the session edit screen, though it only gets you part of the way there.

Pause + session split — this is probably your best workaround for squalls. When the wind drops, hit pause. If the lull lasts 15 minutes or more with the recording paused, the session will automatically split into two clean segments. (I’m considering allowing shorter split intervals — worth thinking about.)

A proper solution for shifting winds is something we’re actively thinking through. It’s more complex than it looks to get right, so we’re taking the time to do it well. It’s on the roadmap, not forgotten.

Re: the 11k points — some devices log up to 18 points per second, so the count alone doesn’t tell the full story. Logging rate also varies by device.