Open CarstenChristmann opened 4 years ago
After nearly four years...how can we proceed in this matter?
I propose the following:
Some thoughts:
runways
may already be moved to airportLayout
. More and more people are currently connecting to this node, following a proposal from NLR, which is still under investigation in a project, but will be discussed/merged next year (better scalability with airspaceLayout
, airportOperations
, airspaceOperations
and more to come). So we would already avoid another change. Let's discuss again in 2028 ;-)
If I have understood correctly, airports
will be renamed to airportTypes
and airport
to airportType
in the future? From which CPACS-Version?
Your suggestion looks good. Since the abbreviations used for the distances are commonly used in the Aeronautical Information Publication (AIP), I prefer to use them here as well.
If I have understood correctly,
airports
will be renamed toairportTypes
andairport
toairportType
in the future? From which CPACS-Version?
No no, this is just visualization of the corresponding type in XSDDiagram. In the complete schema it will appear like cpacs/aiports/airport/...
.
Since the abbreviations used for the distances are commonly used in the Aeronautical Information Publication (AIP), I prefer to use them here as well.
Ok, then we will do so. I add the full names to the description field.
For the calculation of airfield (flight) performance, different airport runway distance parameters are required as shown here:
https://skybrary.aero/sites/default/files/Declared_Distances_2.jpg
Currently, the CPACS schema only includes LDA and TORA. Therefore, it is recommended to add
Accelerate Stop Distance Available (ASDA) /cpacs/airports/airport/runways/runway/aSDA
Take-off Distance Available (TODA) /cpacs/airports/airport/runways/runway/tODA