Cruisers Forum
 


Reply
 
Thread Tools Search this Thread Rate Thread Display Modes
Old 05-10-2021, 01:39   #31
Registered User
 
Antipole's Avatar

Join Date: Oct 2019
Location: Emsworth, UK
Boat: Alubat Ovni 395
Posts: 269
The issue of route and waypoint name duplication

An issue that needs to be thought about is duplication of waypoint and route names. OpenCPN is unusual - maybe unique - in identifying these not by name but by the unique GUID. This allows multiple waypoints or routes with the same name.

But the other devices I know of expect unique names and if a waypoint or route is loaded duplicating an existing item, it is simply replaced. See the warning in my script description here.

So for true interoperability, we need a discussion on whether OpenCPN should enforce unique names.

I have a JavaScript that 'uniquifies' routepoints. So in one route the routepoints are changed to 001.1, 002.1 et seq. and in another they become 001.2, 002.2 et seq. Adding routepoints and re-running the script adds subscripts to the new routepoints using the subscript already in use for that route. But there are complications when a true waypoint is included in a route. It may or may not be a clone of the free-standing waypoint.
Antipole is offline   Reply With Quote
Old 05-10-2021, 08:15   #32
Registered User
 
JohnGC's Avatar

Join Date: Mar 2018
Location: SW UK
Boat: Moody 44
Posts: 86
Re: The issue of route and waypoint name duplication

An advantage of unique IDs, is that renaming is never an issue.

Forcing unique names can make renaming awkward.

I'm not saying it's an issue, just pointing it out.

Currently when adding a new waypoint which is close to an existing one, we are asked if we'd like to use the existing waypoint. Maybe that feature could be extended to imported waypoints. That way you would only get duplicates after import if you say "no" and the problem would be eliminated at source.

John

Quote:
Originally Posted by Antipole View Post
An issue that needs to be thought about is duplication of waypoint and route names. OpenCPN is unusual - maybe unique - in identifying these not by name but by the unique GUID. This allows multiple waypoints or routes with the same name.

But the other devices I know of expect unique names and if a waypoint or route is loaded duplicating an existing item, it is simply replaced. See the warning in my script description here.

So for true interoperability, we need a discussion on whether OpenCPN should enforce unique names.

I have a JavaScript that 'uniquifies' routepoints. So in one route the routepoints are changed to 001.1, 002.1 et seq. and in another they become 001.2, 002.2 et seq. Adding routepoints and re-running the script adds subscripts to the new routepoints using the subscript already in use for that route. But there are complications when a true waypoint is included in a route. It may or may not be a clone of the free-standing waypoint.
JohnGC is offline   Reply With Quote
Old 06-10-2021, 01:49   #33
Registered User
 
Antipole's Avatar

Join Date: Oct 2019
Location: Emsworth, UK
Boat: Alubat Ovni 395
Posts: 269
Transferring waypoints and routes

The most common requirement is to transfer waypoints and routes to or from another device. Making this possible should therefore be the first step in enhancing interoperability.

Transfers should be possible using a script in the JavaScript plugin. This has the advantage that it can easily be tailored to the individual user's requirements. However, there are deficiencies in the Waypoint API that severely restrict what can be done.

I have raised a request on FlySpray to address these. The changes required are minimal in my opinion. It would be great if they could be tacked on to OpenCPN v5.5.
Antipole is offline   Reply With Quote
Old 06-10-2021, 08:49   #34
Registered User
 
sv_pelagia's Avatar

Join Date: Apr 2013
Location: British Columbia
Boat: Sceptre 41
Posts: 1,928
Re: Interoperability between OpenCPN(s) & Devices

Related to the transfer of waypoints and routes to other devices:

As noted earlier, I transfer (via rou/rat files) waypoints and routes from OpenCPN to my Furuno chartplotter. As with many chartplotters, the Furuno has several limitations: (i) limited number of wpt symbols (many which, by the way, do NOT have obvious equivalents in OpenCPN), (ii) colour scheme that only partially matches OpenCPN (e.g., OPCPN black is yellow on Furuno), (iii) a limit of 6 characters for wpt name, and (iv) limit of 13 characters for comments. (There are also other differences, but the above are what I have to deal with.)

It would be great if OpenCPN had a plugin that would make the above changes and save to rou/rat file. (Currently, I use GPSUTILITY to make wholesale changes and save as rou/rat. )

ALSO: Unless I've missed something, I cannot change symbols, colours, etc of wpts for many wpts at once within OpenCPN. This would seem a useful capability, a separate issue from transferring routes and wpts.
sv_pelagia is offline   Reply With Quote
Old 06-10-2021, 10:39   #35
Registered User
 
rgleason's Avatar

Join Date: Mar 2012
Location: Boston, MA
Boat: 1981 Bristol 32 Sloop
Posts: 17,532
Images: 2
Re: Interoperability between OpenCPN(s) & Devices

GPS Utility is mentioned in the Furuno "Converting Waypoints to TZtouch3" youtube.
They are using GPX. Also I believe that bdbcat has made adjustments for the length of the names etc, and provided a Furuno checkbox for transfers. Not knowing anything about Furuno rou or rat files I found this thread on Furuno Waypoint Backup

Your information is good, but we would need a more detailed specification which uses the existing Furuno settings, if the transfer back and forth can be made better. It would probably be part of a plugin I think.


Also https://www.furunousa.com/-/media/si...ing_guide1.pdf
rgleason is offline   Reply With Quote
Old 06-10-2021, 11:04   #36
Registered User
 
sv_pelagia's Avatar

Join Date: Apr 2013
Location: British Columbia
Boat: Sceptre 41
Posts: 1,928
Re: Interoperability between OpenCPN(s) & Devices

Quote:
Originally Posted by rgleason View Post
GPS Utility is mentioned in the Furuno "Converting Waypoints to TZtouch3" youtube.
They are using GPX. Also I believe that bdbcat has made adjustments for the length of the names etc, and provided a Furuno checkbox for transfers. Not knowing anything about Furuno rou or rat files I found this thread on Furuno Waypoint Backup

Your information is good, but we would need a more detailed specification which uses the existing Furuno settings, if the transfer back and forth can be made better. It would probably be part of a plugin I think.


Also https://www.furunousa.com/-/media/si...ing_guide1.pdf
As I have to make changes to most/all my wpts, I do not transfer via data connection, rather I use -->gpx -->gpsutility (to change groups of wpts, and to convert to rat/rou) --> rat/rou files

For my older plotter, wpts etc described in Section 6-1 to 6-4 of the manual (in link to large pdf below). Specification of wpt is in 6-4 (pgs 164-165).

https://www.furunousa.com/-/media/si...ors_manual.pdf
sv_pelagia is offline   Reply With Quote
Old 06-10-2021, 11:06   #37
Registered User
 
rgleason's Avatar

Join Date: Mar 2012
Location: Boston, MA
Boat: 1981 Bristol 32 Sloop
Posts: 17,532
Images: 2
Re: Interoperability between OpenCPN(s) & Devices

What does this mean " I use -->gpx -->gpsutility (to change groups of wpts, and to convert to rat/rou) --> rat/rou files"?


The specification should be a separate document that you attach.
rgleason is offline   Reply With Quote
Old 06-10-2021, 11:13   #38
Registered User
 
rgleason's Avatar

Join Date: Mar 2012
Location: Boston, MA
Boat: 1981 Bristol 32 Sloop
Posts: 17,532
Images: 2
Re: Transferring waypoints and routes

Quote:
Originally Posted by Antipole View Post
The most common requirement is to transfer waypoints and routes to or from another device. Making this possible should therefore be the first step in enhancing interoperability.

Transfers should be possible using a script in the JavaScript plugin. This has the advantage that it can easily be tailored to the individual user's requirements. However, there are deficiencies in the Waypoint API that severely restrict what can be done.

I have raised a request on FlySpray to address these. The changes required are minimal in my opinion. It would be great if they could be tacked on to OpenCPN v5.5.

Users should vote for this I think! Go to tracker / flyspray and vote to get it into the vetted feature requests.


This makes a good deal of sense to me, and I am sure others, but it is unlikely to make it into 5.5.9 fast becoming 5.6. I am going to add this to Issues in OpenCPN in hopes the request will continue to be refined and improved so that it is as good as it can be for interoperability.


https://github.com/OpenCPN/OpenCPN/issues/2421


There could be basic scripts for certain targets that are modified by the user.
rgleason is offline   Reply With Quote
Old 06-10-2021, 11:15   #39
Registered User
 
Antipole's Avatar

Join Date: Oct 2019
Location: Emsworth, UK
Boat: Alubat Ovni 395
Posts: 269
Re: Interoperability between OpenCPN(s) & Devices

Quote:
Originally Posted by sv_pelagia View Post
Related to the transfer of waypoints and routes to other devices:

As noted earlier, I transfer (via rou/rat files) waypoints and routes from OpenCPN to my Furuno chartplotter. As with many chartplotters, the Furuno has several limitations: (i) limited number of wpt symbols (many which, by the way, do NOT have obvious equivalents in OpenCPN), (ii) colour scheme that only partially matches OpenCPN (e.g., OPCPN black is yellow on Furuno), (iii) a limit of 6 characters for wpt name, and (iv) limit of 13 characters for comments. (There are also other differences, but the above are what I have to deal with.)

It would be great if OpenCPN had a plugin that would make the above changes and save to rou/rat file. (Currently, I use GPSUTILITY to make wholesale changes and save as rou/rat. )

ALSO: Unless I've missed something, I cannot change symbols, colours, etc of wpts for many wpts at once within OpenCPN. This would seem a useful capability, a separate issue from transferring routes and wpts.
Not sure about the colour scheme. But, assuming rou/rat files are text files, I think you could do all you want using the JavaScript plugin. You could process your waypoints, select the ones you want by some criterion, truncate names and comments, change the symbol etc. and write out to a file. A refinement would be to warn if truncating names caused waypoint names to clash or you could decide how to make them unique.

Because you would be scripting this, you could tailor it to your needs without having the process baked into a traditional plugin.
Antipole is offline   Reply With Quote
Old 06-10-2021, 11:24   #40
Registered User
 
sv_pelagia's Avatar

Join Date: Apr 2013
Location: British Columbia
Boat: Sceptre 41
Posts: 1,928
Re: Interoperability between OpenCPN(s) & Devices

Quote:
Originally Posted by rgleason View Post
What does this mean " I use -->gpx -->gpsutility (to change groups of wpts, and to convert to rat/rou) --> rat/rou files"?


The specification should be a separate document that you attach.
What does this mean? It is my process of getting wpts from OpenCPN to gpsutility then to rou/rat files which Furuno reads in. (GPSUtility required to convert to rou/rat, and to modify groups of wpts.)

Relevant pages of manual attached. Especially note wpt symbols, colours and naming/comment limitations.

The "format uploads to Furuno" option on connections is for data transfer by serial connection etc, not via file (gpx, rat/rou). Also, it may shorten wpt name but there is no way to alter symbols systematically etc. FurunoNavnetV2-DataTransfer.pdf
sv_pelagia is offline   Reply With Quote
Old 06-10-2021, 11:28   #41
Registered User
 
sv_pelagia's Avatar

Join Date: Apr 2013
Location: British Columbia
Boat: Sceptre 41
Posts: 1,928
Re: Interoperability between OpenCPN(s) & Devices

Quote:
Originally Posted by Antipole View Post
Not sure about the colour scheme. But, assuming rou/rat files are text files, I think you could do all you want using the JavaScript plugin. You could process your waypoints, select the ones you want by some criterion, truncate names and comments, change the symbol etc. and write out to a file. A refinement would be to warn if truncating names caused waypoint names to clash or you could decide how to make them unique.



Because you would be scripting this, you could tailor it to your needs without having the process baked into a traditional plugin.
Yes, after reading your posts, I wondered if this would work for me.

BUT, this requires some coding abilities, and is far too much to expect for most users (no disrespect intended! but how many OpenCPN users code?). Some users already consider OpenCPN not user friendly (I'm not one of them...).
sv_pelagia is offline   Reply With Quote
Old 06-10-2021, 16:59   #42
Registered User
 
rgleason's Avatar

Join Date: Mar 2012
Location: Boston, MA
Boat: 1981 Bristol 32 Sloop
Posts: 17,532
Images: 2
Re: Interoperability between OpenCPN(s) & Devices

You could start by providing a spec detailing how you want to change

O ----> Furuno
Furuno ----> O

Then the next step is to make the two scripts.
rgleason is offline   Reply With Quote
Old 06-10-2021, 17:59   #43
Registered User

Join Date: Aug 2020
Location: PNW
Boat: Catalina 400 MKii
Posts: 4
Re: Interoperability between OpenCPN(s) & Devices

Use case:
Have existing system (Garmin GPSmap XSV) with chartplotter, autopilot (Raytheon ST6000+), depth, wind speed & direction (Garmin) all on NMEA 2000.

As I have researched and read, I come across OpenCPN and think awesome, useful application of open source (I work for the distribution SUSE) and I want to experience the collaboration and features so I build a RaspberryPi + NMEA interface with touch screen for a remote navigation station.

Purpose: connect ship systems to see, track monitor systems, position, conditions etc. Someday remote access to monitor but today, effectively a repeater using OpenCPN (versus buying another node from Garmin) and dogfood the technology.

Issues: I have 5v power and NMEA connection thanks to a PicanM, internet thanks to a Yifan325+antenna, but can’t easily connect to the existing NMEA network (0183 or 2000).

Simple add in for each major device manufacturer?
SjoJungfrun is offline   Reply With Quote
Old 07-10-2021, 00:42   #44
Registered User

Join Date: Mar 2011
Posts: 640
Re: Interoperability between OpenCPN(s) & Devices

This scenario is already supported.

With the RaspberryPI and PicanM hat you have all the bits you need.
stevead is offline   Reply With Quote
Old 07-10-2021, 09:21   #45
Registered User

Join Date: Aug 2020
Location: PNW
Boat: Catalina 400 MKii
Posts: 4
Re: Interoperability between OpenCPN(s) & Devices

@stevead
Yes agreed. Just pointing out from the usability ask to the OP, easy integration to an existing system ex commonly available systems like Furuno, Raymarine, Garmin. Having the right hardware is great too yes.

Quote:
Originally Posted by stevead View Post
This scenario is already supported.

With the RaspberryPI and PicanM hat you have all the bits you need.
SjoJungfrun is offline   Reply With Quote
Reply

Tags
enc, opencpn, rope

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are Off
Pingbacks are Off
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Yacht Devices NMEA wifi to OpenCPN TheOffice OpenCPN 16 26-07-2018 15:12
What chartplotter brand / interoperability between brands CatNewBee Marine Electronics 10 17-08-2017 02:43
OpenCPN+Android : external USB-Serial devices ? PaulRowntree OpenCPN 7 02-04-2016 05:12
Synchronize Routes between OpenCPN Desktop and OpenCPN Android Tablets bgs OpenCPN 2 13-03-2016 19:47
Interoperability Sandero Marine Electronics 1 27-07-2014 17:41

Advertise Here


All times are GMT -7. The time now is 03:02.


Google+
Powered by vBulletin® Version 3.8.8 Beta 1
Copyright ©2000 - 2024, vBulletin Solutions, Inc.
Social Knowledge Networks
Powered by vBulletin® Version 3.8.8 Beta 1
Copyright ©2000 - 2024, vBulletin Solutions, Inc.

ShowCase vBulletin Plugins by Drive Thru Online, Inc.