
<section id='BaseOps_MilitaryTrainingRouteChunk_id'
webfilename='militarytrainingroutechunk'>
    <title>
        Editing Military Training Routes
    </title>
    <para>
        A military training route (MTR) is a long, relatively narrow volume
        of airspace that aircraft operate in when traveling between two
        locations. Horizontally, an MTR is defined by a series of line
        segments denoting the centerline of the MTR, along with a width
        that can vary with location along the MTR centerline. Vertically,
        an MTR is defined by a floor height.
    </para>
    <para>
        In BaseOps, an MTR is defined by 2 or more <termtext>segment points</termtext>.
        Each adjacent pair of segment points defines one straight segment
        of the MTR.
    </para>
    <exhibit>
        <img src='BaseOps_MilitaryTrainingRoute_Figure.png'
        standard_colors='true'/>
    </exhibit>
    <para>
        MTRs are used by the MRNMap noise model. Unless that model is
        selected, the parts of the BaseOps user interface dealing with
        MTRs will be hidden. See <iref
        target='BaseOps_NoiseModelsUsed_id'/>.
    </para>
    <para>
        To work with MTRs, choose Military Training Routes from the <link
        target='#BaseOps_ListPane_id'>object type selector dropdown list</link>.
        MTRs can be added, duplicated, and deleted as described in <iref
        target='BaseOps_ListPane_id'/>.
    </para>
    <note type='tip'>
        <para>
            BaseOps can import MTRs from DAFIF. See <iref
            target='BaseOps_ImportingFromDAFIF_id'/>.
        </para>
    </note>
    <para>
        To edit an MTR, 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_MilitaryTrainingRouteChunk_TextPane_ScreenCap.png'/>
    </exhibit>
    <para>
        MTRs have the following properties.
    </para>
    <unorderedlist>
        [-include "BaseOps_NameLongNameNotes_ListItems.rxl" ObjectTypeName='MTR'-]
        <listitem>
            <para>
                <italic>Length</italic> - The length of the MTR's centerline.
                The length is automatically updated as you edit the MTR.
            </para>
            <para>
                You can change the units used to specify the length: see <iref
                target='BaseOps_CaseUnits_id'/>.
            </para>
        </listitem>
        <listitem>
            <para>
                <italic>Segment Points</italic> - An MTR's segments are specified
                using a table, where each table row represents a segment point.
                An MTR must consist of at least one segment, so a minimum of two
                segment points must be supplied.
            </para>
            <para>
                The following table columns are defined.
            </para>
            <unorderedlist>
                <listitem>
                    <para>
                        <italic>Coordinates</italic> - The geographic location of this
                        segment point.
                    </para>
                    <para>
                        Zero-length segments are not allowed: i.e., adjacent segment points
                        in the table must not have the same coordinates.
                    </para>
                    <para>
                        You can change the coordinate system used to specify locations:
                        see <iref target='BaseOps_CaseCoordinateSystem_id'/>.
                    </para>
                </listitem>
                <listitem>
                    <para>
                        <italic>Turn Radius</italic> - The radius of the turn to the next
                        segment point. It is not unusual for MTR turn radiuses to be zero,
                        and for an MTR to contain a mixture of both zero-radius and non-zero-radius
                        turns.
                    </para>
                    <para>
                        The turn begins at the location specified in the Coordinates column.
                        The angle of the turn is automatically calculated based upon the
                        coordinates of the next segment point.
                    </para>
                    <para>
                        You can change the units used to specify MTR turn radiuses: see
                        <iref target='BaseOps_CaseUnits_id'/>.
                    </para>
                </listitem>
                <listitem>
                    <para>
                        <italic>Left Width<linebreak/>
                         Right Width</italic> - The width of the MTR to the left and right
                        of the MTR's centerline. Left and right are interpreted from the
                        perspective of the pilot of an aircraft that is flying along the
                        MTR from beginning to end. Zero widths are allowed.
                    </para>
                    <para>
                        You can change the units used to specify MTR widths: see <iref
                        target='BaseOps_CaseUnits_id'/>.
                    </para>
                    <!-- <note type='important'>
                        <para>
                            The current version of MRNMap does not support segments that have
                            different left and right widths. It is expected that in the future,
                            a version of MRNMap without this limitation will become available.
                        </para>
                    </note> -->
                </listitem>
                <listitem>
                    <para>
                        <italic>Width Variation</italic> - How the MTR width varies along
                        the segment. If the variation is <italic>constant</italic>, then
                        the width is constant along the entire segment. If the variation
                        is <italic>linear</italic>, then the width varies linearly with
                        distance along the segment centerline; at the end of the segment,
                        the width is equal to the width specified by the next segment
                        point.
                    </para>
                    <para>
                        The width variation is ignored in the last row of the table.
                    </para>
                    <!--<note type='important'>
                        <para>
                            The current version of MRNMap ignores the width variation settings
                            in the MRNMap input file, and treats all segments as if their
                            width variation is constant. It is expected that in the future,
                            a version of MRNMap without this limitation will become available.
                        </para>
                    </note>-->
                </listitem>
                <listitem>
                    <para>
                        <italic>Floor<linebreak/>
                         Turn Exit Floor</italic> - The floor is the minimum allowed flight
                        level for an MTR segment. [-include "BaseOps_HeightInputControl_UsageSentence.txt"-]
                    </para>
                    <para>
                        For turns with non-zero radius, the floor descends to the turn
                        exit floor linearly through the turn. The turn exit floor is then
                        used for the remainder of this segment, up until the next segment
                        point.
                    </para>
                    <para>
                        For turns with zero radius, the turn exit floor is not applicable.
                    </para>
                    <para>
                        You can change the units used to specify heights: see <iref
                        target='BaseOps_CaseUnits_id'/>.
                    </para>
                </listitem>
                <!--
                    <listitem>
                        <para>
                            <italic>Floor Variation</italic> - How the MTR floor varies along
                            the segment. If the variation is <italic>constant</italic>, then
                            the floor is constant along the entire segment. If the variation
                            is <italic>linear</italic>, then the floor varies linearly with
                            distance along the segment centerline; at the end of the segment,
                            the floor is equal to the floor specified by the next segment
                            point.
                        </para>
                        <para>
                            The floor variation is ignored in the last row of the table.
                        </para>
                    </listitem>
                 -->
                <listitem>
                    <para>
                        <italic>Notes</italic> - Miscellaneous information about this
                        MTR segment. There is no restriction on the text that can be typed
                        into this box. The notes are not used by the noise models; they
                        are for your use to record any information you believe is relevant.
                    </para>
                </listitem>
            </unorderedlist>
            <para>
                In the segment points table, the triangle icon <img
                src='intres:BaseOps_RowSelectionIcon_Selected_CroppedForDocumentation'/>
                indicates the selected segment point. To select another point,
                either click somewhere on that point's row, or navigate to that
                point using the <keytext>Tab</keytext> key. Alternatively, click
                on that point on the map using the <link
                target='#BaseOps_MouseTool_SelectAndEdit_id'>Select and Edit mouse
                tool</link>&nbsp;<img
                src='intres:WCF_ArrowMouseCursorToolbarButtonBitmap'/>.
            </para>
            <para>
                To add a new segment point, either press the Add New Point button
                <img src='intres:BaseOps_AddPlusSignSmallButtonBitmap'/>, or press
                <keytext>Ctrl + A</keytext>. Alternatively, use the <link
                target='#BaseOps_MouseTool_Add_id'>Add mouse tool</link>&nbsp;<img
                src='intres:BaseOps_AddTool_ToolbarButton'/> to add new points
                by clicking on the map. New points are added to the MTR after
                the selected point.
            </para>
            <note type='tip'>
                <para>
                    When editing MTRs on the map, you will often find yourself switching
                    back and forth between using the Select and Edit and the Add mouse
                    tools. As a convenience in such situations, hold down the <keytext>Ctrl</keytext>
                    key to make the Add mouse tool temporarily act like the Select
                    and Edit mouse tool, and vice versa.
                </para>
            </note>
            <para>
                When you add a new segment point, BaseOps duplicates the selected
                point. If desired, you can use the quick-add feature, which lets
                you efficiently add a segment point while simultaneously specifying
                its properties. To add a point, type a quick-add command into
                the text box, then press the Add New Point button <img
                src='intres:BaseOps_AddPlusSignSmallButtonBitmap'/> or the <keytext>Enter</keytext>
                key.
            </para>
            <para>
                The quick-add commands are somewhat cryptic, but once learned,
                they allow you to add segment points very quickly. Frequent users
                will find it worthwhile spending a few minutes learning the quick-add
                commands. To display a list of the quick-add commands that you
                can use, either press the Quick-Add Hints button <img
                src='intres:BaseOps_QuickAddSmallButtonBitmap'/>, or press <keytext>Ctrl
                + H</keytext>.
            </para>
            <para>
                To delete the selected segment point, either press the Delete
                Point button <img
                src='intres:WCF_DeleteCrossToolbarButtonBitmap'/>, or press <keytext>Ctrl
                + Del</keytext>.
            </para>
            <para>
                To move the selected point up or down in the table, press the
                Move Up and Move Down buttons <img
                src='intres:WCF_MoveUpToolbarButtonBitmap'/> and <img
                src='intres:WCF_MoveDownToolbarButtonBitmap'/>, or press <keytext>Ctrl
                + U</keytext> and <keytext>Ctrl + D</keytext>.
            </para>
        [-include "BaseOps_CopyPasteSegments.rxl" segment_name_lowercase='segment point' segment_name_uppercase='Segment Point' object_name='MTR'-]
            <note type='tip'>
                <para>
                    Using the Select and Edit map tool, you can graphically edit a
                    MTR's segments. See <iref
                    target='BaseOps_MouseTool_SelectAndEdit_id'/> for more information.
                </para>
            </note>
            <para>
                When you are editing an MTR, BaseOps marks the segment points
                on the map. This makes it easier to edit the MTR using the mouse
                tools.
            </para>
            <exhibit>
                <img
                src='BaseOps_MilitaryTrainingRouteChunk_MapPane_PointsHighlighted_ScreenCap.png'/>
            </exhibit>
            <para>
                The upper-right segment point, highlighted in yellow, is the selected
                point.
            </para>
        </listitem>
    </unorderedlist>
</section>
