search

SignalK / specification

Signal K is a JSON-based format for storing and sharing marine data from different sources (e.g. nmea 0183, 2000, seatalk, etc)
Other
91 stars 68 forks source link

Vessel Identity #91

Closed timmathews closed 8 years ago

timmathews commented 8 years ago

Intro

The vessels object at the root of the Signal K object is a key-value store holding information for 1 or more boats. We need to determine exactly what this key should be and what requirements it must fulfill.

This issue is intended to discuss that. Please keep in mind that this is not the same as the identifier for other Signal K hosts on a network (e.g. on a boat with multiple Signal K sources). This is for identifying a single vessel which may be a collection of one or more Signal K devices.

Background

We were originally going to use MMSIs as the unique identifier, but that won't work for a variety of reasons, not the least of which is not everyone has one. MAC address of the SK server device was floated as an option, but that changes whenever the hardware does, so it may not be a good option either. In fact, a boat may have more than one SK gateway and we need to keep the ID the same across devices.

Requirements

These are what I believe the requirements to be. I would like to use this discussion to firstly agree on a set of requirements, vetted against as many use cases as possible, and then float options which satisfy these requirements so that we can agree on something.

Use Cases

MatsA commented 8 years ago

OK, sorry for that…. beginner…. This issue was labeled ”help wanted” ? Country code maybe should be included in Vessel Identity ? But I will drop it, no further comments in this subject from me.

rob42 commented 8 years ago

MatsA, Pls dont drop it, add what you want in the issue I created here https://github.com/SignalK/specification/issues/125 We do appreciate your help - Kees (canboat) didnt mean it as a rebuff :-)

tkurki commented 8 years ago

Fixed in #110