
<section id='BaseOps_PointObjectChunks_id'
webfilename='pointobjects'>
    <title>
        Editing Point Objects
    </title>
    <para>
        Many of the objects in a <link
        target='#BaseOps_IntroductionToCases_id'>BaseOps case</link> represents
        point locations. These include:
    </para>
    <unorderedlist>
        <listitem>
            <para>
                <bold>Navigational Aids</bold> - Visual or electronic devices
                used to guide aircraft along their intended flight paths. Navigational
                aids serve as anchors for radials and DME arcs: see <iref
                target='BaseOps_RadialAndArcChunks_id'/>. They are also displayed
                on maps to aid in the editing of flight tracks and flight profiles:
                see <iref target='BaseOps_FlightTrackChunk_id'/> and <iref
                target='BaseOps_FlightProfileChunk_id'/>.
            </para>
        </listitem>
        <listitem>
            <para>
                <bold>Waypoints</bold> - Named geographic reference points used
                by aircraft in navigating their routes. Since flight paths are
                often specified with respect to waypoints, it can be useful to
                display waypoints on maps when editing flight tracks and flight
                profiles: see <iref target='BaseOps_FlightTrackChunk_id'/> and
                <iref target='BaseOps_FlightProfileChunk_id'/>.
            </para>
        </listitem>
        <listitem>
            <para>
                <bold>Points of Interest</bold> - Locations of special interest
                where a detailed noise analysis will be performed. Typically,
                these are locations with a heightened sensitivity to noise, such
                as hospitals and schools. See <iref
                target='BaseOps_RunChunk_ComputationsPerformed_id'/>.
            </para>
        </listitem>
        <listitem>
            <para>
                <bold>VTOL Pads</bold> - Locations where vertical-takeoff-and-landing
                (VTOL) aircraft can takeoff and land. VTOL pads (also known as
                helipads) are often used as the anchors for flight tracks: see
                <iref target='BaseOps_FlightTrackChunk_id'/>. VTOL pads are used
                by the AAM and RNM noise model.
            </para>
        </listitem>
        <listitem>
            <para>
                <bold>Static Pads</bold> - Designated locations on an airfield
                where aircraft engines are run during maintenance and repair work.
                Static pads serve as the anchors for static profiles: see <iref
                target='BaseOps_StaticProfileChunk_id'/>. Static pads are used
                by the NMap and AAM noise models.
            </para>
        </listitem>
        <listitem>
            <para>
                <bold>Targets</bold> - Locations at which airborne gunnery
                fire is directed. Targets serve as anchors for AGM attack runs:
                see <iref target='BaseOps_AttackRunChunk_id'/>.
            </para>
        </listitem>
    </unorderedlist>
    <note type='tip'>
        <para>
            BaseOps can import waypoints, navigational aids, and VTOL pads
            from DAFIF. See <iref target='BaseOps_ImportingFromDAFIF_id'/>.
        </para>
    </note>
    <para>
        The different types of point objects are all edited in a similar
        manner. Therefore, only navigational aids will be discussed in
        detail. Keep in mind, however, that the following instructions
        (with the exception of the navaid type) also apply to other point
        objects.
    </para>
    <para>
        To work with navigational aids, choose Navigational Aids from
        the <link target='#BaseOps_ListPane_id'>object type selector dropdown
        list</link>. Navigational aids can be added, duplicated, and deleted
        as described in <iref target='BaseOps_ListPane_id'/>. You can
        use the Add mouse tool <img
        src='intres:BaseOps_AddTool_ToolbarButton'/> to add new navigational
        aids by clicking on the map; see <iref
        target='BaseOps_MouseTool_Add_id'/>.
    </para>
    <para>
        To edit a navigational aid, first select it in the <link
        target='#BaseOps_ListPane_id'>object list</link>, then edit its
        properties in the <link
        target='#WCF_ApplicationMainWindow_id'>text pane</link>.
    </para>
    <exhibit>
        <img src='BaseOps_NavigationalAidChunk_ScreenCap.png'/>
    </exhibit>
    <para>
        Navigational aids have the following properties.
    </para>
    <unorderedlist>
        [-include "BaseOps_NameLongNameNotes_ListItems.rxl" ObjectTypeName='navigational aid'-]
        <listitem>
            <para>
                <italic>Location</italic> - The location of the navigational aid.
                You can change the coordinate system used to specify locations:
                see <iref target='BaseOps_CaseCoordinateSystem_id'/>.
            </para>
            <para>
                Using the Select and Edit map tool, you can drag the navigational
                aid to another location on the map. See <iref
                target='BaseOps_MouseTool_SelectAndEdit_id'/> for more information.
            </para>
        </listitem>
        <listitem>
            <para>
                <italic>NavAid Type</italic> - The type (VOR, TACAN, DME, etc.)
                of the navigational aid. Specifying the type is not strictly necessary.
                However, doing so is useful for documentation purposes, and future
                versions of BaseOps may allow you to display different types of
                navigational aids using different map symbols.
            </para>
            <para>
                The navigational aid types are defined in the NavAid Type group:
                see <iref target='BaseOps_GroupChunk_id'/>. If desired, you can
                add additional types.
            </para>
        </listitem>
    </unorderedlist>
    <note type='note'>
        <para>
            If the AAM and/or the NMap noise models are selected, Points of
            Interest will have two additional properties: the noise level
            reductions when windows are open and closed. These properties
            are used when calculating the Probability of Awakening noise metric.
            Suggested default values are 15 dB for windows open and 25 dB
            for windows closed, which correspond to national averages for
            residential construction per FICAN 1992.
        </para>
    </note>
</section>
