<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p>Hi,</p>
    <p>I have add a  google drive link to the world MGRS. This should
      help.<br>
    </p>
    <p><a class="moz-txt-link-freetext" href="https://drive.google.com/file/d/1HeTOUCHrOF4dqLXyebO33nUwioYGnGbI/view?usp=sharing">https://drive.google.com/file/d/1HeTOUCHrOF4dqLXyebO33nUwioYGnGbI/view?usp=sharing</a></p>
    <p>Nicolas<br>
    </p>
    <div class="moz-cite-prefix">On 2021-02-08 9:34 a.m., C Hamilton
      wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CABPxTTqWkLLEzq_oMgj0-oKOfhFrJ=VnssjEF89+8Ujts+TWbQ@mail.gmail.com">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <div dir="ltr">I should have jumped in on this conversation over
        the weekend especially since I am the author of Lat Lon Tools.
        but all who responded have properly addressed the problems with
        UTM and especially with how MGRS got mixed in with UTM and the
        confusion with N & S. What Lat Lon Tools provides is the
        standard UTM coordinates without the MGRS latitude bands. I have
        been considering adding another function that provides the
        alternative UTM with MGRS latitude bands.
        <div><br>
        </div>
        <div>If anyone has any suggestions on the best way to present
          these two different UTM versions that helps to avoid
          ambiguity, please let me know.</div>
        <div><br>
        </div>
        <div>Thanks,</div>
        <div><br>
        </div>
        <div>Calvin</div>
      </div>
      <br>
      <div class="gmail_quote">
        <div dir="ltr" class="gmail_attr">On Sat, Feb 6, 2021 at 2:19 PM
          Eric Sorensen <<a href="mailto:e.b.s@me.com"
            moz-do-not-send="true">e.b.s@me.com</a>> wrote:<br>
        </div>
        <blockquote class="gmail_quote" style="margin:0px 0px 0px
          0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
          <div style="overflow-wrap: break-word;">As Greg and others
            point out, I appear to be using the UTM zone term
            inappropriately.  My apologies.
            <div><br>
            </div>
            <div>What I am after in my label, is the MGRS flavor that
              includes the latitude band, and agrees with the image
              shown in this link;</div>
            <div><br>
            </div>
            <div><a
                href="https://docs.qgis.org/3.4/en/_images/utm_zones.png"
                target="_blank" moz-do-not-send="true">https://docs.qgis.org/3.4/en/_images/utm_zones.png</a></div>
            <div><br>
            </div>
            <div>After you folks successfully educated me on this, I
              came up with the following;</div>
            <div><br>
            </div>
            <div>concat(name, ', ',  mgrs_gzd($Y, $X), ' ',  
              format_number(utm_east( $Y, $X), 0), ' ',
               format_number(utm_north( $Y, $X), 0))</div>
            <div><br>
            </div>
            <div>Which gets me a label like this for the point I
              originally supplied;</div>
            <div>Park, 13S 384,258 3,974,547</div>
            <div><br>
            </div>
            <div>This is how my Garmin GPS displays coordinates of
              waypoints (sans the commas), and how someone would input
              the point into their gps, after I hand them a map I have
              created in QGIS.  Now to eliminate the commas.</div>
            <div><br>
            </div>
            <div>Thank you all for your input,</div>
            <div>es</div>
            <div><br>
              <div><br>
                <blockquote type="cite">
                  <div>On Feb 6, 2021, at 11:41 AM, Greg Troxel <<a
                      href="mailto:gdt@lexort.com" target="_blank"
                      moz-do-not-send="true">gdt@lexort.com</a>>
                    wrote:</div>
                  <br>
                  <div>
                    <div><br>
                      Eric Sorensen <<a href="mailto:e.b.s@me.com"
                        target="_blank" moz-do-not-send="true">e.b.s@me.com</a>>
                      writes:<br>
                      <br>
                      <blockquote type="cite">  <wpt
                        lat="35.908381976187229"
                        lon="-106.282681999728084"><br>
                           <ele>2262.188964999999826</ele><br>
                      </blockquote>
                      <br>
                      <blockquote type="cite">The labels appear as
                        expected, except one small problem.  I know the
                        points are in UTM zone 13S, yet the label shows
                        zone 13N.<br>
                        <br>
                        Any thoughts on what I am doing wrong.<br>
                      </blockquote>
                      <br>
                      That latitude is north, and in New Mexico.  Why do
                      you think it's zone<br>
                      13S?<br>
                      <br>
                      <pause to read><br>
                      <br>
                      Beware of the confusion between grid zones from
                      MGRS, not technically<br>
                      part of UTM, and UTM north/south.  See<br>
                      <br>
                       <a
href="https://en.wikipedia.org/wiki/Universal_Transverse_Mercator_coordinate_system#Notation"
                        target="_blank" moz-do-not-send="true">https://en.wikipedia.org/wiki/Universal_Transverse_Mercator_coordinate_system#Notation</a><br>
                      <br>
                      So it seems the UTM output uses S and N -- which
                      is what I would expect<br>
                      for straight UTM without a MGRS flavor.<br>
                      <br>
                      If you moved north, you could be in 13T, from
                      40-48 degrees, and not<br>
                      have this issue, but then you'd have more snow :-)<br>
                      <br>
                    </div>
                  </div>
                </blockquote>
              </div>
              <br>
            </div>
          </div>
          _______________________________________________<br>
          Qgis-user mailing list<br>
          <a href="mailto:Qgis-user@lists.osgeo.org" target="_blank"
            moz-do-not-send="true">Qgis-user@lists.osgeo.org</a><br>
          List info: <a
            href="https://lists.osgeo.org/mailman/listinfo/qgis-user"
            rel="noreferrer" target="_blank" moz-do-not-send="true">https://lists.osgeo.org/mailman/listinfo/qgis-user</a><br>
          Unsubscribe: <a
            href="https://lists.osgeo.org/mailman/listinfo/qgis-user"
            rel="noreferrer" target="_blank" moz-do-not-send="true">https://lists.osgeo.org/mailman/listinfo/qgis-user</a><br>
        </blockquote>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <pre class="moz-quote-pre" wrap="">_______________________________________________
Qgis-user mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Qgis-user@lists.osgeo.org">Qgis-user@lists.osgeo.org</a>
List info: <a class="moz-txt-link-freetext" href="https://lists.osgeo.org/mailman/listinfo/qgis-user">https://lists.osgeo.org/mailman/listinfo/qgis-user</a>
Unsubscribe: <a class="moz-txt-link-freetext" href="https://lists.osgeo.org/mailman/listinfo/qgis-user">https://lists.osgeo.org/mailman/listinfo/qgis-user</a>
</pre>
    </blockquote>
    <pre class="moz-signature" cols="72">-- 
Nicolas Cadieux
<a class="moz-txt-link-freetext" href="https://gitlab.com/njacadieux">https://gitlab.com/njacadieux</a></pre>
  </body>
</html>