Feature Requests

[barcoMeCasa]

Think it would be useful to have a "save database as.." & "load database" option?
So when you end of season or whatever you can save the lot as 2025Cruising?
Maybe better as a plugin 🤔

The routes manager can get very bloated, might be nice to have an easy way to manage better? I had a play around with ai code but too much on the go so gave up early.

Any thoughts?

[Hakan]

end of season or whatever you can save the lot as 2025Cruising

At the end of season I use to in Route & mark manager export all tracks to e.g 2025_tracks.gpx and also save a backup of navobj.db. Then I delete all tracks from the live db in the manager, to have a clean board next year.

[barcoMeCasa]

Originally Posted by Hakan

At the end of season I use to in Route & mark manager export all tracks to e.g 2025_tracks.gpx and also save a backup of navobj.db. Then I delete all tracks from the live db in the manager, to have a clean board next year.

Similar I export every passage as a gpx, but it's a run around, might be very nice to have a quicker and easier way to control what's in there? Maybe a backup database with filters like view tracks by date, routes by name etc etc
The python playaround image above sort of works enough to be a bit useful, sends to/ from raspberry pi / laptop (send to peer broken in latest openplotter)

Maybe time to give writing a plugin a go

[Oli89]

Originally Posted by Oli89

Hey,

I currently have a suggestion for improving the AIS alarm feature. I use it quite often and really like it — it’s a great tool. However, especially while sailing, due to yawing, I frequently encounter the issue that another vessel repeatedly enters and exits my alarm zone.

The problem is that each time this happens, the vessel triggers a new alarm, even if I have already acknowledged or muted the alarm for that specific vessel. If it’s just one ship, it’s a bit annoying and usually leads me to mute my computer’s sound — which is risky, as I might later forget to turn it back on and later miss an important alert for a new vessel. But when sailing in busy areas (like TSS zones), where AIS navigation becomes even more important, these repeated alerts from already-known vessels make it extremely difficult to focus on new, relevant alarms.

My suggestion would be to add two additional options to the current alarm message window (next to "Acknowledge" and "Silent alarm") — for example:

Acknowledge for the next 60 minutes

Silent alarm for the next 60 minutes

This way, once one of these options is selected, the vessel could not trigger a new alarm for the next 60 minutes, no matter how often it moves in and out of the alarm zone.

I’d really appreciate your feedback on this idea.
Please also feel free to reach out if you have any questions — or if you ever release a first version and need someone to test it, I’d be happy to help.

Looking forward to hearing from you!

Best regards,
Oli

Hey everyone, I’ve opened a GitHub feature request — if you’d like to support the importance of this topic or share any ideas, please do so here: https://github.com/OpenCPN/OpenCPN/i...ent-3478420152

[stevead]

Think it would be useful to have a "save database as.." & "load database" option?

FYI, The next version of OpenCPN has a "backup" database feature, which allows you to perform a full backup of navobj.db while OpenCPN is running. No need to shutdown OpenCPN and manually copy the database file.

I'm personally loath to publish yet another plugin to import routes, waypoints and tracks from a "backup" database when I believe that feature, like backup, should be a core function of OpenCPN.

[barcoMeCasa]

Originally Posted by stevead

FYI, The next version of OpenCPN has a "backup" database feature, which allows you to perform a full backup of navobj.db while OpenCPN is running. No need to shutdown OpenCPN and manually copy the database file.

I'm personally loath to publish yet another plugin to import routes, waypoints and tracks from a "backup" database when I believe that feature, like backup, should be a core function of OpenCPN.

Always worth asking! Didn't even notice that. Tnx.

[sailingharry]

Originally Posted by Oli89

Hey,

I currently have a suggestion for improving the AIS alarm feature. I use it quite often and really like it — it’s a great tool. However, especially while sailing, due to yawing, I frequently encounter the issue that another vessel repeatedly enters and exits my alarm zone.

The problem is that each time this happens, the vessel triggers a new alarm, even if I have already acknowledged or muted the alarm for that specific vessel. If it’s just one ship, it’s a bit annoying and usually leads me to mute my computer’s sound — which is risky, as I might later forget to turn it back on and later miss an important alert for a new vessel. But when sailing in busy areas (like TSS zones), where AIS navigation becomes even more important, these repeated alerts from already-known vessels make it extremely difficult to focus on new, relevant alarms.

My suggestion would be to add two additional options to the current alarm message window (next to "Acknowledge" and "Silent alarm") — for example:

Acknowledge for the next 60 minutes

Silent alarm for the next 60 minutes

This way, once one of these options is selected, the vessel could not trigger a new alarm for the next 60 minutes, no matter how often it moves in and out of the alarm zone.

I’d really appreciate your feedback on this idea.
Please also feel free to reach out if you have any questions — or if you ever release a first version and need someone to test it, I’d be happy to help.

Looking forward to hearing from you!

Best regards,
Oli

YES! OMG, it's a big part of why, on my MFD (Furuno), I almost never turn on alarms. I so wish I could have alarms -- they are useful. But alarm fatigue is a real thing, and if the alarm goes off too often, you turn it off. Ignoring boats under 1kt (a feature on my MFD) helps a lot, but not enough. One single boat going down the Bay 300 yards to my side at the same speed can alarm every minute or two, annoying beyond words.


On that note, a high degree of granularity in AIS alarms would help a LOT. One AIS alarm criteria for boats over 100 feet long (ie, the "big boys"), another for boats under 100 feet. Or a CPA range for boats over and under 8 kts -- I'm OK with a 100 yard CPA (really, even 50 yards) for a slow boat, but not for a boat making 20 kts.


When I first got AIS, I thought CPA alarms would be a godsend. Now, I rarely turn them on unless offshore. Or, set it for CPA of under 100 yards in under a minute -- basically, an "imminent collision alarm."

[Hakan]

We have two limits for CPA-alert. CPA range like 1 Nm. TCPA >> The time to go to the CPA point, in minutes. The latter will take care of the high/low speed target.

Also you can choose to no show the alarm dialog but only the CPA-red lines, red target and the closest point of approach, if the actual courses and speed are stable.

[sailingharry]

Originally Posted by Hakan

We have two limits for CPA-alert. CPA range like 1 Nm. TCPA >> The time to go to the CPA point, in minutes. The latter will take care of the high/low speed target.

Also you can choose to no show the alarm dialog but only the CPA-red lines, red target and the closest point of approach, if the actual courses and speed are stable.

No, we are talking two different things. The "two limits" is one set of rules, and most systems do that. What I'm suggesting is, in words, this:
SIZE SPLIT (let me know early about big boys, but avoid the nuisance of pleasure boats)
* For vessels over 100', alarm when CPA is less than 1 mile and less than 15 minutes. This covers big boys, and gives me ample time to steer clear. While this is a big "window" there are very few of these and I WANT to know, basically as soon as it shows on AIS.
* For vessels under 100', alarm when CPA is less than 200 yards and TCPA is under 2 minutes. These are all the pleasure boats, with zig-zagging courses and so easy to avoid with even 1 minute before collision. I do NOT want these alarms early.
SPEED SPLIT (give me an early warning on 30 knot cruisers, but not so much on sailboats)
* For vessels over 15 kts, (T)CPA of 10 minutes and 500 yards. These boats are hard to evaluate and take action, because they go so fast.
* For vessels under 15 kts, (T)CPA of 2 minutes 200 yards -- again, I can see, evaluate, and evade in way under a minute.


I realize there may be a "logic" challenge with a split on both size and speed (what if it is slow and long, or fast and short), but that shouldn't be hard.


Yes, as a watchstander, I should see all these early and take action, and there should be no need for alarms. But if I've already seen and evaluated, I don't want an alarm 30 seconds later. I only want an alarm when I HAVE to take action (ie, let me know when I've missed one) or for the big boys, to make sure I know they are there very early.

[Antipole]

@sailingharry... an interesting want.

You could do this sort of thing in JavaScript. Every user will probably have different wants, so using JavaScript lets you tailor it to what you want. It is also good for experimenting and finding which criteria you want to use.

To get you started, here is a simple script, which you can develop as you wish.

bigBoyTypes = [
	70,	// cargo ship
	31,	// towing
	32	// towing exceeds 200m
	];

onAllSeconds(review, 45);		//call review every 45 seconds

function review(){
	targets = OCPNgetAISTargets();		// get all targets
	for (t = 0; t < targets.length; t++){	// for each target
		target = targets[t];
		if (
		  (bigBoyTypes.indexOf(target.shipType) >= 0)	//check if big boy
		  && (target.CPAnm < 0.5)
		  && (target.navStatus == 0)	// underway
		  ) OCPNsoundAlarm();
		}
	};

This compiles OK but I have not tested it with AIS as my system is out of commission at present.

[Hakan]

Originally Posted by sailingharry

... But if I've already seen and evaluated, I don't want an alarm 30 seconds later. .

That's easy to solve. Use the Options-Ships-AIS: "Enable Target Alert Acknowledge timeout (min)" and set the time to something suitable for you.


For else; To use ship's size reported in a AIS target report is not feasible for any alarm or similar critical functions. That value is to unsure. Position, course and speed are reported quite often, often seconds, and are based on input from (GNSS)sensors. Dimensions, name and more are reported more seldom, sometimes even not at all. All depends also on user input and can be valid or not.

[wholybee]

Originally Posted by sailingharry

No, we are talking two different things. The "two limits" is one set of rules, and most systems do that. What I'm suggesting is, in words, this:
SIZE SPLIT (let me know early about big boys, but avoid the nuisance of pleasure boats)
* For vessels over 100', alarm when CPA is less than 1 mile and less than 15 minutes. This covers big boys, and gives me ample time to steer clear. While this is a big "window" there are very few of these and I WANT to know, basically as soon as it shows on AIS.
* For vessels under 100', alarm when CPA is less than 200 yards and TCPA is under 2 minutes. These are all the pleasure boats, with zig-zagging courses and so easy to avoid with even 1 minute before collision. I do NOT want these alarms early.
SPEED SPLIT (give me an early warning on 30 knot cruisers, but not so much on sailboats)
* For vessels over 15 kts, (T)CPA of 10 minutes and 500 yards. These boats are hard to evaluate and take action, because they go so fast.
* For vessels under 15 kts, (T)CPA of 2 minutes 200 yards -- again, I can see, evaluate, and evade in way under a minute.


I realize there may be a "logic" challenge with a split on both size and speed (what if it is slow and long, or fast and short), but that shouldn't be hard.


Yes, as a watchstander, I should see all these early and take action, and there should be no need for alarms. But if I've already seen and evaluated, I don't want an alarm 30 seconds later. I only want an alarm when I HAVE to take action (ie, let me know when I've missed one) or for the big boys, to make sure I know they are there very early.

Another way to handle this that might be a simpler feature request would be to have different CPA alarms for class A and Class B/B+ ships. There might be some overlap, but "Big Boys" will ALWAYS be class A, and small recreational boats very rarely will be.

[sailingharry]

Originally Posted by wholybee

Another way to handle this that might be a simpler feature request would be to have different CPA alarms for class A and Class B/B+ ships. There might be some overlap, but "Big Boys" will ALWAYS be class A, and small recreational boats very rarely will be.

My initial idea for solving this, when I got my first VHF with an included AIS receiver, was to use an ESP32 in the line between the VHF and the MFD. It would accept all AIS signals, and only forward Class A to the MFD. It was beyond my feeble skills -- I bought the processor, downloaded the IDE, and that was the end of my skills.


But, yes, that's a very simple solution that is very close to sufficient.

[sailingharry]

Originally Posted by Hakan

That's easy to solve. Use the Options-Ships-AIS: "Enable Target Alert Acknowledge timeout (min)" and set the time to something suitable for you.


For else; To use ship's size reported in a AIS target report is not feasible for any alarm or similar critical functions. That value is to unsure. Position, course and speed are reported quite often, often seconds, and are based on input from (GNSS)sensors. Dimensions, name and more are reported more seldom, sometimes even not at all. All depends also on user input and can be valid or not.

This is classic "perfect is the enemy of done." The reality is that, with the "system" as it is, I (and many others) have given up on AIS alarms. So instead of an imperfect, but useful, system, we have no system at all. But at least our solution isn't imperfect.
The problem with length not being in every broadcast is real, however, I'm fairly confident that anyone over 200 feet is accurately broadcasting length -- it's the amateurs that aren't filling in all the fields. It could be solved by "defaulting" to small boy rules, which would minimize alarms. If/when a length is broadcast (and all big boys will), then you move to the broader alarm regeime. This could delay the alarm by up to a minute (I believe Class A, which all big boys are, includes this more often).

[sailingharry]

Originally Posted by Antipole

@sailingharry... an interesting want.

You could do this sort of thing in JavaScript. Every user will probably have different wants, so using JavaScript lets you tailor it to what you want. It is also good for experimenting and finding which criteria you want to use.

To get you started, here is a simple script, which you can develop as you wish.

bigBoyTypes = [
    70,    // cargo ship
    31,    // towing
    32    // towing exceeds 200m
    ];

onAllSeconds(review, 45);        //call review every 45 seconds

function review(){
    targets = OCPNgetAISTargets();        // get all targets
    for (t = 0; t < targets.length; t++){    // for each target
        target = targets[t];
        if (
          (bigBoyTypes.indexOf(target.shipType) >= 0)    //check if big boy
          && (target.CPAnm < 0.5)
          && (target.navStatus == 0)    // underway
          ) OCPNsoundAlarm();
        }
     };

This compiles OK but I have not tested it with AIS as my system is out of commission at present.

This is a "problem" with OpenCPN (and also a huge benefit, I get it). Rather than a packaged system which doesn't require much knowledge and gives no flexibiity, OpenCPN is a science project which requires from the very beginning a rather strong set of relevant skills (you have to understand hats, and optoisolaters, and power supplies, and cases, and cooling, and installing linux on an SD card, and all that -- much of which I'm at least somewhat up to speed on, but it's not easy stuff).


You say this is a script that compiles. That almost is Greek. Yes, I sort of get the language and can almost read that snippet (I don't know JavaScript, but I've done a fair amount of programming -- Basic, Clipper, a course in VisualBasic, a very small amount of Fortran, an even smaller amount of C+ for an ESP32 project, I even taught myself 8088 Assembly once upon a time). So, to do what you suggest, I suspect I copy that snippet into a text file (with the correct extension), download and install a Java compiler, and then it will output "something." An *.exe? A *.dll? And then, somehow, insert it into the OpenCPN ecosystem. Does that work on both a Pi and Windows? Does it get compiled differently on each?


I don't really need a response -- I'm more muttering. I'm somewhat techhi, and I can probably figure it out on my own.