Thanks for your detailed response. I gone over the thread and its an interesting discussion. Learned much as always as there are different points of view each valid from their own camps. I guess the main issue is this, the licensing structure adopted by OpenCPN and how that allows other data sources to interoperate, and then a standardized method. Third option is what OpenGIS uses which is a pluggin system independantly developed by others to a standardize format. The data source licenses then become less of an issue (I say less not irrevocable) as the data is transmitted one way.
I really like this piece of software and have tested it enough 1.3.6, to make it the resident program to get me home, some 1500 miles in the comming weeks. Add to that zyGrib, and xtides and you have a 90 percent solution. The last piece and this is where I use AC data is anchorages
and marina information. The accuracy of that data is important and will be tested on the trip home. It is not in the unix/linux tradition to develop comprehensive programs that do everything, rather do one thing and do it well or stellar. (speaking of stellar, stellarium is in the kit as well) Hence if I were asked, which Ive not, just hoping to make a simple contribution, a pluggin module system would go a long way to address many issues, as well as take the burden of development off the core
group and allow them the time and energy to do what they do best.
Thanks for allowing me to comment. Its appreciated. As I get more into this piece of software I would like to help out on the documentation
front. Once I get home that is as I dont code but do have some experience with OSS projects and will have some time this summer sitting on a hook, contemplating my next step.