Variable LogEntrySchemaConst
LogEntrySchema: TObject<
{
author: TOptional<TString>;
category: TOptional<TString>;
datetime: TOptional<TString>;
id: TOptional<TString>;
origin: TOptional<TString>;
position: TOptional<
TObject<
{
altitude: TOptional<TNumber>;
latitude: TNumber;
longitude: TNumber;
},
>,
>;
schemaVersion: TOptional<TInteger>;
telemetry: TOptional<
TArray<
TObject<
{
$source: TOptional<TString>;
path: TString;
timestamp: TOptional<TString>;
value: TUnknown;
},
>,
>,
>;
text: TString;
},
> = ...
Log entry resource — a line in the vessel's logbook, time-anchored by
datetimeand optionally place-anchored byposition, carrying an optional snapshot of Signal K paths observed at that moment.Open content model: consumers must ignore unknown fields and providers must preserve them on write; top-level extension fields should be prefixed with the writing application's namespace (e.g.
x-stylusapp-ink), and telemetry extension paths should use a namespaced root segment.originandcategoryare open enumerations: the listed values are the recommended vocabulary, unknown values must not be rejected.