forked from interuss/monitoring
-
Notifications
You must be signed in to change notification settings - Fork 2
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[uss_qualifier] Add ability to specify flight intents directly in con…
…figuration (interuss#341) Add ability to specify flight intents directly in configuration
- Loading branch information
1 parent
272784e
commit 9c0e2f1
Showing
14 changed files
with
463 additions
and
24 deletions.
There are no files selected for viewing
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
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
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
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
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
18 changes: 18 additions & 0 deletions
18
...toring/monitorlib/clients/flight_planning/flight_info/ASTMF354821OpIntentInformation.json
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,18 @@ | ||
| { | ||
| "$id": "https://github.com/interuss/monitoring/blob/main/schemas/monitoring/monitorlib/clients/flight_planning/flight_info/ASTMF354821OpIntentInformation.json", | ||
| "$schema": "https://json-schema.org/draft/2020-12/schema", | ||
| "description": "Information provided about a flight plan that is necessary for ASTM F3548-21.\n\nmonitoring.monitorlib.clients.flight_planning.flight_info.ASTMF354821OpIntentInformation, as defined in monitoring/monitorlib/clients/flight_planning/flight_info.py", | ||
| "properties": { | ||
| "$ref": { | ||
| "description": "Path to content that replaces the $ref", | ||
| "type": "string" | ||
| }, | ||
| "priority": { | ||
| "type": [ | ||
| "integer", | ||
| "null" | ||
| ] | ||
| } | ||
| }, | ||
| "type": "object" | ||
| } |
98 changes: 98 additions & 0 deletions
98
...as/monitoring/monitorlib/clients/flight_planning/flight_info/FlightAuthorisationData.json
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,98 @@ | ||
| { | ||
| "$id": "https://github.com/interuss/monitoring/blob/main/schemas/monitoring/monitorlib/clients/flight_planning/flight_info/FlightAuthorisationData.json", | ||
| "$schema": "https://json-schema.org/draft/2020-12/schema", | ||
| "description": "The details of a UAS flight authorization request, as received from the user.\n\nNote that a full description of a flight authorisation must include mandatory information required by ANNEX IV of COMMISSION IMPLEMENTING REGULATION (EU) 2021/664 for an UAS flight authorisation request. Reference: https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:32021R0664&from=EN#d1e32-178-1\n\nmonitoring.monitorlib.clients.flight_planning.flight_info.FlightAuthorisationData, as defined in monitoring/monitorlib/clients/flight_planning/flight_info.py", | ||
| "properties": { | ||
| "$ref": { | ||
| "description": "Path to content that replaces the $ref", | ||
| "type": "string" | ||
| }, | ||
| "connectivity_methods": { | ||
| "description": "Connectivity methods. Required by ANNEX IV of COMMISSION IMPLEMENTING REGULATION (EU) 2021/664, paragraph 7.", | ||
| "items": { | ||
| "type": "string" | ||
| }, | ||
| "type": "array" | ||
| }, | ||
| "emergency_procedure_url": { | ||
| "description": "The URL at which the applicable emergency procedure in case of a loss of command and control link may be retrieved. Required by ANNEX IV of COMMISSION IMPLEMENTING REGULATION (EU) 2021/664, paragraph 9.", | ||
| "type": "string" | ||
| }, | ||
| "endurance_minutes": { | ||
| "description": "Endurance of the UAS. This is expressed in minutes. Required by ANNEX IV of COMMISSION IMPLEMENTING REGULATION (EU) 2021/664, paragraph 8.", | ||
| "type": "integer" | ||
| }, | ||
| "identification_technologies": { | ||
| "description": "Technology used to identify the UAS. Required by ANNEX IV of COMMISSION IMPLEMENTING REGULATION (EU) 2021/664, paragraph 6.", | ||
| "items": { | ||
| "type": "string" | ||
| }, | ||
| "type": "array" | ||
| }, | ||
| "operation_category": { | ||
| "description": "Category of UAS operation (\u2018open\u2019, \u2018specific\u2019, \u2018certified\u2019) as defined in COMMISSION DELEGATED REGULATION (EU) 2019/945. Required by ANNEX IV of COMMISSION IMPLEMENTING REGULATION (EU) 2021/664, paragraph 4.", | ||
| "enum": [ | ||
| "Unknown", | ||
| "Open", | ||
| "Specific", | ||
| "Certified" | ||
| ], | ||
| "type": "string" | ||
| }, | ||
| "operation_mode": { | ||
| "enum": [ | ||
| "Undeclared", | ||
| "Vlos", | ||
| "Bvlos" | ||
| ], | ||
| "type": "string" | ||
| }, | ||
| "operator_id": { | ||
| "description": "Registration number of the UAS operator.\nThe format is defined in EASA Easy Access Rules for Unmanned Aircraft Systems GM1 to AMC1\nArticle 14(6) Registration of UAS operators and \u2018certified\u2019 UAS.\nRequired by ANNEX IV of COMMISSION IMPLEMENTING REGULATION (EU) 2021/664, paragraph 10.", | ||
| "type": "string" | ||
| }, | ||
| "uas_class": { | ||
| "enum": [ | ||
| "Other", | ||
| "C0", | ||
| "C1", | ||
| "C2", | ||
| "C3", | ||
| "C4", | ||
| "C5", | ||
| "C6" | ||
| ], | ||
| "type": "string" | ||
| }, | ||
| "uas_id": { | ||
| "description": "When applicable, the registration number of the unmanned aircraft.\nThis is expressed using the nationality and registration mark of the unmanned aircraft in\nline with ICAO Annex 7.\nSpecified by ANNEX IV of COMMISSION IMPLEMENTING REGULATION (EU) 2021/664, paragraph 10.", | ||
| "type": [ | ||
| "string", | ||
| "null" | ||
| ] | ||
| }, | ||
| "uas_serial_number": { | ||
| "description": "Unique serial number of the unmanned aircraft or, if the unmanned aircraft is privately built, the unique serial number of the add-on. This is expressed in the ANSI/CTA-2063 Physical Serial Number format. Required by ANNEX IV of COMMISSION IMPLEMENTING REGULATION (EU) 2021/664, paragraph 1.", | ||
| "type": "string" | ||
| }, | ||
| "uas_type_certificate": { | ||
| "description": "Provisional field. Not applicable as of September 2021. Required only if `uas_class` is set to `other` by ANNEX IV of COMMISSION IMPLEMENTING REGULATION (EU) 2021/664, paragraph 4.", | ||
| "type": [ | ||
| "string", | ||
| "null" | ||
| ] | ||
| } | ||
| }, | ||
| "required": [ | ||
| "connectivity_methods", | ||
| "emergency_procedure_url", | ||
| "endurance_minutes", | ||
| "identification_technologies", | ||
| "operation_category", | ||
| "operation_mode", | ||
| "operator_id", | ||
| "uas_class", | ||
| "uas_serial_number" | ||
| ], | ||
| "type": "object" | ||
| } |
102 changes: 102 additions & 0 deletions
102
schemas/monitoring/monitorlib/clients/flight_planning/flight_info/RPAS26FlightDetails.json
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,102 @@ | ||
| { | ||
| "$id": "https://github.com/interuss/monitoring/blob/main/schemas/monitoring/monitorlib/clients/flight_planning/flight_info/RPAS26FlightDetails.json", | ||
| "$schema": "https://json-schema.org/draft/2020-12/schema", | ||
| "description": "Information about a flight necessary to plan successfully using the RPAS Platform Operating Rules version 2.6.\n\nmonitoring.monitorlib.clients.flight_planning.flight_info.RPAS26FlightDetails, as defined in monitoring/monitorlib/clients/flight_planning/flight_info.py", | ||
| "properties": { | ||
| "$ref": { | ||
| "description": "Path to content that replaces the $ref", | ||
| "type": "string" | ||
| }, | ||
| "aircraft_type": { | ||
| "description": "Type of vehicle being used as per ASTM F3411-22a.", | ||
| "enum": [ | ||
| "NotDeclared", | ||
| "Aeroplane", | ||
| "Helicopter", | ||
| "Gyroplane", | ||
| "HybridLift", | ||
| "Ornithopter", | ||
| "Glider", | ||
| "Kite", | ||
| "FreeBalloon", | ||
| "CaptiveBalloon", | ||
| "Airship", | ||
| "FreeFallOrParachute", | ||
| "Rocket", | ||
| "TetheredPoweredAircraft", | ||
| "GroundObstacle", | ||
| "Other" | ||
| ], | ||
| "type": [ | ||
| "string", | ||
| "null" | ||
| ] | ||
| }, | ||
| "flight_profile": { | ||
| "description": "Type of flight profile.", | ||
| "enum": [ | ||
| "AutomatedGrid", | ||
| "AutomatedWaypoint", | ||
| "Manual" | ||
| ], | ||
| "type": [ | ||
| "string", | ||
| "null" | ||
| ] | ||
| }, | ||
| "operator_number": { | ||
| "description": "Operator number.", | ||
| "type": [ | ||
| "string", | ||
| "null" | ||
| ] | ||
| }, | ||
| "operator_type": { | ||
| "description": "The type of operator.", | ||
| "enum": [ | ||
| "Recreational", | ||
| "CommercialExcluded", | ||
| "ReOC" | ||
| ], | ||
| "type": [ | ||
| "string", | ||
| "null" | ||
| ] | ||
| }, | ||
| "pilot_license_number": { | ||
| "description": "License number for the pilot.", | ||
| "type": [ | ||
| "string", | ||
| "null" | ||
| ] | ||
| }, | ||
| "pilot_phone_number": { | ||
| "description": "Contact phone number for the pilot.", | ||
| "type": [ | ||
| "string", | ||
| "null" | ||
| ] | ||
| }, | ||
| "uas_registration_numbers": { | ||
| "description": "The list of UAS/drone registration numbers that will be operated during the operation.", | ||
| "items": { | ||
| "type": "string" | ||
| }, | ||
| "type": [ | ||
| "array", | ||
| "null" | ||
| ] | ||
| }, | ||
| "uas_serial_numbers": { | ||
| "description": "The list of UAS/drone serial numbers that will be operated during the operation.", | ||
| "items": { | ||
| "type": "string" | ||
| }, | ||
| "type": [ | ||
| "array", | ||
| "null" | ||
| ] | ||
| } | ||
| }, | ||
| "type": "object" | ||
| } |
33 changes: 33 additions & 0 deletions
33
...rlib/clients/flight_planning/flight_info_template/BasicFlightPlanInformationTemplate.json
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,33 @@ | ||
| { | ||
| "$id": "https://github.com/interuss/monitoring/blob/main/schemas/monitoring/monitorlib/clients/flight_planning/flight_info_template/BasicFlightPlanInformationTemplate.json", | ||
| "$schema": "https://json-schema.org/draft/2020-12/schema", | ||
| "description": "Template to provide (at runtime) basic information about a flight plan that an operator and/or UAS can be expected to provide in most flight planning scenarios.\n\nmonitoring.monitorlib.clients.flight_planning.flight_info_template.BasicFlightPlanInformationTemplate, as defined in monitoring/monitorlib/clients/flight_planning/flight_info_template.py", | ||
| "properties": { | ||
| "$ref": { | ||
| "description": "Path to content that replaces the $ref", | ||
| "type": "string" | ||
| }, | ||
| "uas_state": { | ||
| "description": "State of the user's UAS associated with this flight plan.", | ||
| "enum": [ | ||
| "Nominal", | ||
| "OffNominal", | ||
| "Contingent" | ||
| ], | ||
| "type": "string" | ||
| }, | ||
| "usage_state": { | ||
| "description": "User's current usage of the airspace specified in the flight plan.", | ||
| "enum": [ | ||
| "Planned", | ||
| "InUse" | ||
| ], | ||
| "type": "string" | ||
| } | ||
| }, | ||
| "required": [ | ||
| "uas_state", | ||
| "usage_state" | ||
| ], | ||
| "type": "object" | ||
| } |
Oops, something went wrong.