-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add diagnostics and data products. Specify sigan settings and cal info captures. JSON Schema 2020-12. #42
Conversation
…aproducts, removed location extension, added nasctn-sea extension.
…entation passing test from sensor.
…tation. Renamed Java class to SPU.
* Point to v1.x (current default) branch of SigMF. Changes made in v1.x should remain backwards-compatible with v1.0.0. * Also includes a minor change to the datetime type listing for some objects, since the previously linked section can no longer be linked.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See above comments
…Correct xunits and yunits to x_units and y_units. Fix CPU type to Computer. Fix rfpaths link. Remove duplicate waveform extension listing. Remove setCoordinates in GeoJsonPoint. Update javadocs.
… from algorithm example.
* Get the action that produced the Acquisition, or unknown if it is not in the metadata. | ||
* @return The name of the action that produced the Acquisition. | ||
*/ | ||
public String getActionName() { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please confirm that removal of getActionName
is intended
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It was, but I think it makes sense to add back in.
@@ -1,34 +0,0 @@ | |||
package gov.doc.ntia.sigmf; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why was SchemaGenerator
removed?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It didn't handle some annotations properly and wasn't generating the schema in the latest version of the JSON Schema spec (2020-12)
This PR: