Generic Sensor Sub Views and Timestamps #194
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This is intended for physical sensors not matching any of the currently specified sensor technologies (or not wanting to make use of those views).
pmai
added
the
FeatureRequest
ghost
merged commit
This pull request was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds generic sensor sub views (and sub configurations) to address physical sensors which either do not match the other technologies, or do not wish to use the services provided for those. This is a minimal PR, not splitting up ground-truth generation and making it view and sensor-coordinate specific.
This PR also addresses the use of doubles for times in SensorViewConfiguration, changing those to be Timestamps.