Open GoogleCodeExporter opened 8 years ago
Thanks for the input.
Toolspecifics, as always, are free to be designed by the tool implementors.
For the overall DOC we need to start a discussion with further partners prior
to CPACS 2.1
Original comment by daniel.b...@googlemail.com
on 28 Aug 2012 at 9:18
Better proposal in attachment
Original comment by brsverv...@gmail.com
on 13 Sep 2012 at 1:19
Attachments:
While on the topic of cost, a place to put the aircraft price would be useful
as well. I'm thinking along the lines of the mass breakdown, with total
aircraft cost subdivided in airframe and engine(s) cost, etc.
Original comment by brsverv...@gmail.com
on 9 Jan 2013 at 1:35
Original comment by daniel.b...@googlemail.com
on 16 Apr 2013 at 9:40
This issue is opened again, as DOC will be shifted towards the flightplan node
within fleets. See attached file for details from a discussion with RWTH Aachen
Original comment by daniel.b...@googlemail.com
on 11 Dec 2013 at 10:00
Attachments:
Issue 365 has been merged into this issue.
Original comment by daniel.b...@googlemail.com
on 19 Feb 2014 at 4:15
Original comment by daniel.b...@googlemail.com
on 7 May 2014 at 1:36
Original issue reported on code.google.com by
brsverv...@gmail.com
on 2 Aug 2012 at 8:25