Jacob Gilbert
Jacob Gilbert
This extension was written to support suggestive input as to how SigMF Recordings and Metadata should be presented visually to users. A basic example of how this could be used...
This is done in favor of JSON objects, avoiding nested vectors (prohibited by flatbuffers) and also permitting expansion within this object.
One possible implementation, starting point only. Things I like about this: - Badly needed, long overdue. - Can be a single file in a collection OR an aggregated field within...
This is something discussed in #124 that I continue to find need of; there is currently no way to track why a segment exists that information is sufficiently captured via...
### Summary: Non conforming SigMF datasets require use of the `global` scope `core:dataset` field, which explicitly specifies the full data filename associated with the SigMF recording. When managing SigMF datasets,...
Just as 'frequency' can be modified for different segments, it may be helpful for other characteristics such as 'gain' to be defined on a per-segment basis here. Continuation of discussion...
### Summary It is often useful to have a quick preview of the contents of a recording such as a spectrogram of the data or other graphical representation of what...
SigMF has [intentionally] created many 'optional' fields within the core namespace and throughout the extensions. Its highly likely that certain applications may require some of these optional fields, for which...
This adds metadata to the example recordings. I made up the RF frequencies based on reasonable values but the annotations line up nicely... though in the Mavic recording the two...