Signal K

SK

Signal K

Join the community to ask questions about Signal K and get answers from other members.

Join

questions

announcements

server

specification

plugins-and-webapps

sensors

nmea2000

node-red

wilhelmsk

sensesp

I'm seeing some inconsistencies in the

I'm seeing some inconsistencies in the schemas related to complex values (e.g. navigation.position, design.keel) and am curious if it's intentional or a mistake. According to the description of the full data model (https://github.com/SignalK/specification/blob/master/mdbook/src/data_model.md#full-format), the {latitude: …, longitude: :} value for navigation.position is still nested in a value field, and the schema (https://github.com/SignalK/specification/blob/master/schemas/definitions.json#L813) accurately describes it that way. However, some paths, like design.keel, don't have their properties nested inside of value...

I don't understand what you are meaning

I don't understand what you are meaning? AIS Msg 1 is for class A vessel position report. Check Msg IDs and contents e.g. from here https://www.navcen.uscg.gov/ais-messages If needed to continue about AIS topics, then let's continue that in separate thread....

@AdrianP that's awesome, I will update

@AdrianP that's awesome, I will update the AC plugin accordingly.

This is already technically there....the

This is already technically there....the resource provider just needs to send a delta message with the path resources.<res_type>. The client should see this and update the display accordingly....