Hi @digger, welcome. You are spot on—if you want to share your position or logs with a select group of people, like your family, you can enable the public profile and set a password. That’s exactly what the password for the public profile is for.
@admin Hi Admin, today I was able to go out by boat and I was able to verify that in the trip the number of engine hours was not recorded and I don't understand why, the RPMs are recorded as long as the engine is running of course and instead the pre-engines are not
@admin Hello admin, I entered in the data to be recorded what you suggested and in fact when I started the engine this parameter showed the total running hours of the engine. Unfortunately, however, this data has not been recorded in the path data as per the attached screenshot, although the data is present on the SK server and is available among those shown on Saillogger
Hi @Andrea unfortunately no, all custom monitoring values are displayed in the same format like the second one. The latter one is specialized for reporting the house/main battery.
Hi @jimholthaus, moorage name lookup in Saillogger is a multi-layer process. It uses four to five different types of logic to identify a moorage name, which can come from GIS sources, community-added moorages, or external references like Wikipedia.
Moorages are created automatically, but once they exist, renaming them is straightforward as Kevin mentioned. Please let us know if you’d like any help with that.
Hi @Sparohok , @jimholthaus 's suggestion is a good one. Please try it.
Beyond that, the behavior is definitely not normal. We will need to simulate your account here and run some tests. I will see what we can do about it but please try the above suggestion first.
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.
Hello John, That’s a good catch, I’m not the developer but I’m assuming that that was the most intuitive direction when he developed it. I’m guessing he’ll comment on this if need be. Thanks, Kevin.
Thank you very much. Sadly we moved since Saillogger went down and I updated it. The .GPX track was to fill in our transit from when it went down and our new location where I brought it back up. Not the end of the world. Glad to have our beloved Saillogger back up and running!
Hi Brian, replied over e-mail but I suspect Venus 3.63 upgrade will not help as Signal K configuration is persisted across upgrades. There is no harm to try though.
Glad to hear you sorted it out! For future reference, it may take up to an hour for new data keys to show up in Saillogger. This is only applicable for the initial configuration, once done data flows in regular one minute intervals.
Hmm, spotty access point should not cause this. It is almost always due to GPS. Please keep monitoring and let us know if you observe anything else that is unusual.
