specification
specification copied to clipboard
Signal K is a JSON-based format for storing and sharing marine data from different sources (e.g. nmea 0183, 2000, seatalk, etc)
We don't yet support metadata, for example `displayName` per source for a single path. >For example, both my depth sounder and speed log report water temperature. I can figure out...
add the lenght of de anchor line, the temperature of the anchor motor and the current the motor takes
_Ref: Previous issue #215 (2016) started to address this topic but with no outcome._ **Proposal:** Establish path(s) to contain the data for weather forecasts, observations and warnings/alerts. _Example:_ `environment.weather.forecasts` `environment.weather.observations`...
@panaaj and I (well, mostly Adrian) have been [working on two new Signal K APIs](https://github.com/SignalK/signalk-server/pull/1381): - [Resources API](https://github.com/SignalK/signalk-server/blob/resources_course_api/src/api/resources/openApi.json) - [Course API](https://github.com/SignalK/signalk-server/blob/resources_course_api/src/api/course/openApi.json) While Signal K v1 was a lot about defining...
When running signalk nodejs server and an Airmar WX220 weather station, wind data comes in as environment.self.directionGround but with no unit specified. Is there a way of updating the specification...
Navtex
Just a thought, should Navtex messages have a place in the specification?
NavTex, Inmarsat Fleet messages should be made part of the SignalK spec
Motivated by a desire to monitor my bilge pump in SignalK. But a standard should be applicable to other kinds of pumps (think domestic water, hydraulic, macerators) and to intermittent...
``` └─┬ [email protected] └─┬ @signalk/[email protected] └─┬ [email protected] └─┬ [email protected] └── [email protected] ```
# Feature: Course API ## Description: Define an API for Signal K client applications that provides methods to set a destination or navigate a route. These methods manage the setting...