sumps

@timmathews further to our discussions last night, I think we should have a dynamic deviation value in Signal K that we take from the NMEA 0183 HDG sentence and NMEA2000...

A server could also add value by working out magnetic variation using this code from NOAA... https://www.ngdc.noaa.gov/geomag/WMM/soft.shtml

Agree and I am dubious as to how many heading sensors actually output this data. They will send deviation corrected values out.

During some work on iKommunicate, it became clear that we never did support magnetic deviation in the SIgnal K V1 spec. Think at the very least we should have the...

I agree @rob42 and if we were only dealing with new SIgnal K sensors then this would be fine, but we have to work with legacy, current and future 3rd...

I don't think it is correct for developers and users to make assumptions about the data and whether it has been adjusted for variation and/or deviation. Basically NMEA devices that...

I don't understand this concept of "current" by its very nature the deviation value will be the one applicable to the heading the compass is outputting. You need another "static"...

This theoretically perfect world where we have Signal K sensors that output perfect data is great but we still need to work with imperfect NMEA based sensors and displays and...

I also sense from this thread that no one knows whether any systems populate the deviation fields in NMEA 0183 and NMEA 2000 so having a key that iKommunicate, CANBoat,...

The more we describe these marine values and terminologies, the more value we add to the schema and work that everyone is doing. HeadingTrue used to be only generated by...