IMPORTANT!
This article is a stub that has been created in preparation for future updates and as such contains no meaningful information on this subject.

The ApronControlServices.xml file is used to define the services that are available at an airport, as well as any vehicles that you wish to define. This file is only needed if you wish to create your own Apron Services or vehicles for use in an apron service, otherwise the default services and vehicles can be used by your airports (and this is the recommended way to proceed).

 

If you wish to create your own services/vehicles, then this file will need to be created as part of an airport package. You would create an SPB asset group in the package, call it ApronControl, and the save the XML file. The file has to be named ApronControlServices.xml. The package and package sources should look like this:

Example Of Where To Create An ApronControlSevice XML File

 

The ApronControlServices file is written using XML, and it can easily be created and edited using any text editor. The general format for the file is as follows:

<?xml version="1.0" encoding="Windows-1252"?>
<SimBase.Document Type="ApronControlService" version="1.0">
    
    <ApronControl.ApronServices>
        <ApronService Name ="SERVICE_NAME" Filename="SERVICE_FILENAME" Foldername="FOLDER_NAME" FallbackFilename="FALLBACK_FILE"/>
        
    </ApronControl.ApronServices>
    
    <ApronControl.ApronVehicleParams>
        <ApronVehicleParam Name="VEHICLE_NAME" ServiceName="SERVICE_NAME" BehaviourName="BEHAVIOUR_NAME"/>
        
    </ApronControl.ApronVehicleParams>
</SimBase.Document>

 

Note that for each ApronService that is listed, there will need to be an accompanying folder named after the service which contains the apron service XML file.

 

 

<ApronControl.ApronServices>

This is a container element for one or more <ApronService /> elements.

 

 

<ApronService />

This is a self-closing sub-element of <ApronControl.ApronServices> and is used to register a single apron service for use in an airport. You may have multiple of these elements to register multiple different services as available.

 

This element has the following attributes:

 

AttributeDescriptionTypeRequired
NameThis is the name of the service being registered, and is what will be used in other elements to reference or request the service.StringYes
FilenameThis is the name of the XML file associated with the service.StringYes
FoldernameThis is the folder where the XML file for the service is located.StringYes
FallbackFilenameThis is an optional attribute that can be used to define a fallback service to use when the service being registered can’t be used. This is only really applicable if you are creating a service that can be used at any airport, since it’s possible that not all airports will have the required data for full apron services to work. For more information please see the section on Fallback Services.StringNo

 

 

 

<ApronControl.ApronVehicleParams>

This is a container element for one or more <ApronControlServiceType> elements.

 

 

<ApronVehicleParam />

This is a self-closing sub-element of <ApronControl.ApronVehicleParams> and is used to register a single vehicle (and it’s associated navigation service and behaviour) with the airport for use in Apron Services. You may have multiple of these elements to register multiple different vehicles as available.

This element has the following attributes:

 

AttributeDescriptionTypeRequired
NameThis is the name of the vehicle, as referenced in <ApronControl.ApronContextReference /> or <ApronControlServiceType>.StringYes
ServiceNameThe name of the Navigation Service to spawnStringYes
BehaviourNameThe name of the <Behaviour> of this vehicle inside this cabinserviceStringYes
ContainerTitleThe name of the SimObject to spawn and use the service and behaviour.StringNo