User defined granularity of log points
-
I would like to request a the ability to define the granularity of trip points. As a motor boat travelling in excess of 15kts (cruise at +25kts) a lot of the time my tracks are not accurate enough when I travel. I see am traveling through land masses when cruising between islands or through a channel.
Maybe a high-speed and a low-speed option a user can set for how often a point is captured in the log.
thanks!
John -
Hi John, I thought we had addressed this as part of this thread. Isn't it working as expected?
In general, if you are moving fast, the granularity is automatically adjusted and can be as high as every minute.
-
Hi - Yes, we did - but I may have not understood that you had implemented a speed-sensitive granularity change versus just increasing the granularity one time. Also, I admit that I am being picky when i see parts of my track going across land or outside of channels. My last track of 7/8/25 shows me returning to Eagle Harbor, Bainbridge. I was at 10 kts approaching the channel (ferry wake and wind) and accelerated to 24 knots to the inside buoy. There is about 2.5 minutes between log points so it looks like i cut-the-corner, etc. That made me wonder if there was a way to adjust the granularity on a per-user basis. I know I am being picky.
-
As I already emailed Ilker, I would second @TargaDriver that granularity should be improved.
Ideally based on user settings. However, this would still require an intelligent cleaning algorithm. No need to record marks every few meters when going in a perfectly straight line.
However, high granularity required when slowly entering a barely chartered bay. As we won’t to follow our safe track next time we get there.
-
Hi @TargaDriver and @Voodoo, thank you both for the suggestion.
We understand the desire for more granular tracking in certain situations. That said, a key part of Saillogger’s design is full automation, sampling frequency is part of the core logic and is dynamically adjusted based on context.
That said, we recently deployed updates to improve how frequency adapts, including better handling of maneuvers beyond just speed changes. Let us know how it helps you. We’ll also log a ticket to explore additional enhancements, such as incorporating vectored charts to help Saillogger recognize when maneuvering occurs near islands, ports, channels, and other complex areas.
-
my last few track logs look great. thanks for the last update and adding it to a list of future enhancements to explore.
-
Hi @admin , just saw this thread and I have a suggestion. I recently wrote an algorithm to simplify GPS tracks which worked really nicely. I'm not sure if it's original but worked for me. Basically use Shoelace formula (https://en.wikipedia.org/wiki/Shoelace_formula) on a sequence of waypoints. If the area of the polygon formed by those waypoints is less than a threshold, add another waypoint to the sequence; if it's more than a threshold, turn it into a track segment and start over again with the next 3 waypoints. That way the area threshold is a single number that users can tweak for their desired level of detail, you don't have to explain a bunch of parameters. Points all in a line have low area, but the momemnt there's a turn the area increases a lot. Happy to share my Python code.
