This Service Interface exposes operations used by the Operational Supervisor to modify the Aerodrome Configuration Data.
Operations
Allows to modify the current configuration of the runways for an aerodrome of a given Aerodrome Group.
This operation enables an eligible user (normally a supervisor) to modify the following data of a given runway or of the runway(s) of an aerodrome: landing and/or take-off rates, IAP in operation and operating mode (open or closed).
It is also possible to revert to default rate values of runway(s) if no rate value is provided in the operation..
Allows replacing the current Aerodrome Group Configuration with another given aerodrome group configuration.
The user may activate an offline predefined aerodrome group configuration, activate the one previously defined as the Next one or revert back to the default one.
When the aim of this operation is to :
- activate an offline predefined aerodrome group configuration, aerodromeGroupConfigName should be filled with the name of the configuration,
- activate the next aerodrome group configuration, aerodromeGroupConfigName should not be filled,
- revert back to the default aerodrome group configuration, aerodromeGroupConfigName should not be filled and aerodromeConfigurationOrigin should be DEFAULT.
.
Allows removing the fact that an aerodrome group configuration is identified as the next one..
Allows modifying the configuration parameters of an aerodrome.
The 3 possibilities given by this operation are :
- revert to default the aerodrome Altitude Correction
- revert to default the aerodrome Transition Level. In this case, defaultAltitudeCorrection should be set to FALSE
- modify one or several of the following parameters : transitionLevel, altitudeCorrection, modeSCapabilityState. In this case, revertToDefault should not be filled
aerodromeGroup is ignored by CCS..
Allows changing the next configuration to be applied for an aerodrome group by selecting another aerodrome configuration from a predefined configuration list, and/or to change the date and time that the configuration is planned to be activated.
.
Information is exchanged in Protobuf format. Protocol buffers or Protobuf are Google's language-neutral, platform-neutral, extensible mechanism for serializing structured data similar to XML, but smaller, faster, and simpler.