Is your feature request related to a problem? Please describe.
I observed a USS indicate a time range of A to B in their op intent details when the op intent reference indicated a time range of A-dA to B-dB, but InterUSS automated tests for F3548-21 did not indicate failure for any requirements. This situation isn't allowed because the time period from B-dB to B is one in which the USS says their op intent uses (per information in details), but the reference does not indicate that the op intent covers that time period. This is a violation of USS0105,1 since the fields of the reference were not populated consistently with the details fields according to the API documentation.
Describe the solution you'd like
Whenever uss_qualifier obtains the details of an op intent from a USS, uss_qualifier should check (to the extent of its ability) that the 4D extent of the detailed op intent volumes is contained within the 4D extent of the op intent reference. So, for instance, it's ok that the details indicate a start time of A while the reference indicates a start time of A-dA because A is within the time range starting at A-dA. However, it is not ok that the details indicate an end time of B while the reference indicates an end time of B-dB because B is not within the time range ending at B-dB. This same logic should be applied to the altitude extents as well. This logic cannot be applied to 2D extents since an OperationalIntentReference does not specify 2D extents.
I expect this check would likely be a candidate for inclusion in OpIntentValidator.
Note: the reference data other than OVN should match exactly between USS and DSS (see #1378 separately); this Issue is regarding the op intent details being consistent with the reference.
Is your feature request related to a problem? Please describe.
I observed a USS indicate a time range of A to B in their op intent details when the op intent reference indicated a time range of A-dA to B-dB, but InterUSS automated tests for F3548-21 did not indicate failure for any requirements. This situation isn't allowed because the time period from B-dB to B is one in which the USS says their op intent uses (per information in
details), but the reference does not indicate that the op intent covers that time period. This is a violation of USS0105,1 since the fields of thereferencewere not populated consistently with thedetailsfields according to the API documentation.Describe the solution you'd like
Whenever uss_qualifier obtains the details of an op intent from a USS, uss_qualifier should check (to the extent of its ability) that the 4D extent of the detailed op intent volumes is contained within the 4D extent of the op intent reference. So, for instance, it's ok that the details indicate a start time of A while the reference indicates a start time of A-dA because A is within the time range starting at A-dA. However, it is not ok that the details indicate an end time of B while the reference indicates an end time of B-dB because B is not within the time range ending at B-dB. This same logic should be applied to the altitude extents as well. This logic cannot be applied to 2D extents since an OperationalIntentReference does not specify 2D extents.
I expect this check would likely be a candidate for inclusion in OpIntentValidator.
Note: the reference data other than OVN should match exactly between USS and DSS (see #1378 separately); this Issue is regarding the op intent details being consistent with the reference.