Standardize Nmea0183 on one library? Marnav?

[rgleason]

What pain would there be to standardize on one Nmea0183 Library?

• For plugins
• For OpenCPN

Would something like Marnav https://github.com/mariokonrad/marnav/tree/master help?

• Covers Seatalk
• AIS
• Nmea0183

[bdbcat]

1. Plugins should be using the opencpn-libs submodule, which contains NMEA0183 library, and other regularized support items like OpenGL. Not hard to do, just needs doing.
2. Using a common library between core and plugins is a good idea. Makes things easier for devs in the long term. We should all do this as plugins undergo normal maintenance.
3. However, I would sure be interested to know what specific user problems will be resolved by this. I do not think that there are any, but could be wrong. Just trying to avoid chasing red herrings with limited resources.
4. I cannot see any advantage to switching to Marnav. No reason to think that Marnav is more experienced than OCPN in handling NMEA0183 messages. We have a 13 year history of handling NMEA0183 from a huge population of sometimes non-compliant devices.