Wasmer Consulting Scientific and Engineering Software

Previous  Home  Site Map  Contact  Next

Wasmer Consulting - BaseOps - User's Guide - Editing Data With a Spreadsheet


BaseOps User's Guide, Chapter 28: Editing Data With a Spreadsheet

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.

Exporting Flight Operations to a Spreadsheet

To export the current case's flight operations to a spreadsheet, follow these steps.

  1. Choose Export Flight Operations to Spreadsheet from the File menu. The Export Flight Operations dialog box appears.

  2. 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 " - Operations.xml" added.

    Alternatively, you can type a file name in the box provided. Press the Browse button , located to the right of the text box, to display the Open File dialog box, which allows you to browse for the file.

  3. Go to the Columns page of the Export Flight Operations dialog box.

    BaseOps will automatically export the following columns to the spreadsheet.

    • Aircraft name

    • Flight profile name

    • Flight track name

    • Flight track type (arrival, departure, etc.)

    • Number of day operations

    • Number of evening operations (if the case uses the evening period)

    • Number of night operations

    You can optionally export the following additional columns to the spreadsheet.

    • Flight profile long name

    • Runway or VTOL pad name

    • Aircraft engine name

    • Noise model used for the aircraft (NMap, AAM, etc.)

    • Any groups that are applicable to flight profiles (such as aircraft category)

    Check the box next to each additional column that you would like to export.

  4. Go to the Filtering page of the Export Flight Operations dialog box.

    By default, all flight operations in the current case are exported to the spreadsheet. If desired, you can export only a subset.

    Selecting the flight profiles to export is similar to selecting the objects to display in the object list. See Filtering the Object List for more information.

  5. Press the OK button on the Export Flight Operations dialog box. The spreadsheet file is created, and the flight operations are written to it.

  6. 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.

The flight profiles in the exported spreadsheet are grouped by aircraft and flight track type. The spreadsheet includes extra columns (Num Total, % Day, % Evening [if the case uses the evening period], % Night, and % Total) and rows (Subtotal) 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.

Importing Flight Operations from a Spreadsheet

To import flight profile operation counts from a spreadsheet, follow these steps.

  1. Using Microsoft Excel, create a spreadsheet containing the flight profile operation counts. At a minimum, this spreadsheet must contain the following columns.

    • Flight profile name

    • Number of day operations

    • Number of evening operations (if the BaseOps case uses the evening period)

    • Number of night operations

    The columns can appear in any order. It does not matter if the spreadsheet contains extra columns.

  2. Save the spreadsheet to a file in XML Spreadsheet format. Choose Save As from Excel's File menu, then select XML Spreadsheet 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.

  3. Choose Import Flight Operations from Spreadsheet from the BaseOps File menu. The Import Flight Operations dialog box appears.

  4. 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 " - Operations.xml" added.

    Alternatively, you can type a file name in the box provided. Press the Browse button , located to the right of the text box, to display the Open File dialog box, which allows you to browse for the file.

  5. Go to the Columns page of the Import Flight Operations dialog box.

    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.

    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 Also import flight tracks box, and select the column containing the track names.

  6. Go to the Missing Data page of the Import Flight Operations dialog box.

    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.

    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.

    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.

  7. 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.

Tip:

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.

Editing Static Profiles with a Spreadsheet

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 Importing Flight Operations from a Spreadsheet and Exporting Flight Operations to a Spreadsheet.

The key differences between editing flight and static profiles using a spreadsheet are:


Previous  Home  Site Map  Contact  Next

Copyright © 1996-2017, Wasmer Consulting
Page URL: http://wasmerconsulting.com/baseops_usersguide_editingopswithspreadsheet.htm
Webmaster e-mail: wasmer@wasmerconsulting.com