
<section id='BaseOps_RunwayChunk_id'
webfilename='runwaychunk'>
    <title>
        Editing Runways
    </title>
    <para>
        Runways serve an important purpose in BaseOps: they are anchors
        for <link target='#BaseOps_FlightTrackChunk_id'>flight tracks</link>.
        The location and orientation of a flight track depends on the
        location and heading, respectively, of the track's runway.
    </para>
    <para>
        Runways are used by the NMap, AAM, and RNM noise models. Unless
        one of these models is selected, the parts of the BaseOps user
        interface dealing with runways will be hidden. See <iref
        target='BaseOps_NoiseModelsUsed_id'/>.
    </para>
    <para>
        To work with runways, choose Runways from the <link
        target='#BaseOps_ListPane_id'>object type selector dropdown list</link>.
        Runways can be added, duplicated, and deleted as described in
        <iref target='BaseOps_ListPane_id'/>.
    </para>
    <note type='tip'>
        <para>
            BaseOps can import runways from DAFIF. See <iref
            target='BaseOps_ImportingFromDAFIF_id'/>.
        </para>
    </note>
    <para>
        To edit a runway, 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_RunwayChunk_ScreenCap.png'/>
    </exhibit>
    <para>
        Runways have the following properties.
    </para>
    <unorderedlist>
        [-include "BaseOps_NameLongNameNotes_ListItems.rxl" ObjectTypeName='runway'-]
        <listitem>
            <para>
                <italic>Start Location</italic> -<linebreak/>
                <italic>End Location</italic> - The location of the runway centerline
                at the beginning and end of the runway, not counting any overrun
                areas.
            </para>
            <para>
                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 a runway endpoint
                to another location on the map. See <iref
                target='BaseOps_MouseTool_SelectAndEdit_id'/> for more information.
            </para>
            <note type='note'>
                <para>
                    Displaced runway thresholds are incorporated into flight profiles.
                    See the discussion of the <italic>displacement</italic> parameter
                    in <iref target='BaseOps_FlightProfileChunk_id'/>.
                </para>
            </note>
            <note type='important'>
                <para>
                    It is critical that runway locations be entered accurately and
                    with sufficient precision. Since a flight track's initial direction
                    is determined by its runway, a small error in the runway's heading
                    will result in substantial location errors in the portions of
                    the flight track that are far from the runway.
                </para>
            </note>
        </listitem>
        <listitem>
            <para>
                <italic>Start Elevation</italic> -<linebreak/>
                <italic>End Elevation</italic> - The elevations, with respect
                to mean sea level, of the runway centerline at the beginning and
                end of the runway, not counting any overrun areas.
            </para>
            <para>
                You can manually enter the elevations, or else choose to use the
                elevation of the case reference point: see <iref
                target='BaseOps_CaseReferencePoint_id'/>.
            </para>
            <para>
                You can change the units used to specify the elevations: see <iref
                target='BaseOps_CaseUnits_id'/>.
            </para>
        </listitem>
        <listitem>
            <para>
                <italic>Width</italic> - The width of the runway. The width is
                not used when calculating noise levels, but BaseOps uses it when
                drawing runways on maps.
            </para>
        </listitem>
        <listitem>
            <para>
                <italic>Length</italic> -<linebreak/>
                <italic>Heading</italic> - The length and heading of the runway,
                calculated from the endpoint locations.
            </para>
            <note type='tip'>
                <para>
                    You can double-check a runway's endpoints by comparing the calculated
                    length and heading with published values (from, say, a FLIP chart).
                </para>
            </note>
        </listitem>
    </unorderedlist>
    <para>
        Press the Reverse button to swap the runway endpoints and modify
        the runway name so that it refers to the opposite runway (for
        example, changing 23L to 05R). The name is not changed if it does
        not follow standard runway naming conventions (two digits referring
        to the heading, optionally followed by 'L', 'C', or 'R').
    </para>
    <note type='tip'>
        <para>
            After adding a runway, you can easily add the opposite runway
            to the BaseOps case by following these steps.
        </para>
        <orderedlist>
            <listitem>
                <para>
                    Press the Duplicate button <img
                    src='intres:BaseOps_DuplicateToolbarButtonBitmap'/> on the <link
                    target='#BaseOps_ListPane_id'>list pane</link> to create a copy
                    of the first runway.
                </para>
            </listitem>
            <listitem>
                <para>
                    Press the Reverse button to change the copy into the opposite
                    runway.
                </para>
            </listitem>
        </orderedlist>
    </note>
</section>
