SensorKey's type is listed as Integer. I don't think that is being enforced. The "key" is being used as kind of a password for sensor authentication, so would a string would be preferable? Currently, placing a non-integer character sequence as the SensorKey in the admin interface and then passing a string SensorKey to the streaming database works.
Section 3.2, item 10 gives examples of acceptable time zone identifiers for Loc messages (“America/New_York”, “America/Chicago”, “America/Denver”, “America/Phoenix”, or “America/Los_Angeles”), but the example Loc message at the top of the spec uses "TimeZone": "America_Denver". Was "America_Denver" an acceptable message tzone format or should the example be changed?
https://github.com/usnistgov/SpectrumBrowser/blob/master/documents/transfer-spec/MSODTransferSpec.md
Integer
. I don't think that is being enforced. The "key" is being used as kind of a password for sensor authentication, so would a string would be preferable? Currently, placing a non-integer character sequence as the SensorKey in the admin interface and then passing a string SensorKey to the streaming database works.(“America/New_York”, “America/Chicago”, “America/Denver”, “America/Phoenix”, or “America/Los_Angeles”)
, but the example Loc message at the top of the spec uses"TimeZone": "America_Denver"
. Was "America_Denver" an acceptable message tzone format or should the example be changed?