[flight_planning] Add RID-relevant information to flight planning interface #33
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
mickmis
approved these changes
Mar 25, 2025
Comment on lines
+15
to
+17
| message: | ||
| description: Message presented to the user, description of notification, or other means of helping identify the nature of the notification, for the purpose of increased readability of test reports. | ||
| type: string |
There was a problem hiding this comment.
Is this change intended? It is not included in the PR description.
Although checking injection.yaml it is probably intended.
| type: string | ||
| example: INTCJ123-4567-890 | ||
| default: '' | ||
| registration_numbers: |
There was a problem hiding this comment.
Is there any reason why this is enabling multiple registration IDs? While the original UASID schema only enables one.
| type: string | ||
| example: N | ||
| default: '' | ||
| type: |
There was a problem hiding this comment.
This seems to be an addition compared to the original UASID schema. Is this required?
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.
Currently, we have two different interfaces for actuating flight-related activities on systems under test: the
ridinjection interface allows us to "inject" a flight for the purpose of remote ID testing, and theflight_planninginterface allows us to originate a flight for other flight planning purposes. This can be problematic for systems which perform multiple UTM functions in response to a single user interface, however, as they will need to implement two different interfaces and each interface may not specify a sufficient amount of information for the flight.This PR attempts to move toward addressing this issue by adding RID-relevant information to the flight planning interface. In the future, we can allow USSs to use either the
ridinjection interface or theflight_planninginterface to "inject" RID flights (in the same way we support the deprecatedscdinterface alongside theflight_planninginterface), which will then allow us to gracefully deprecate theridinjection interface entirely (theridobservation interface will remain relevant).The information in this PR is intended to cover all the information in the
ridinjection interface, but not necessarily use the same format. Instead, it attempts to capture the information that might be provided/necessary from a user of a USS's system if that USS were performing remote ID. To this end, three groups of information are added to aFlightPlan:BasicFlightPlanInformation)uasfield with information defined in uas.yaml)operatorfield with information defined in operator.yaml)