However the SK data model and SK Server support data using arbitrary, custom paths. Naturally these don't have metadata associated with them, as people make them up and things are rarely added to the specification. SK Server supports adding metadata, but it is cumbersome, involving editing JSON files manually.
The server should support adding metadata for arbitrary paths, either when the server already has data for the paths but also when there is no data for them yet.
The metadata editor should allow only SI Units, otherwise the SK philosophy of always having SI units gets diluted.
People have suggested this feature should be available from Data Browser, where the lack of unit metadata is obvious.
Signal K specification includes Metadata and defines the units for some well known paths.
However the SK data model and SK Server support data using arbitrary, custom paths. Naturally these don't have metadata associated with them, as people make them up and things are rarely added to the specification. SK Server supports adding metadata, but it is cumbersome, involving editing JSON files manually.
The server should support adding metadata for arbitrary paths, either when the server already has data for the paths but also when there is no data for them yet.
The metadata editor should allow only SI Units, otherwise the SK philosophy of always having SI units gets diluted.
People have suggested this feature should be available from Data Browser, where the lack of unit metadata is obvious.