That's a good reason to have a standardized interchange format.
Scenario: David has an app he's downloaded on his phone/tablet that let's him pre-fill his flight cards out. It has the information that
he wants/needs stored in his app. He's all ready to go and packs up his fleet and heads to the field.
Once there, the field is using a different app for check-ins. David uses the "send card" feature of his app to send the flight card to the RSO's app. (Bluetooth, WiFi, NFC, doesn't matter.) If the minimum fields are present, David has checked in his rocket. RSO shoots it to LCO, who assigns it a pad and that gets sent to David, informing him where to go next.
So, RSO/LCO types: What is the
minimum information needed for a flight card? Here's what I've got, so far:
First Name | Last Name |
NAR # | TRA # |
Rocket Name | Motor (multiples possible, definition would include delay, etc.) |
Deployment Style (Electronic, Motor, etc) | Recover type (Parachute, glider, streamer, etc.) |
Mass on pad | Kit/Scratch/Bash |
Main Deployment (apogee, altitude) | Heads-Up (boolean, 0 for no, 1 for yes) |
Comments/Notes (text field, probably limited to 255 characters unless you convince me otherwise) | |
Interchange would be acknowledged by a packet that includes flight serial number to uniquely identify the flight. Once that's done and a pad is assigned, a packet with serial number and pad assignment would go back to the RSO and the flyer's app.
Comments and suggestions certainly welcome. Still working on the XML definitions.