Anthony Romaniello

I've just come across this issue, and wanted to point folks towards a solution which may work for some use cases: NTIA's `ntia-algorithm` extension of the SigMF namespace. View the...

@blainNTIA looking back at this, with much more C++ experience compared to when I made the initial changes, I found many more instances where const correctness could be implemented. The...

Also, I still have not made edits to the .NET wrapper, or tested the .NET wrapper for the C++ changes. I don't think any changes are needed in .NET based...

Thanks for your pull request, @JayKickliter! I just submitted a separate pull request, #12, which implements these changes as well as more `const` correctness across the codebase. Please feel free...

Closing this since #12 was just merged, which includes this change. Thanks @JayKickliter for the recommendation. If you need this change in the near term, I recommend building ITM from...

I haven't had a chance to test this yet @dboulware

This would be an excellent addition!

This seems like a more limiting change to the spec than the one proposed in #237, although maybe I am misunderstanding the use case here.

Maybe there's a split of 3 different ways for handling geolocation metadata: Case 1 (recordings by static receiver at a single location): Use the global geolocation field and no others....

If/when this gets revisited, put the information in the new wiki. Relevant wiki sections: - [Sensor Calibration](https://github.com/NTIA/scos-sensor/wiki/Sensor-Calibration) - [Component Definition Files](https://github.com/NTIA/scos-sensor/wiki/Component-Definition-Files) e.g. sensor definition files