Re: [Gpsbabel-misc] solmeta file conversion

[Robert L. <rob...@gp...>]

Thank you for providing enough information for us to reproduce your case.

Your file is almost like a NMEA file, only Every Single Line has an
incorrect checksum.  Whatever created this file went to all the effort to
include a checksum (it's like a magic square: I say "there are numbers one
two five and the sum is eight" you know you got all the data correctly and
that a burst of noise on the phone call didn't make you miss a number or
add a number. This mattered a lot in the serial days and matters now on
things like data loggers and messed up SD cards.

The thing is, if someone goes to the effort to put in a checksum, we're
going to use it and trust it. So we throw away every line of your output.
GPSBabel, however, honors the case where there is NO checksum. If we edit
your file to remove the *XX (where XX is a two digit number) from the end
of every line (If you're a vi user, that's :%s/\*..$//, but the basic trick
can be done with about any text editor.) we read that file just fine.

<?xml version="1.0" encoding="UTF-8"?>
<gpx version="1.0" creator="GPSBabel - http://www.gpsbabel.org" xmlns="
http://www.topografix.com/GPX/1/0">
  <time>2017-04-05T03:53:59.316Z</time>
  <bounds minlat="31.227040333" minlon="-81.536043333"
maxlat="31.227210333" maxlon="-81.535815500"/>
  <trk>
    <trkseg>
      <trkpt lat="31.227155333" lon="-81.536043333">
        <time>2017-04-05T00:25:03Z</time>
        <course>106.580002</course>
        <speed>0.000000</speed>
      </trkpt>
      <trkpt lat="31.227155333" lon="-81.536043333">
        <ele>19.200000</ele>
        <time>2017-04-05T00:25:13Z</time>
        <course>126.849998</course>
        <speed>0.000000</speed>
        <geoidheight>-31.7</geoidheight>


You really should contact whomever makes a Solmeta and tell them to read
https://en.wikipedia.org/wiki/NMEA_0183 and search for the word "checksum"
- they even include example code to do it right and checksum checkers and
calculators are plentify. (Hint: the "83" part of that is "1983" - this
isn't exactly hard to get right.

Interestingly, I see that "According to the official specification, the
checksum is optional for most data sentences, but is compulsory for RMA,
RMB, and RMC (among others)." - in the spirit of Postel's Law of being
liberal with what we receive, we actually treat it optional everywhere -
but if you have it, it has to be _right_.


As a side note, what do you have that uses Delorme GPL? That's a format
that I thought we could drop years ago, but haven't just because that wheel
hasn't squeaked.



On Tue, Apr 4, 2017 at 10:26 PM, <sta...@co...> wrote:

>
>    heres my setup for the conversion.
>
>
> [image: image]
>
> *From:* sta...@co...
> *Sent:* Tuesday, April 04, 2017 9:59 PM
> *To:* gps...@li...
> *Cc:* sta...@co...
> *Subject:* solmeta file conversion
>
> good evening all,
>    i have not posted in several years, i’m trying to do it right....
>    i have recently purchased a solmeta gmax eos gps and can not get any of
> its log files to convert.
>    i would appreciate any comments you might have.
>    the log file is attached.
>    i am using version 1.5.3 on a windows 7 home premium version 6.1 build
> 7601 service pack 1 machine.
>    i have been using gpsbabel for many years converting gpx to delorme
> gpl, mostly, with no problems.
>
> thanks,
> bill
>
>
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Gpsbabel-misc mailing list http://www.gpsbabel.org
> Gps...@li...
> To unsubscribe, change list options, or see archives, visit:
> https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc
>
>