After comparing the RASAero II data structure to that of the current unstable, I believe that it would be appropriate to split this one issue into two issues, a new feature to export an OpenRocket design in the RASAero II file format, and a separate new issue to import RASAero II designs into OpenRocket.

• As to a new export feature, the RASAero II file format is very similar to that of the current unstable, though the variable names are different, and distances are measured in inches, not meters. It appears that all that is needed is a translator that (1) changes field names, (2) corrects numerical values, if needed, and (3) removes excess data fields.

• As to a new import feature, although RASAero II features 8 different fin cross-sections compared to the 3 in OpenRocket, in most other design features RASAero II lacks the component parameters that OpenRocket requires; for example, RASAero II does not "position" rail buttons on the body tube, it simply puts 2 buttons on the body tube according to its own internal spacing parameters. A new import feature, if even possible, will be much more complex than the export feature and require a host of acceptable default values for parameters that it does not support.

Thoughts on splitting this issue @JoePfeiffer, @wolsen, @SiboVG, @neilweinstock?

Uh oh!

RASAero import #875

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions