search

nasa / utm-docs

16 stars 16 forks source link

Dynamic waypoints? #44

Closed nasajoey closed 5 years ago

nasajoey commented 5 years ago

https://github.com/nasa/utm-docs/blob/23d170472059ea3d9eb626e6580ea809fb38f9cf/TCL4%20Data%20Management/utm-tcl4-dmp-aircraft-flightplan.yaml#L17

@akishiha how do we handle dynamic waypoints? This model assumes preflight, non-changing list of waypoints I think.

nasajoey commented 5 years ago

Do we assume timestamp covers this? Later submissions (during operation) are assumed to be an updated set of waypoints? Or do we need an additional field:

waypoint_collection_index: description: >- For sets of waypoints that are dynamically defined, this index indicates the order in which each set was created. An initial plan would be 1, a dynamic update would then be 2, etc. with a full set of waypoints defined with their own set of type: integer minimum: 1 maximum: 9999

Thoughts? I may be missing something, so any clarification would be welcome.

akishiha commented 5 years ago

This model can accommodate dynamic waypoints even though we have organized it under the preflight banner.

The primary key here is the waypoint_sequence_id a uuid.

We only support post and deletes. To accommodate a new waypoint for a particular (call,run) it is just another post during flight. To accommodate a change in waypoints for a particular (call,run), it is a delete of waypoint_sequence_id followed by a new post.

akishiha commented 5 years ago

Note that in the final implementation we are saving all raw HTTP communications on S3 so all of this can be reconstructed if needed.

nasajoey commented 5 years ago

seems good. Thanks.