
<section id='BaseOps_EditingFlightOpsWithSpreadsheet_id'
webfilename='editingopswithspreadsheet'>
    <title>
        Editing Data With a Spreadsheet
    </title>
    <para>
        Using BaseOps, you can edit all aspects of a BaseOps case. However,
        there may be situations where it is more convenient to edit data
        using Microsoft Excel. BaseOps gives you the ability to export
        and import portions of a BaseOps case's data to/from a spreadsheet
        file in XML format. For flight profiles, the operations counts
        can be edited in this manner. For static profiles, full round-trip
        editing of all static profile properties is supported.
    </para>
    <section
    id='BaseOps_EditingFlightOpsWithSpreadsheet_Exporting_id'>
        <title>
            Exporting Flight Operations to a Spreadsheet
        </title>
        <para>
            To export the <link target='#BaseOps_IntroductionToCases_id'>current
            case's</link> flight operations to a spreadsheet, follow these
            steps.
        </para>
        <orderedlist>
            <listitem>
                <para>
                    Choose <menutext>Export Flight Operations to Spreadsheet</menutext>
                    from the <menutext>File</menutext> menu. The Export Flight Operations
                    dialog box appears.
                </para>
                <exhibit>
                    <img
                    src='BaseOps_ExportFlightOpsToSpreadsheetDialogBox_ScreenCap.png'/>
                </exhibit>
            </listitem>
            <listitem>
                <para>
                    Go to the File page of the Export Flight Operations dialog box,
                    and select the spreadsheet file to which you would like to export
                    the operations. You can export to the default file, which will
                    be the same as the BaseOps case file name, but with the suffix
                    "<filetext>&nbsp;-&nbsp;Operations.xml</filetext>" added.
                </para>
                <para>
                    Alternatively, you can type a file name in the box provided. Press
                    the Browse button <img src='WCF_ThreeDotsButton_Figure.png'/>,
                    located to the right of the text box, to display the Open File
                    dialog box, which allows you to browse for the file.
                </para>
            </listitem>
            <listitem>
                <para>
                    Go to the Columns page of the Export Flight Operations dialog
                    box.
                </para>
                <exhibit>
                    <img
                    src='BaseOps_ExportFlightOpsToSpreadsheetDialogBox_Columns_ScreenCap.png'/>
                </exhibit>
                <para>
                    BaseOps will automatically export the following columns to the
                    spreadsheet.
                </para>
                <unorderedlist>
                    <listitem>
                        <para>
                            Aircraft name
                        </para>
                    </listitem>
                    <listitem>
                        <para>
                            Flight profile name
                        </para>
                    </listitem>
                    <listitem>
                        <para>
                            Flight track name
                        </para>
                    </listitem>
                    <listitem>
                        <para>
                            Flight track type (arrival, departure, etc.)
                        </para>
                    </listitem>
                    <listitem>
                        <para>
                            Number of day operations
                        </para>
                    </listitem>
                    <listitem>
                        <para>
                            Number of evening operations (if the case uses the evening period)
                        </para>
                    </listitem>
                    <listitem>
                        <para>
                            Number of night operations
                        </para>
                    </listitem>
                </unorderedlist>
                <para>
                    You can optionally export the following additional columns to
                    the spreadsheet.
                </para>
                <unorderedlist>
                    <listitem>
                        <para>
                            Flight profile long name
                        </para>
                    </listitem>
                    <listitem>
                        <para>
                            Runway or VTOL pad name
                        </para>
                    </listitem>
                    <listitem>
                        <para>
                            Aircraft engine name
                        </para>
                    </listitem>
                    <listitem>
                        <para>
                            Noise model used for the aircraft (NMap, AAM, etc.)
                        </para>
                    </listitem>
                    <listitem>
                        <para>
                            Any groups that are applicable to flight profiles (such as aircraft
                            category)
                        </para>
                    </listitem>
                </unorderedlist>
                <para>
                    Check the box next to each additional column that you would like
                    to export.
                </para>
            </listitem>
            <listitem>
                <para>
                    Go to the Filtering page of the Export Flight Operations dialog
                    box.
                </para>
                <exhibit>
                    <img
                    src='BaseOps_ExportFlightOpsToSpreadsheetDialogBox_Filtering_ScreenCap.png'/>
                </exhibit>
                <para>
                    By default, all flight operations in the current case are exported
                    to the spreadsheet. If desired, you can export only a subset.
                </para>
                <para>
                    Selecting the flight profiles to export is similar to selecting
                    the objects to display in the object list. See <iref
                    target='BaseOps_FilteringListPane_id'/> for more information.
                </para>
            </listitem>
            <listitem>
                <para>
                    Press the OK button on the Export Flight Operations dialog box.
                    The spreadsheet file is created, and the flight operations are
                    written to it.
                </para>
            </listitem>
            <listitem>
                <para>
                    Start Microsoft Excel and open the spreadsheet. If your version
                    of Excel is not capable of reading XML Spreadsheet files, you
                    will need to get a later version.
                </para>
            </listitem>
        </orderedlist>
        <para>
            The flight profiles in the exported spreadsheet are grouped by
            aircraft and flight track type. The spreadsheet includes extra
            columns (<italic>Num Total</italic>, <italic>%&nbsp;Day</italic>,
            <italic>%&nbsp;Evening</italic> [if the case uses the evening
            period], <italic>%&nbsp;Night</italic>, and <italic>%&nbsp;Total</italic>)
            and rows (<italic>Subtotal</italic>) that display statistics about
            the flight profile operations counts in each aircraft/track type
            group. These statistics are calculated by spreadsheet functions,
            so if you edit the operations counts using Excel, the statistics
            are automatically updated.
        </para>
        <exhibit>
            <img
            src='BaseOps_ExportFlightOpsToSpreadsheet_ExampleSpreadsheet_Figure.png'
            standard_colors='true'/>
        </exhibit>
    </section>
    <section
    id='BaseOps_EditingFlightOpsWithSpreadsheet_Importing_id'>
        <title>
            Importing Flight Operations from a Spreadsheet
        </title>
        <para>
            To import flight profile operation counts from a spreadsheet,
            follow these steps.
        </para>
        <orderedlist>
            <listitem>
                <para>
                    Using Microsoft Excel, create a spreadsheet containing the flight
                    profile operation counts. At a minimum, this spreadsheet must
                    contain the following columns.
                </para>
                <unorderedlist>
                    <listitem>
                        <para>
                            Flight profile name
                        </para>
                    </listitem>
                    <listitem>
                        <para>
                            Number of day operations
                        </para>
                    </listitem>
                    <listitem>
                        <para>
                            Number of evening operations (if the BaseOps case uses the evening
                            period)
                        </para>
                    </listitem>
                    <listitem>
                        <para>
                            Number of night operations
                        </para>
                    </listitem>
                </unorderedlist>
                <para>
                    The columns can appear in any order. It does not matter if the
                    spreadsheet contains extra columns.
                </para>
            </listitem>
            <listitem>
                <para>
                    Save the spreadsheet to a file in XML Spreadsheet format. Choose
                    <menutext>Save As</menutext> from Excel's <menutext>File</menutext>
                    menu, then select <italic>XML Spreadsheet</italic> for the save
                    as type. If your version of Excel is not capable of writing XML
                    Spreadsheet files, you will need to get a later version.
                </para>
            </listitem>
            <listitem>
                <para>
                    Choose <menutext>Import Flight Operations from Spreadsheet</menutext>
                    from the BaseOps <menutext>File</menutext> menu. The Import Flight
                    Operations dialog box appears.
                </para>
                <exhibit>
                    <img
                    src='BaseOps_ImportFlightOpsFromSpreadsheetDialogBox_ScreenCap.png'/>
                </exhibit>
            </listitem>
            <listitem>
                <para>
                    Go to the File page of the Import Flight Operations dialog box,
                    and select the spreadsheet file that you would like to import
                    the operations from. You can import from the default file, which
                    will be the same as the BaseOps case file name, but with the suffix
                    "<filetext> - Operations.xml</filetext>" added.
                </para>
                <para>
                    Alternatively, you can type a file name in the box provided. Press
                    the Browse button <img src='WCF_ThreeDotsButton_Figure.png'/>,
                    located to the right of the text box, to display the Open File
                    dialog box, which allows you to browse for the file.
                </para>
            </listitem>
            <listitem>
                <para>
                    Go to the Columns page of the Import Flight Operations dialog
                    box.
                </para>
                <exhibit>
                    <img
                    src='BaseOps_ImportFlightOpsFromSpreadsheetDialogBox_Columns_ScreenCap.png'/>
                </exhibit>
                <para>
                    Select the columns in the spreadsheet that contain the required
                    information. Columns are identified by either letter (A, B, C...)
                    or number (1, 2, 3...), starting with the left-most column and
                    counting to the right.
                </para>
                <para>
                    In addition to importing flight operation counts, you can optionally
                    choose to import flight tracks. A column containing flight track
                    names is specified, and the flight profiles in the BaseOps case
                    are updated to use these tracks. To import flight tracks, check
                    the <italic>Also import flight tracks</italic> box, and select
                    the column containing the track names.
                </para>
            </listitem>
            <listitem>
                <para>
                    Go to the Missing Data page of the Import Flight Operations dialog
                    box.
                </para>
                <exhibit>
                    <img
                    src='BaseOps_ImportFlightOpsFromSpreadsheetDialogBox_MissingData_ScreenCap.png'/>
                </exhibit>
                <para>
                    Select how to handle flight profiles that appear in the spreadsheet
                    but not in the BaseOps case. You can either create new flight
                    profiles in the BaseOps case, or else simply ignore the extra
                    profiles in the spreadsheet.
                </para>
                <para>
                    Select how to handle flight profiles that appear in the BaseOps
                    case but not in the spreadsheet. You can simply leave those flight
                    profiles' operations counts unchanged. Alternatively, you can
                    delete those profiles from the BaseOps case. Exercise care if
                    you choose the second alternative; make sure that you really do
                    want the extra flight profiles to be deleted.
                </para>
                <para>
                    If you are also importing flight tracks, select how to handle
                    tracks that appear in the spreadsheet but not in the BaseOps case.
                    You can leave the tracks of the affected profiles unchanged, set
                    the tracks of the affected profiles to "undefined", or add the
                    missing flight tracks to the BaseOps case. If you select the last
                    alternative, you will later need to manually edit the properties
                    (runway, segments, etc.) of the new flight tracks.
                </para>
            </listitem>
            <listitem>
                <para>
                    Press the OK button on the Import Flight Operations dialog box.
                    A window appears, giving an overview of the flight profiles that
                    will be modified. Press OK again, and the flight profile operations
                    counts will be imported.
                </para>
            </listitem>
        </orderedlist>
        <note type='tip'>
            <para>
                When importing flight operations from a spreadsheet, BaseOps ignores
                any rows that have a blank flight profile name; a blank flight
                track name (if importing flight tracks); or a blank or non-numeric
                day, evening, or night operations count. This allows you to have
                rows in your spreadsheet (that contain, for example, operations
                count subtotals) that are ignored when importing. Simply insure
                that one of the above-mentioned columns in these rows does not
                contain any text.
            </para>
        </note>
    </section>
    <section id='BaseOps_EditingStaticOpsWithSpreadsheet_id'>
        <title>
            Editing Static Profiles with a Spreadsheet
        </title>
        <para>
            Static profiles can be edited with a spreadsheet in a similar
            manner to flight profiles. Since the process is similar, only
            the differences are described in this section. It is assumed that
            you are familiar with editing flight profiles using a spreadsheet:
            see <iref
            target='BaseOps_EditingFlightOpsWithSpreadsheet_Importing_id'/>
            and <iref
            target='BaseOps_EditingFlightOpsWithSpreadsheet_Exporting_id'/>.
        </para>
        <para>
            The key differences between editing flight and static profiles
            using a spreadsheet are:
        </para>
        <unorderedlist>
            <listitem>
                <para>
                    For flight profiles, only operation counts and, optionally, associated
                    flight tracks, can be edited using a spreadsheet. For static profiles,
                    all properties, including the static profile segment table, can
                    be edited using a spreadsheet.
                </para>
            </listitem>
            <listitem>
                <para>
                    For flight profiles, you can choose to export certain additional
                    flight profile properties to the spreadsheet. For static profiles,
                    all static profile properties are always automatically exported.
                </para>
            </listitem>
            <listitem>
                <para>
                    For flight profiles, the column numbers in the spreadsheet are
                    user-selectable. For static profiles, column numbers are fixed.
                    Imported static profile spreadsheets much match the layout of
                    exported static profiles spreadsheets as created by BaseOps.
                </para>
            </listitem>
        </unorderedlist>
    </section>
    <section id='BaseOps_EditingAirspaceOpsWithSpreadsheet_id'>
        <title>
            Editing Airspace Profiles with a Spreadsheet
        </title>
        <para>
            Airspace profiles can be edited with a spreadsheet in a similar
            manner to flight profiles. Since the process is similar, only
            the differences are described in this section. It is assumed that
            you are familiar with editing flight profiles using a spreadsheet:
            see <iref
            target='BaseOps_EditingFlightOpsWithSpreadsheet_Importing_id'/>
            and <iref
            target='BaseOps_EditingFlightOpsWithSpreadsheet_Exporting_id'/>.
        </para>
        <para>
            The key differences between editing flight and airspace profiles
            using a spreadsheet are:
        </para>
        <unorderedlist>
            <listitem>
                <para>
                    When exporting airspace profiles, you can optionally select additional
                    parameters to include in the spreadsheet, such as the airtime
                    and the standoff distance.
                </para>
            </listitem>
            <listitem>
                <para>
                    When exporting airspace profiles, you can filter which profiles
                    to export by the profile type (either MOAs, MTRs, or both).
                </para>
            </listitem>
            <listitem>
                <para>
                    When importing airspace profiles with the option to import areas
                    and routes, the option to add missing areas/routes that are not already
                    present in the BaseOps case is not supported. This is because
                    it isn't know, from the the area/route name alone, whether an area or
                    a route should be added to the case.
                </para>
            </listitem>
        </unorderedlist>
    </section>
</section>
