
<section id='BaseOps_CaseChunk_id'
webfilename='caseinformation'>
    <title>
        Setting Core Case Properties
    </title>
    <para>
        After creating a new <link
        target='#BaseOps_IntroductionToCases_id'>BaseOps case</link>,
        your first task should be setting the core case properties. Core
        case properties can affect how the rest of a case's data is entered.
    </para>
    <para>
        In the <link target='#BaseOps_ListPane_id'>list pane</link>, choose
        Case from the <link target='#BaseOps_ListPane_id'>object type
        selector dropdown list</link>. Then set the properties in the
        <link target='#WCF_ApplicationMainWindow_id'>text pane</link>.
    </para>
    <note type='tip'>
        <para>
            BaseOps can import some core case properties from DAFIF. See the
            instructions for importing airfield information in <iref
            target='BaseOps_ImportingFromDAFIF_id'/>.
        </para>
    </note>
    <section>
        <title>
            Case Information
        </title>
        <exhibit>
            <img src='BaseOps_CaseChunk_CaseInformation_ScreenCap.png'/>
        </exhibit>
        <para>
            The <italic>Case Name</italic> is a short (60 characters maximum)
            description of a BaseOps case, such as "Wright-Patterson Air Force
            Base 1990 Noise Study". It should unambiguously identify the case.
        </para>
        <para>
            The <italic>Case Abstract</italic> is a narrative summary of a
            BaseOps case. It describes the "what" aspects of the case. There
            is no restriction on the length of the abstract. Press the <keytext>Enter</keytext>
            key to insert additional lines.
        </para>
        <para>
            The <italic>Case Purpose</italic> is a brief description of the
            reason that a BaseOps case was created. It describes the "why"
            aspects of the case. There is no restriction on the length of
            the description. Press the <keytext>Enter</keytext> key to insert
            additional lines.
        </para>
        <para>
            Use the <italic>Case Notes</italic> to store miscellaneous information
            about a case. There is no restriction on the length of notes.
            Press the <keytext>Enter</keytext> key to insert additional lines.
        </para>
    </section>
    <section>
        <title>
            Site Information
        </title>
        <exhibit>
            <img src='BaseOps_CaseChunk_SiteNameAndNotes_ScreenCap.png'/>
        </exhibit>
        <para>
            The <italic>Site Name</italic> is a short (60 characters maximum)
            description of the location being modeled by a BaseOps case. Typically,
            this will be an airfield name, such as "Wright-Patterson Air Force
            Base". However, it may also be the name of a region, such as "Boston
            Metropolitan Area" or "NAS Oceana and Associated Outlying Airfields".
        </para>
        <para>
            Use the <italic>Site Notes</italic> to store miscellaneous information
            about a site. There is no restriction on the length of notes.
            Press the <keytext>Enter</keytext> key to insert additional lines.
        </para>
    </section>
    <section id='BaseOps_NoiseModelsUsed_id'>
        <title>
            Noise Models
        </title>
        <exhibit>
            <img src='BaseOps_CaseChunk_NoiseModels_ScreenCap.png'/>
        </exhibit>
        <para>
            BaseOps supports the following noise models:
        </para>
        [-include "BaseOps_SupportedNoiseModelList.rxl"-]
        <para>
            Check the box next to each noise model that you wish to use as
            part of this BaseOps case. At least one model must be selected.
        </para>
        <para>
            When you <link target='#BaseOps_RunningCases_id'>run the case</link>,
            BaseOps runs each of the selected noise models. If more than one
            model is selected, BaseOps creates a combined noise grid containing
            the summed noise from all of the selected models.
        </para>
        <note type='note'>
            <para>
                BaseOps hides sections of the user interface that are not relevant
                to the selected noise models. For example, <link
                target='#BaseOps_TrainingProfileChunk_id'>airspace profiles</link>
                are only relevant to MRNMap. If you don't select the MRNMap noise
                model, then BaseOps hides the section of the user interface that
                allows airspace profiles to be edited.
            </para>
        </note>
    </section>
    <section id='BaseOps_CaseReferencePoint_id'>
        <title>
            Reference Point
        </title>
        <exhibit>
            <img src='BaseOps_CaseChunk_ReferencePoint_ScreenCap.png'/>
        </exhibit>
        <para>
            The reference point is a well-defined location associated with
            a BaseOps case. The latitude, longitude, and elevation of the
            reference point must be known, and the point should be easily
            identifiable on maps.
        </para>
        <para>
            The reference point serves as the origin of the local X-Y coordinate
            system used by the noise models. As such, it should be located
            near the center of the case's area of interest.
        </para>
        <note type='tip'>
            <para>
                The center of one end of a major runway is often a good reference
                point.
            </para>
        </note>
        <para>
            The reference point has the following properties.
        </para>
        <unorderedlist>
            <listitem>
                <para>
                    <italic>Reference Point Name</italic> - Type a short (60 characters
                    maximum) description of the reference point: for example, "Centerline,
                    Beginning of Runway 32".
                </para>
            </listitem>
            <listitem>
                <para>
                    <italic>Reference Point Lat/Long</italic> - Specify the horizontal
                    coordinates of the reference point, in degrees of latitude and
                    longitude, using the <link
                    target='#WCGIS_IntroductionToDatums_id'>WGS-84 datum</link>.
                </para>
                <note type='note'>
                    <para>
                        The reference point location must be specified using latitude
                        and longitude, regardless of the current <link
                        target='#BaseOps_CaseCoordinateSystem_id'>case coordinate system</link>.
                        This is because the case coordinate system can be defined in terms
                        of the reference point (for example, feet east and north of the
                        reference point). Thus, allowing the reference point to be specified
                        in the case coordinate system could cause a circular reference.
                    </para>
                </note>
            </listitem>
            <listitem>
                <para>
                    <italic>Reference Point Elevation</italic> - Type the elevation
                    (above mean sea level) of the ground at the site reference point.
                    See <iref target='BaseOps_CaseUnits_id'/> for information on selecting
                    the units used to specify elevations.
                </para>
                <para>
                    The reference point elevation is used to convert between AGL (above
                    ground level) and MSL (mean sea level) heights in a BaseOps case.
                    It is also used as the default ground elevation when NMap, AAM,
                    and RNM are run without <link
                    target='#BaseOps_ElevationAndImpedanceChunks_id'>elevation data</link>.
                </para>
            </listitem>
        </unorderedlist>
    </section>
    <section id='BaseOps_CaseChunk_Operations_id'>
        <title>
            Operations
        </title>
        <exhibit>
            <img src='BaseOps_CaseChunk_Operations_ScreenCap.png'/>
        </exhibit>
        <para>
            The <italic>Flying Days per Month</italic> and <italic>Annual
            Operating Days</italic> are the average number of days per month
            and year, respectively, on which aircraft typically operate at
            the principal airfield being modeled by the BaseOps case. For
            airfields that operate continuously, 30 days per month and 365
            days per year are typically used. The monthly average is used
            by the MRNMap noise model. The yearly average is used by NMap,
            AAM, AGM, and RNM. These data entry fields may be hidden, depending
            on which noise models you selected: see <iref
            target='BaseOps_NoiseModelsUsed_id'/>.
        </para>
        <para>
            The <italic>Number of Daily Periods</italic> specifies the number
            of periods into which a 24-hour day is partitioned for the purpose
            of noise modeling. This allows the noise models to give some consideration
            to the time at which noise events occur (events that occur at
            night are considered more significant, due to their greater potential
            to annoy).
        </para>
        <para>
            The number of daily periods is determined by the noise metric
            (DNL or CNEL) being used, which in turn is generally determined
            by the applicable laws governing the site being modeled.
        </para>
        <para>
            You have two choices for the number of daily periods.
        </para>
        <unorderedlist>
            <listitem>
                <para>
                    <italic>2 (day, night)</italic> - Two periods are used: day (for
                    aircraft operations between 0700 and 2200 hours local time) and
                    night (for operations before 0700 or after 2200 hours).
                </para>
            </listitem>
            <listitem>
                <para>
                    <italic>3 (day, evening, night)</italic> - Three periods are used:
                    day (for aircraft operations between 0700 and 1900 hours local
                    time), evening (for operations between 1900 and 2200 hours) and
                    night (for operations before 0700 or after 2200 hours).
                </para>
            </listitem>
        </unorderedlist>
    </section>
    <section>
        <title>
            Magnetic Declination
        </title>
        <exhibit>
            <img
            src='BaseOps_CaseChunk_MagneticDeclination_ScreenCap.png'/>
        </exhibit>
        <para>
            The <italic>Magnetic Declination</italic> is the difference between
            true and magnetic north at the location being modeled by a BaseOps
            case. It is specified in decimal degrees.
        </para>
        <para>
            The current magnetic declination is indicated by BaseOps' north
            arrow: see <iref target='WCGISxWCF_NorthArrowGlyph_id'/>.
        </para>
    </section>
    <section>
        <title>
            Contact Information
        </title>
        <exhibit>
            <img src='BaseOps_CaseChunk_ContactInformation_ScreenCap.png'/>
        </exhibit>
        <para>
            The requested contact information identifies the person or organization
            that is responsible for a BaseOps case. All of the information
            is typed as freeform text; there are no restrictions on what can
            be typed into each of the text boxes.
        </para>
    </section>
    <section id='BaseOps_FlightTrackAdvancedOptions_id'>
        <title>
            Flight Track Advanced Options
        </title>
        <exhibit>
            <img
            src='BaseOps_CaseChunk_FlightTrackAdvancedOptions_ScreenCap.png'/>
        </exhibit>
        <para>
            The Flight Track Advanced Options section pertains only to those
            noise model that use <link
            target='#BaseOps_FlightTrackChunk_id'>flight tracks</link>.
            This section is hidden unless one or more of those noise models
            is selected: see <iref target='BaseOps_NoiseModelsUsed_id'/>.
        </para>
        <para>
            Use the check box to select whether the optional Heading field is displayed
            when editing flight track segments. See <iref
            target='BaseOps_FlightTrackChunk_id'/> for more information
            about this field.
        </para>
    </section>
    <section id='BaseOps_FlightProfileAdvancedOptions_id'>
        <title>
            Flight Profile Advanced Options
        </title>
        <exhibit>
            <img
            src='BaseOps_CaseChunk_FlightProfileAdvancedOptions_ScreenCap.png'/>
        </exhibit>
        <para>
            The Flight Profile Advanced Options section pertains only to those
            noise model that use <link
            target='#BaseOps_FlightProfileChunk_id'>flight profiles</link>.
            This section is hidden unless one or more of those noise models
            is selected: see <iref target='BaseOps_NoiseModelsUsed_id'/>.
        </para>
        <para>
            Use the check boxes to select which optional fields are displayed
            when editing or viewing flight profile segment tables. See <iref
            target='BaseOps_FlightProfileChunk_Segments_id'/> for more information
            about these fields.
        </para>
    </section>
    <section id='BaseOps_AAMAdvancedOptions_id'>
        <title>
            AAM Advanced Options
        </title>
        <exhibit>
            <img src='BaseOps_CaseChunk_AAMAdvancedOptions_ScreenCap.png'/>
        </exhibit>
        <para>
            The AAM Advanced Options section pertains only to the AAM noise
            model. This section is hidden unless that noise model is selected:
            see <iref target='BaseOps_NoiseModelsUsed_id'/>.
        </para>
        <para>
            For non-helicopter AAM aircraft (such as the fixed-wing vectored
            thrust F-35 and the tilt-rotor V-22 Osprey), accurate values for
            the angle of attack and the yaw angle are difficult to obtain.
            Under realistic flying conditions, these values rarely depart
            significantly from zero, so by default, BaseOps assumes zero for
            these parameters, and hides the portions of the BaseOps user interface
            where these parameters are edited and/or displayed. Most uses
            should leave these parameters locked at zero.
        </para>
        <para>
            If you have specialized needs, you can check the box labeled <italic>Allow
            editing of attack and yaw angles for non-helicopter AAM aircraft</italic>.
            This will display the sections of the BaseOps user interface where
            these parameters can be edited.
        </para>
    </section>
</section>
