[mock_uss/ridsp] Expose aircraft_type through observation interface #859
Conversation
This file contains 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
mickmis
force-pushed
the
net0260/mockussobserve
branch
3 times, most recently
from
77e7912 to
e1a766d
Compare
mickmis
force-pushed
the
net0260/mockussobserve
branch
from
e1a766d to
ae477ae
Compare
BenjaminPelletier
approved these changes
Dec 9, 2024
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.
#854 updated uas_standards to the version that includes the
aircraft_typein the injection data. With the dependency update the injected aircraft_type was 'automatically' stored.This PR wires up the mock USS to expose it through the observation interface.
There is a special case that is handled: the definitions of the enums in both versions of RID do not match. In v22a VTOL is replaced by HybridAircraft. This PR accounts for that.