search

nasa / utm-apis

The collection of APIs for NASA's UTM project in the form of OpenAPI documents.
55 stars 35 forks source link

Operator API - stakeholders should review conformance & protected buffer definitions #123

Closed issmith1 closed 5 years ago

issmith1 commented 6 years ago

Stakeholders using Conformance and Protected buffer definitions should review the TCL4 Operator API definition. In particular, TCL2's Operator API definitions for conformance buffer are zero which seems wrong. The commit history shows these values in place on Oct. 2016.

For TCL4 the buffer values will be stored as a OperationVolume specific property. The TCL4 implementation allows binding these runtime to support the use case where an SDSP is consulted to modify values based on, say, weather, vehicle type or density.

TCL2 Default values are defined on line 56. https://atmjira.arc.nasa.gov:7443/stash/projects/UTM/repos/utm/browse/utm-config/src/main/resources/application.properties

TCL4 defaults defined line 82 in https://github.com/nasa/NUSS/blob/utm3830conformanceProtectedBuffers/src/main/resources/application.yml

issmith1 commented 6 years ago

@vbaskara Adding you so you are aware of the conformance values. Note that TCL2 had them zero, and at this time in the branch they are 1.

issmith1 commented 5 years ago

No complaints from stakeholders. Good enough