| vehicles Element |
Vehicles
Namespace: Empty
Schema: Empty
Type
ParentsChildren| Name | Occurrences | Description |
|---|---|---|
 All | ||
 aircraft | [0, 1] | Aircraft |
| deckElements | [0, 1] | Deck elements |
| energyCarriers | [0, 1] | Energy Carriers |
| engines | [0, 1] | Engines |
| flightPoints | [0, 1] | Flight Cases |
| materials | [0, 1] | Materials |
| performanceCases | [0, 1] | Performance Cases |
| profiles | [0, 1] | Profiles |
| rotorcraft | [0, 1] | Rotorcraft |
| rotorElements | [0, 1] | Rotor elements |
| structuralElements | [0, 1] | Structural elements |
| systemElements | [0, 1] | System elements |
Attributes| Name | Type | Required | Description |
|---|---|---|---|
 externalDataDirectory |  string | ||
| externalDataNodePath | string | ||
| externalFileName | string |
RemarksThe vehiclesType contains all vehicle-specific data.
This includes the vehicle itself (i.e. aircraft and rotorcraft). Furthermore, components (e.g. engines, structuralElements, etc.) as well as physical properties of materials and fuels can be predefined for easy and consistent reuse via uID-references.
See Also