Saillogger Community

@admin thanks for the feedback, great info. However I am still seeing the same behavior, tracks have 30 idle minutes before we set out on our trip. I set the priorities with n2k_on_ve.can_socket.* above the USB GPS which is venus.com.victronenergy.gps.ve_ttyACM0 and restarted the Signal K server. Any other suggestions?

Saillogger is awesome, started using it this summer and I'm loving it. Having said that, on to the quibbles!

I'm not sure if this is normal or something unique about my setup. All my logs seem to start about 30 minutes before we actually weigh anchor, with a bunch of floating around the anchor at 0.2 knots or whatever As a result the duration is longer and average speed lower than expected.

The only thing I can think of that's unusual about my setup is that I have a USB GPS connected to Cerbo GX so my Signal K will have a boat position all the time, even when the boat instruments are turned off. Could that be causing this issue?

Anyway, thanks for the app, its great!

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.