| rotorBlade Element |
Rotor blade geometries are defined using the same data structure as wings (wingType). But in order to be compatible with the other rotor blade related types (e.g. rotorType, rotorHubType, rotorHubHingeType) there are some additional conventions/requirements regarding the definition and orientation of rotorBlade geometries: see remarks.
Namespace: Empty
Schema: Empty
Type
ParentsChildren| Name | Occurrences | Description |
|---|---|---|
 All | ||
 componentSegments | [0, 1] | ComponentSegments of the wing. |
| description | [0, 1] | Description of the wing. |
| dynamicAircraftModel | [0, 1] | dynamicAircraftModelType |
| name | Name of the wing. | |
| parentUID | [0, 1] | UID of part to which the wing is mounted (if any). The parent of the wing can e.g. be the fuselage. In each aircraft model, there is exactly one part without a parent part (The root of the connection hierarchy). |
| positionings | [0, 1] | Positionings of the wing. |
| sections | Sections of the wing. | |
| segments | Segments of the wing. | |
| transformation | transformationType |
Attributes| Name | Type | Required | Description |
|---|---|---|---|
 externalDataDirectory |  string | ||
| externalDataNodePath | string | ||
| externalFileName | string | ||
| symmetry |  string | ||
| uID | string | Yes |
See Also