Quite often I've been using OCPN nav objects just to annotate charts
I used tracks to draw Traffic Separation Schemes, Prohibited Areas and Firing Ranges (all equally important as shoreline) as well as outlines and status of paper charts
making up Forums
- Post 458229">various-IRJDSUNE9932123321222xxeww-folios .
I used routes to draw lat/lon grids.
I used waypoints to update charts with new nav marks and dangers as per Notices to Mariners, and to add Radio
Call-In Points or to build a database of lights and locations, that I want to see on chart regardless of current
Technically, all of these are standard nav objects to OCPN. About the only difference I want is their persistence and protection from change.
So, after some tweaking, the Route
Manager gets a new tab - Layers. Anything imported into a Layer
- is not deletable
- is not modifiable
Objects created in Layers are not subject to Delete (incl. Delete All), Export nor are they saved into navobj.xml upon program termination.
Extended control allows (still to-do) selective show/hide on chart and in general nav objects listing, and deletion on a per-layer basis.
A Layer is a single
GPX file, that can be prepared offline by any means.
In addition to a standard set of layers imported during startup from the /Layers subdirectory layers can be imported just for the current
session by specifying a file in RM Dialog.
I still have to implement some of the buttons, but it starts to look quite promising.