
<section id='BaseOps_ImportingFromINM_id' webfilename='importfrominm'>
    <title>
        Importing Integrated Noise Model (INM) Cases
    </title>
    <para>
        The United States' Federal Aviation Administration's Integrated
        Noise Model (INM) is commonly used to calculate the noise levels
        around civilian airports. BaseOps can import some information
        from INM cases.
    </para>
    <note type='important'>
        <para>
            There are a number of differences between the ways that Noisemap/BaseOps
            and INM represent noise cases. For example, some INM flight tracks
            are point-to-point tracks (p-tracks), while all Noisemap flight
            tracks are represented using vectors.
        </para>
        <para>
            Because of these differences, the typical INM cases will have
            data that BaseOps cannot import. Using BaseOps' "Import INM Case"
            feature should be viewed as merely the first step in converting
            an INM case into a BaseOps case. You should carefully check all
            imported INM cases to insure that no differences were introduced
            by the importation process.
        </para>
    </note>
    <para>
        To import an INM case, follow these steps.
    </para>
    <orderedlist>
        <listitem>
            <para>
                Choose <menutext>Import INM Case</menutext> from the <menutext>File</menutext>
                menu. The Import INM Case dialog box appears.
            </para>
            <exhibit>
                <img src='BaseOps_INM_ImportINMCaseDialogBox_ScreenCap.png'/>
            </exhibit>
        </listitem>
        <listitem>
            <para>
                <italic>INM System Data File "prof_pts.dbf"</italic> - Type the
                full path name of the INM system file named <filetext>prof_pts.dbf</filetext>.
                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>
            <para>
                This file will be located in the <filetext>sys_data</filetext>
                subdirectory of the INM directory.
            </para>
        </listitem>
        <listitem>
            <para>
                <italic>INM Case File "ops_calc.dbf"</italic> - Type the full
                path name of the INM case file named <filetext>ops_calc.dbf</filetext>.
                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>
            <para>
                This file will be located in the case directory of the INM case
                you wish to import. You may need to run the INM case to create
                this file. The case directory will be a subdirectory of an INM
                study directory.
            </para>
        </listitem>
        <listitem>
            <para>
                <italic>Origin of INM Study Coordinates</italic> - Enter the origin
                of the coordinates used by the INM study that contains the case
                you are importing. You can find the origin by choosing <menutext>Study</menutext>
                from INM's <menutext>Setup</menutext> menu.
            </para>
        </listitem>
        <listitem>
            <para>
                Press OK. BaseOps imports as much data as it can from the INM
                case.
            </para>
        </listitem>
        <listitem>
            <para>
                Carefully check the imported case. BaseOps will attempt to
                issue warning messages describing any problems it finds while
                importing the case. However, it cannot automatically detect all
                problems, so you must check the imported case even if you receive no
                warning messages.
            </para>
        </listitem>
    </orderedlist>
</section>
