If you are using OCPN 5.x.x and you want to use OCPN Draw then you need to be running version 1.5(beta) or 1.6(release). Version 1.4 is not compatible with OCPN 5.x.x. due to the change to MUI.
OCPN Draw (ODraw or OD) 1.6 is the release version of the plugin and should be used where possible. There are minor changes between 1.5 and 1.6 that may make the ODnavob.xml incompatible.
Now, what is new? Apart from supporting the new version of OCPN 5.x.x.
- CSV Import
- Added OD current tool to the OCPN canvas 'Right Click' menu
- Auto generation of OD plugin
- Extended the OD API
- Updated user manual
If you want to create OD objects using a spreadsheet or text editor there is a new format that can be used. This is a basic CSV file and allows the creation of Boundaries, Boundary Points and Text Points. The CSV file is imported via the 'Import gpx...'/'Import csv...' button on the bottom left of the Path & Point manger. The file dialog popup will let you pick either gpx or csv for the file type.
OCPN 'Right Click' menu
Right Mouse click the OCPN canvas
window and you will find the OD 'last used tool' as a menu item. This provides another path to enable creating OD objects.
Auto generation of OD plugin
This allows the creation of new versions of the plugin automatically for all supported platforms. When a change is made to OD and a new version is 'tagged' (as git term) installable versions of the plugin will be generated. If you want to use these you will find them in git at https://github.com/jongough/ocpn_draw_pi/releases
. This will have 'pkg', 'deb' and 'exe' files available for download and installation
. For Linux
based systems there is also a ppa that can be used https://launchpad.net/~jonsgough/+archive/ubuntu/ppa
Extended the OD API
The OD API which is used by other plugins, currrently WeatherRouting, Watchdog and Squiddio, has been extended to allow the creation and deletion of OD Boundaries, Boundary Points and Text Points. The API is available in both JSON and Binary. For plugins which have occasional need to create or delete OD objects then JSON messages can be used. For those that need high speed large volume usage, the three above being examples, then the binary interface should be used as it uses much less resources, but is more difficult to use with less error checking.
As part of extending the use of JSON it is now being validated against a JSON Schema using Draft
7 of the schema specification. Due to the use of a schema there is now a definition, at a high level, of the message content within the source code.
For developers there is another plugin, https://github.com/jongough/testplugin_pi
, which installs the same as OD and allows you to see what happens when you use both the JSON and Binary API's. It can then be used as a starting point or a source for your interactions with the OD API.
If you wish to use the OD API I would suggest at least letting me know you are using it as I may be able to assist with any issues you may get.
Updated user manual
With this new release the user manual has been updated to reflect these changes. There are now two versions of the manual available (there may be users still using OD 1.4), you will find them here: https://opencpn.org/wiki/dokuwiki/doku.php?id=opencpnpencpn_user_manuallugins:sa fety