Multiple gravimeters per flight?

[cbertinato]

Consider how we might deal with multiple sensors per flight. This has certainly happened on many of our flights and I can see how a user might want to make comparisons between sensors. This is a discussion thread for now, but I think we should push this feature in the next after initial release.

[bradyzp]

Hey Chris good point, I had vaguely considered that in the project restructuring - and my thought is/was that each Flight could have 1 or more DataSets, each containing a pair of Gravity/Trajectory data, associated segments (flight-lines), and a link to a sensor defined at the project level.

I think what would make sense then too (interface wise) is to have a new tab created on a per-dataset basis, so you could open multiple datasets from a single flight, and individually plot/transform them. Doing more detailed comparisons/overlays would be something more complex to handle in the future however.

This would also tie into how I'd like to flatten the tree structure a bit, removing the DataSets folder under flights, so that each dataset would be a direct child (in the UI) of their flight, then everything would nest under them.

Something to consider then would be if we should/could add some functionality to copy Flight Lines/Data Segments between DataSets in a Flight, saving the user from re-creating the segments which should be pretty much identical I'm assuming if we're talking about two sensors being flown on the same flight.