
<section id='BaseOps_ImportFromCase_id'
webfilename='importfromcase'>
    <title>
        Importing Information from a Noise Case File
    </title>
    <para>
        BaseOps allows you to import information into your current <link
        target='#BaseOps_IntroductionToCases_id'>BaseOps case</link> from
        a second noise case file. The imported case file can be a BaseOps
        <filetext>.baseops</filetext> or <filetext>.bps</filetext> file;
        an NMap/AAM/RNM <filetext>.ops</filetext> or <filetext>.opx</filetext>
        operations file; or an MRNMap <filetext>.inp</filetext>, <filetext>.ins</filetext>
        or <filetext>.inx</filetext> input file.
    </para>
    <para>
        You can select the subset of information to import. For example,
        assume that you are calculating the noise impact of moving an
        F-16 fighter wing from one airfield to another. Furthermore, assume
        that you have BaseOps cases that model the existing conditions
        at both airfields. You can open the destination airfield's case,
        then import all F-16 flight profiles from the source airfield's
        case.
    </para>
    <para>
        To import information from a noise case file, follow these steps:
    </para>
    <orderedlist>
        <listitem>
            <para>
                Choose <menutext>Import from Noise Case File</menutext> from the
                <menutext>File</menutext> menu. The "Select the Noise Case File
                to Import Data From" dialog box appears.
            </para>
            <exhibit>
                <img
                src='BaseOps_ImportFromCase_SelectCaseToImportFrom_ScreenCap.png'/>
            </exhibit>
        </listitem>
        <listitem>
            <para>
                Select the noise case file you wish to import from. Then press
                Open.
            </para>
        </listitem>
        <listitem>
            <para>
                The "Importing From Noise Case File" dialog box appears.
            </para>
            <exhibit>
                <img
                src='BaseOps_ImportFromCase_ImportingFromDialogBox_ScreenCap.png'/>
            </exhibit>
            <para>
                The "Importing From" dialog box is a Multiple Page dialog box.
                See <iref target='WCF_MultiplePageDialogBoxes_id'/> for more information.
            </para>
            <para>
                Visit each of the pages in the "Importing From" dialog box, and
                set the options as desired.
            </para>
        </listitem>
        <listitem>
            <para>
                Go to the Summary page, and review the summary of the options
                you have selected.
            </para>
            <exhibit>
                <img
                src='BaseOps_ImportFromCase_ImportingFromDialogBox_SummaryPage_ScreenCap.png'/>
            </exhibit>
        </listitem>
        <listitem>
            <para>
                Press OK, closing the "Importing From" dialog box. The requested
                information is imported into the current BaseOps case.
            </para>
        </listitem>
    </orderedlist>
    <section
    id='BaseOps_ImportFromCase_ImportingFromDialogBox_ImportPages_id'>
        <title>
            Selecting What Information to Import
        </title>
        <para>
            Use the Import pages of the "Importing From" dialog box to select
            what information you wish to import.
        </para>
        <exhibit>
            <img
            src='BaseOps_ImportFromCase_ImportingFromDialogBox_ImportPages_ScreenCap.png'/>
        </exhibit>
        <para>
            There is one dialog box page for each type of object (runways,
            flight tracks) that can be imported. Visit each page and set the
            options as desired, noting these points:
        </para>
        <unorderedlist>
            <listitem>
                <para>
                    A BaseOps case can only contain one instance of some types of
                    objects (for example, the weather object). If you import objects
                    of this type, their data will replace the existing data in your
                    case.
                </para>
            </listitem>
            <listitem>
                <para>
                    A BaseOps case can contain any number of instances of some types
                    of objects (for example, flight tracks). If you import objects
                    of this type, they will be added to any existing objects already
                    in your case. If you have existing objects with the same names
                    as objects you import, you will wind up with multiple objects
                    that have the same name, and will need to give each object a distinct
                    name before your case can be <link
                    target='#BaseOps_RunningCases_id'>run</link>.
                </para>
            </listitem>
            <listitem>
                <para>
                    Selecting the objects that will be imported is done in a similar
                    manner to selecting the objects to display in the object list.
                    See <iref target='BaseOps_FilteringListPane_id'/> for more information.
                </para>
            </listitem>
            <listitem>
                <para>
                    Some objects have fields that refer to other objects. For example,
                    every flight profile has a flight track field, and every flight
                    track has a runway field. You can select how these fields are
                    initialized.
                </para>
                <para>
                    As an example, consider flight profiles. You can select how the
                    flight track field of each imported flight profile is initialized.
                    You have two choices.
                </para>
                <unorderedlist>
                    <listitem>
                        <para>
                            <italic>attempt to find a flight track in the current case with
                            a matching name</italic> - The existing case is searched for a
                            flight track with the same name as the flight track that the profile
                            referred to in the imported-from case. Typically, you will select
                            this option if you <bold>are</bold> importing flight tracks along
                            with the flight profiles.
                        </para>
                    </listitem>
                    <listitem>
                        <para>
                            <italic>leave it undefined</italic> - The flight track will be
                            undefined. You will later need to manually select which flight
                            track to associate with each imported flight profile. Typically,
                            you will select this option if you <bold>are not</bold> importing
                            flight tracks, but instead will be assigning the imported flight
                            profiles to existing flight tracks in the current case.
                        </para>
                        <note type='tip'>
                            <para>
                                Use the Flight Track Assignment Tool to efficiently assign flight
                                tracks to flight profiles. See <iref
                                target='BaseOps_AssignmentTool_id'/>.
                            </para>
                        </note>
                    </listitem>
                </unorderedlist>
            </listitem>
        </unorderedlist>
        <para>
            In addition to the objects that you explicitly select to import,
            you can also choose to automatically import any linked objects.
            This choice is made on the "Linked Objects" page of the "Importing
            From" dialog box.
        </para>
        <exhibit>
            <img
            src='BaseOps_ImportFromCase_ImportingFromDialogBox_LinkedObjectsPage_ScreenCap.png'/>
        </exhibit>
        <para>
            If the "Automatically import linked objects" box is checked, then
            all linked objects will be imported. For example, assume that
            the BaseOps case you are importing from contains a flight profile FP1, a flight track
            FT1, and a runway R1. Furthermore, assume that FP1 operates on
            FT1, and FT1 is associated with R1. Now assume that you have selected
            to import FP1. In this case, FT1 and R1 will also be imported
            automatically. You don't need to manually select them for importation.
        </para>
    </section>
    <section
    id='BaseOps_ImportFromCase_ImportingFromDialogBox_ModifyPages_id'>
        <title>
            Modifying Imported Information
        </title>
        <para>
            You can use the "Name and Notes" page of the "Importing From"
            dialog box to modify the text of each imported object's name,
            long name, and notes. This is useful for marking imported objects
            so that you can identify them as such in the future.
        </para>
        <exhibit>
            <img
            src='BaseOps_ImportFromCase_ImportingFromDialogBox_NameAndNotesPage_ScreenCap.png'/>
        </exhibit>
        <para>
            The name <italic>Prefix</italic> and <italic>Suffix</italic> are
            text added to the beginning and ending, respectively, of imported
            objects' short names.
        </para>
        <note type='warning'>
            <para>
                For most types of objects, the length of the name is limited to
                10 characters. If the length of an imported object's name, plus
                the name prefix and suffix, is longer than 10 characters, the
                name will be truncated. Therefore, the name prefix and suffix
                should be very short.
            </para>
        </note>
        <para>
            The long name <italic>Prefix</italic> and <italic>Suffix</italic>
            are text added to the beginning and ending, respectively, of imported
            objects' long names.
        </para>
        <para>
            The text added to the beginning of imported objects' notes can
            contain any number of lines. Press the <keytext>Enter</keytext>
            key to insert additional lines.
        </para>
        <note type='tip'>
            <para>
                You can modify imported objects' notes to include import audit
                trail information, such as the BaseOps case imported from and
                the date the objects were imported.
            </para>
        </note>
        <para>
            Your current BaseOps case may contain <link
            target='#BaseOps_GroupChunk_id'>groups</link> that are not present
            in the case you are importing from. If so, the "Importing From"
            dialog box will contain the "Group Settings" page.
        </para>
        <exhibit>
            <img
            src='BaseOps_ImportFromCase_ImportingFromDialogBox_GroupSettingsPage_ScreenCap.png'/>
        </exhibit>
        <para>
            Use this page to select the initial values of these groups for
            the objects you are importing.
        </para>
        <note type='tip'>
            <para>
                It is often useful to mark imported objects so that they can be
                easily selected for further manipulation. For example, after importing
                flight profiles, you may wish to use the <link
                target='#BaseOps_PatternAltitudeTool_id'>Pattern Altitude Tool</link>
                to modify the imported profiles. The easiest way to do this is
                to use a group created especially for this purpose. Follow these
                steps.
            </para>
            <orderedlist>
                <listitem>
                    <para>
                        In your current BaseOps case, create a new group called, say,
                        <italic>Source</italic>. Make this group applicable to the types
                        of objects you will be importing.
                    </para>
                </listitem>
                <listitem>
                    <para>
                        Give this group two choices. The first choice should be named,
                        say, <italic>Existing</italic>. The second choice should be named,
                        say, <italic>Imported</italic>. Or, if you will be importing from
                        multiple cases, you can create a choice for each case.
                    </para>
                </listitem>
                <listitem>
                    <para>
                        Since <italic>Existing</italic> is the first choice, it will be
                        the default value for this group. Therefore, the <italic>Source</italic>
                        of all existing objects in your case will be set to <italic>Existing</italic>.
                    </para>
                </listitem>
                <listitem>
                    <para>
                        When importing from the other case, go to the Group Settings page
                        of the Importing From dialog box and select the <italic>Imported</italic>
                        value for the <italic>Source</italic> group. The <italic>Source</italic>
                        of all imported objects will be set to <italic>Imported</italic>.
                    </para>
                </listitem>
                <listitem>
                    <para>
                        If you need to edit the imported objects, filter the <link
                        target='#BaseOps_ListPane_id'>object list</link> (see <iref
                        target='BaseOps_FilteringListPane_id'/>) to only show objects
                        whose <italic>Source</italic> is set to <italic>Imported</italic>.
                        You can then easily select all imported objects and, for example,
                        run the <link target='#BaseOps_PatternAltitudeTool_id'>Pattern
                        Altitude Tool</link> on them.
                    </para>
                </listitem>
                <listitem>
                    <para>
                        After you have finished editing the imported objects, you can
                        delete the <italic>Source</italic> group. Alternatively, you can
                        leave it to permanently document the source of each object.
                    </para>
                </listitem>
            </orderedlist>
        </note>
    </section>
</section>
