Hi @Sparohok, thank you.

This is definitely unusual, Saillogger normally eliminates all those starting points automatically and works without any issues. You’re clearly observing something different.
Having a position all the time is actually a good thing, so that won’t cause the issue, but I suspect it has something to do with that USB GPS.

I presume you have a GPS source on your NMEA network (chartplotter, AIS, etc.) that comes online before you start moving. If so, can you configure a priority so that your USB GPS is always the lowest priority and only used when nothing else is available?

Go to Signal K → Server → Data Connections and, using the Priorities table at the bottom, configure priority for your navigation.position and give higher priority to NMEA sources (make sure your instruments are on while you do this). Put the USB GPS at the bottom, and set a timeout of 5 or 10 seconds.

It will look something like this:

Screenshot 2025-08-13 at 9.00.35 PM.png

Make sure you restart Signal K afterwards and let us know what happens on your next trip.

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.

I second @MacJL
There is already a nice autostate plugin.
No need to reinvent the wheel.

The current coverage is stunning! I can appreciate the amount of data involved which I assume could be downloaded in real time in small chunks specific to the localized area of interest? Perhaps have to zoom to a minimum level before data becomes visible. Perhaps a unified Fleet view where vessels which are broadcasting weather can be identified by a small flag (or color). With regard to AIS: more helpful to me than seeing clusters of targets would be searching for a specific boat name/mmsi by submitting that criteria to the server.

Hi @SV_Atlas , it is possible to add any NMEA 2000 data monitoring and with plugin version 4 they are also associated with your trip logs. Please see the announcement here: Plugin 4.0: A Game-Changer for Saillogger!

We have also published a video tutorial explaining how to use this functionality: Saillogger NMEA 2000 Monitoring

Let us know if you encounter any problems using it.

Yes, this was a bug that we also noticed an fixed it (hence you saw it gone). You have probably noticed it before we addressed it.

All should be good now but let us know if not.

@SV_Atlas said in Log Notes editing?:

We are enjoying the new notes editor, thanks again for the really great update.

One request please: Can you please move and/or change the color of the "Cancel" button? It's proximity and similar colors to "Save" have led to more than a few deleted notes which has been frustrating. Ideally if one were to press cancel or delete there would be a second "Are you sure" confirmation.

We re-aligned save to the left and cancel/delete actions to the right, this should create enough spacing and hopefully avoid accidental cancellations.

BTW, for delete, there is already a confirmation but we think it will be an overkill for cancel.

Hello,

For the GPX track, it's an export from TZ Iboat app. I'll send it by mail tonight. I also have other GPX files from my Yach Device router. I'll send it too when I get it.

But I'm sure I will have some trips where I'll have no log at all, whatever the reason (bug, electronic issue, small trip whithout powering on instrument, etc...). And I would love to track it, as I would do it in a real Logbook.

Of course, all informations would have to be entered manually, and automations will not work. Don't you think it's a real use case ?

Wow, this is great, THANK YOU!!!! Well done and so quickly implemented! Thanks again.

Hi Brian,

At the moment, we don’t offer an annual subscription due to accounting complexities.

However, please check out our partner program. By making referrals to Saillogger, you can cover the cost of your subscription or even add to your cruising budget!

Thank you for your consideration.

I, too, agree that the UI needs to be clean.

Perhaps just add them to the History section of the Monitoring tab? Ideally, it would be on the main page so those tracking us could see them, but if they're nerdy enough they can click through to see the more granular data.

Hi, yes, this is configurable from the Signal K plugin. Go to plugin configuration, and change the value under Monitoring data source for depth.

Sounds like you want to use environment.depth.belowSurface, make sure it is available in the Data Browser.

Save the configuration and restart Signal K for the changes to take effect and all should be good!

Hi there thank you for the questions, this functionality already exists. You can click on the datapoint and it will open a popup that includes a button to delete that tracepoint. Here is a demo:

Saillogger delete datapoint/trackpoint demo

We will also add this to Support documents.

@andreshs1, additionally we also revamped the log details page with the new design and the entire site's color palette has been updated as well. Gradually all pages will be transitioned to the newer look and feel (that of monitoring page and now the log details page).

Hi there, thank you for the recommendation. There are upcoming changes to timelapse and the first step will be to integrate timelapse customizer and export function to the page so that you can do that all from a side bar in the main navigation menu. Agree that slider will also be very useful, we will look into it!

Thank you @mmor for the feature requests, these are very valuable! We will definitely keep these in mind while prioritizing our development.

And thank you @andreshs1 for chiming in for the feature to monitor additional information. I think this is emerging as a a common request (@Incentive also raised similar a request in a different thread). Getting the UX right for this is non-trivial but we are thinking of ways to enable it. The new monitoring UX will help here. More to come on this!

Thank you for the feedback Peter. We just pushed a change to keep the info box in the direction of the boat is heading, keeping the track visible. Let us know if it improves the experience.