<p dir="ltr">I realized that coordinates copied directly from xml file are not recognized if  pasting them into coordinates input field.<br>
It doesn't like the lacking of N E references. Sadly google maps recognize them.<br></p>
<p dir="ltr">davide@mobile</p>
<div class="gmail_quote">Il 22/feb/2015 19:24 "Patrick Valsecchi" <<a href="mailto:patrick@thus.ch">patrick@thus.ch</a>> ha scritto:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
  
    
  
  <div text="#000000" bgcolor="#FFFFFF">
    On 22. 02. 15 17:52, Miika Turkia wrote:<br>
    <blockquote type="cite">
      
      <div dir="ltr">
        <div class="gmail_extra">
          <div class="gmail_quote">On Wed, Feb 4, 2015 at 11:28 AM,
            Patrick Valsecchi <span dir="ltr"><<a href="mailto:patrick@thus.ch" target="_blank">patrick@thus.ch</a>></span> wrote:<br>
            <blockquote class="gmail_quote"><span>On 02/03/2015
                04:41 PM, Dirk Hohndel wrote:<br>
                <blockquote class="gmail_quote">
                  On Tue, Feb 03, 2015 at 04:32:40PM +0100, Patrick
                  Valsecchi wrote:<br>
                  <blockquote class="gmail_quote">
                    Hi,<br>
                    <br>
                    This is a tentative to make subsurface a bit more
                    flexible when parsing GPS<br>
                    coordinates. I like to geo-reference my dives, but
                    copy and pasting the<br>
                    coordinates from web sites was quite a pain (needed
                    a lot of manual<br>
                    correction).<br>
                    <br>
                    Please have a look and comment. I'm quite tempted to
                    go wild and do another<br>
                    rewrite without using regular expressions... would
                    be more flexible and less<br>
                    code, IMHO.<br>
                  </blockquote>
                  Absolutely. By all means, please rewrite it without
                  regular expression if<br>
                  that makes it more flexible.<br>
                  <br>
                  Given where we are in the testing cycle, I won't apply
                  this fix to master.<br>
                  I'm hoping to cut 4.4 in the next day or two and
                  there's no way this will<br>
                  get enough testing.<br>
                </blockquote>
                <br>
              </span>
              OK, here is a total rewrite of the GPS coordinates parsing
              including UTs.<br>
              It is a lot more flexible on the format and supports all
              the formats of the previous parser (AFAIK).<br>
              <br>
              I share your opinion on not including it in 4.4.<br>
            </blockquote>
            <div><br>
            </div>
            <div>Do you care to work on the GPS parsing a bit more? We
              have some requests for more lax parsing on our user forum:<br>
              <br>
              <a href="https://groups.google.com/forum/#%21category-topic/subsurface-divelog/pMPlpNvhmfw" target="_blank">https://groups.google.com/forum/#!category-topic/subsurface-divelog/pMPlpNvhmfw</a><br>
              <br>
              E.g. 48 51.491n 2 17.677e<br>
            </div>
          </div>
        </div>
      </div>
    </blockquote>
    <br>
    No problem. I'll come up with a patch in the next days.<br>
  </div>

<br>_______________________________________________<br>
subsurface mailing list<br>
<a href="mailto:subsurface@subsurface-divelog.org">subsurface@subsurface-divelog.org</a><br>
<a href="http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface" target="_blank">http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface</a><br>
<br></blockquote></div>