Giters
astm-utm
/
Protocol
ASTM UTM Protocol (API and sequence diagrams)
Geek Repo:
Geek Repo
Github PK Tool:
Github PK Tool
Stargazers:
16
Watchers:
9
Issues:
40
Forks:
10
astm-utm/Protocol Issues
`Circle` does not require `center` or `radius` properties
Updated
a year ago
Appropriate use of exclusiveMinimum and exclusiveMaximum
Updated
3 years ago
Comments count
4
Add polling frequency indication to position reports
Closed
3 years ago
Clarify that accuracy field in situational awareness position report is optional
Closed
3 years ago
Fix constraint reference error conditions
Closed
3 years ago
Add operation priorities
Closed
3 years ago
Use RID-style geo format rather than GeoJSON
Closed
3 years ago
Clarify that any object field can be set to null rather than omitted for the same effect
Closed
3 years ago
Specify expected value for "no-fly" constraint type
Closed
3 years ago
Add operation ID to telemetry model
Closed
3 years ago
Implement basic down-USS mitigation
Closed
3 years ago
Clearly document Subscription dependency behavior
Closed
4 years ago
Separate entity_conflicts by type in AirspaceConflictResponse
Closed
4 years ago
Comments count
1
Clarify expected USS behavior when transitioning Operations
Closed
4 years ago
Clarify behavior of GET /operations/{id} when operation is Ended
Closed
4 years ago
Comments count
1
Add data logging pseudo-endpoint
Closed
3 years ago
Comments count
1
Restore sequential version for Operation references and Constraint references
Closed
4 years ago
Investigate multiple scope specification
Closed
4 years ago
Harmonize with text of standard
Closed
3 years ago
Clean up missing OVNs response
Closed
4 years ago
Make ID terminology consistent
Closed
4 years ago
Comments count
1
Clarify mapping between DELETE and "Ended"
Closed
4 years ago
Wrong scopes for Constraint details endpoints
Closed
3 years ago
Comments count
1
clarify JWT Claim 'scope' datatype in ASTM and RID specs
Closed
4 years ago
Comments count
1
Start and end times for Operations and Constraints should be required
Closed
4 years ago
aud is not a required field
Closed
3 years ago
Comments count
1
Altitude bounds in Volume3D should not be required in general
Closed
4 years ago
Comments count
1
`state` field in OperationDetails is not required
Closed
4 years ago
Comments count
1
Specify that at least one notification type is required in Subscription
Closed
4 years ago
Comments count
3
if 'anyOf' is imported to AWS API Gateway, schema-level validations are silently omitted by Gateway
Updated
3 years ago
Comments count
5
Remove regex expressions
Updated
4 years ago
Comments count
1
Make "references" terminology consistent
Closed
4 years ago
Comments count
1
Remove single scope specification
Closed
4 years ago
Comments count
2
Version type should be string rather than int
Closed
4 years ago
Comments count
1
Object deletion needs versioning
Closed
4 years ago
Comments count
3
Incorrect representation of Circle in utm.yaml
Closed
4 years ago
Comments count
3
DSS API GeoJSON Polygon Discrepancy
Closed
4 years ago
Comments count
1
Possible DSS endpoints inconsistency
Closed
4 years ago
Comments count
3
Response code for telemetry request on nominal operation
Closed
4 years ago
USS Operation notification endpoint not fully RESTful
Closed
3 years ago
Comments count
1