GPSBabel

On Sat, Jun 1, 2013 at 6:14 PM, Claudius <gpsbabel.list@...> wrote:

> Hi everyone,
>
> i did not find a bugtracker or any mention of one. So i'm trying this
> one here. Maybe i'm just doing something wrong.
>

Doubtful this is pilot error.



>
> Today i created a bunch of tracklogs with a Wintec 202 (tes-files). For
> the first time, i actually cared about the altitude information. Usually
> i'm just clamping the tracks to the ground.
>
> I did two conversions (one to GPX, one to KML using GPSbabel 1.4.4), and
> in both, the altitudes were far off. Not only were they off, they were
> actually the wrong way round?
>
> Actual height profile from Google Earth:
> http://temp.amenthes.de/gpsbabel/tes_actual_height.png
>
> Recorded height from Wintec, converted to KML:
> http://temp.amenthes.de/gpsbabel/tes_recorded_height.png
>
> The track starts in the upper left corner. I was riding a bus, wich went
> downhill. So i'm pretty certain that the Google Earth profile from the
> first image is more or less correct.
>
> If anyone cares to take a look, here's my original recording as well:
> http://temp.amenthes.de/gpsbabel/08_08_26.TES
> And the conversion being displayed on Google Earth in the screenshot:
> http://temp.amenthes.de/gpsbabel/08_08_26.TES.kml


The Wintec TES file format was reverse engineered about 3 years ago.  The
code treats the two bytes after longitude as altitude in meters and I don't
think anyone before you has challenged that, though there are conflicting
comments in the code on how well altitude was actually understood.

I don't have one of those units so I don't know if the alt is barometeric
(notoriously inaccurate in some cases) or GPS derived or if it's using
internal tables to correct to the geoid or what.  You can see the code that
reads these as
https://code.google.com/p/gpsbabel/source/browse/trunk/gpsbabel/wintec_tes.cc#68
(You can see the comments that say we don't know what the units are,
but
then say that it's meters...and that we ignore negative values, but we're
putting it in an unsigned value.)

If you have a better understanding as to what those two bytes actually
represent - if they're altitude at all - whether you find it empirically,
via the source of other free software, or via specs obtained from Wintec
and can help us improve that, that'd be great.

Am 02.06.2013 05:16, schrieb Robert Lipe:
> The Wintec TES file format was reverse engineered about 3 years ago.
>  The code treats the two bytes after longitude as altitude in meters and
> I don't think anyone before you has challenged that, though there are
> conflicting comments in the code on how well altitude was actually
> understood.
> 
> I don't have one of those units so I don't know if the alt is
> barometeric (notoriously inaccurate in some cases) or GPS derived or if
> it's using internal tables to correct to the geoid or what.

It's a GPS-only unit, i guess they derive the altitude from that. If
they do any kind of correction from tables is beyond my knowledge.

> You can see the code that reads these
> as https://code.google.com/p/gpsbabel/source/browse/trunk/gpsbabel/wintec_tes.cc#68
>  (You can see the comments that say we don't know what the units are,
> but then say that it's meters...and that we ignore negative values, but
> we're putting it in an unsigned value.)

Thanks for the pointer! I'll experiment with it.

> If you have a better understanding as to what those two bytes actually
> represent - if they're altitude at all - whether you find it
> empirically, via the source of other free software, or via specs
> obtained from Wintec and can help us improve that, that'd be great.

>From the comparison between Google earth and my own conversion, i'd say
the bytes are definitely correlated to altitude. I gathered a lot of
interesting profiles, so i should be able to math the expected and the
actual values more closely.

Best wishes
Claudius

You're trying to do something more than download and convert to GPX, but
you didn't say *what*.  That message is coming from the track filter, so
you're doing some additional filtering on it that you did not describe.
 You're attempting to perform some operation on track data that requires
time to move forward, but as you see from the error, you have a trackpoint
with a timestamp ending in ...10s that appears before ....08s.




On Thu, May 30, 2013 at 11:01 AM, Oates, Julie <Julie.Oates@...:

> I am trying to download tracks from a GlobalSAT DG-100 data logger to the
> GPX XML format and get the following error:****
>
> ** **
>
> trackfilter-init: Track points badly ordered (timestamp
> 2013-05-21T21:06:10Z > 2013-05-21T21:06:08Z)!****
>
> Error running gpsbabel: Process exited unsucessfully with code 1****
>
> ** **
>
> Does anyone know how to fix this?  ****
>
> ** **
>
> Thanks!  ****
>
> ** **
>
> Julie****
>
> ______________________________________________________________________
> Attention:
> This e-mail and any files transmitted with it from Hatch Mott MacDonald
> are confidential and intended solely for use of the individual or entity to
> whom they are addressed. If you have received this e-mail in error please
> immediately notify the sender.
> ______________________________________________________________________
>
>
> ------------------------------------------------------------------------------
> Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET
> Get 100% visibility into your production application - at no cost.
> Code-level diagnostics for performance bottlenecks with <2% overhead
> Download for free and get started troubleshooting in minutes.
> http://p.sf.net/sfu/appdyn_d2d_ap1
> _______________________________________________
> Gpsbabel-misc mailing list http://www.gpsbabel.org
> Gpsbabel-misc@...
> To unsubscribe, change list options, or see archives, visit:
> https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc
>
>

Yes, I did have the "Speed" and "Course" boxes checked in the Track Filters.  Apparently that wasn't necessary.  I unchecked them and ran it again and it worked fine.  Thank you so much for your help!

Julie

From: robertlipe@... [mailto:robertlipe@...] On Behalf Of Robert Lipe
Sent: Thursday, May 30, 2013 10:06 AM
To: Oates, Julie
Cc: gpsbabel-misc@...
Subject: Re: [Gpsbabel-misc] trackfilter-init: Track points badly ordered

You're trying to do something more than download and convert to GPX, but you didn't say *what*.  That message is coming from the track filter, so you're doing some additional filtering on it that you did not describe.  You're attempting to perform some operation on track data that requires time to move forward, but as you see from the error, you have a trackpoint with a timestamp ending in ...10s that appears before ....08s.



On Thu, May 30, 2013 at 11:01 AM, Oates, Julie <Julie.Oates@...>> wrote:
I am trying to download tracks from a GlobalSAT DG-100 data logger to the GPX XML format and get the following error:


trackfilter-init: Track points badly ordered (timestamp 2013-05-21T21:06:10Z > 2013-05-21T21:06:08Z)!

Error running gpsbabel: Process exited unsucessfully with code 1

Does anyone know how to fix this?

Thanks!

Julie

______________________________________________________________________
Attention:
This e-mail and any files transmitted with it from Hatch Mott MacDonald are confidential and intended solely for use of the individual or entity to whom they are addressed. If you have received this e-mail in error please immediately notify the sender.
______________________________________________________________________

------------------------------------------------------------------------------
Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET
Get 100% visibility into your production application - at no cost.
Code-level diagnostics for performance bottlenecks with <2% overhead
Download for free and get started troubleshooting in minutes.
http://p.sf.net/sfu/appdyn_d2d_ap1
_______________________________________________
Gpsbabel-misc mailing list http://www.gpsbabel.org
Gpsbabel-misc@...>
To unsubscribe, change list options, or see archives, visit:
https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc


______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________

______________________________________________________________________
Attention:
This e-mail and any files transmitted with it from Hatch Mott MacDonald are confidential and intended solely for use of the individual or entity to whom they are addressed. If you have received this e-mail in error please immediately notify the sender.
______________________________________________________________________

speed relies on time moving forward. (Think about the math...)  If your GPS
really is creating successive positions with non-linear times, you should
probably file a bug report with GlobalSAT on that.

Enjoy.
RJL

If you find GPSBabel useful, especially if a feature was added or fixed for
you, please consider supporting its development at
http://www.gpsbabel.org/contribute.html




On Thu, May 30, 2013 at 12:47 PM, Oates, Julie <Julie.Oates@...:

> Yes, I did have the “Speed” and “Course” boxes checked in the Track
> Filters.  Apparently that wasn’t necessary.  I unchecked them and ran it
> again and it worked fine.  Thank you so much for your help!****
>
> ** **
>
> Julie  ****
>
> ** **
>
> *From:* robertlipe@... [mailto:robertlipe@...] *On Behalf Of *Robert
> Lipe
> *Sent:* Thursday, May 30, 2013 10:06 AM
> *To:* Oates, Julie
> *Cc:* gpsbabel-misc@...
> *Subject:* Re: [Gpsbabel-misc] trackfilter-init: Track points badly
> ordered****
>
> ** **
>
> You're trying to do something more than download and convert to GPX, but
> you didn't say *what*.  That message is coming from the track filter, so
> you're doing some additional filtering on it that you did not describe.
>  You're attempting to perform some operation on track data that requires
> time to move forward, but as you see from the error, you have a trackpoint
> with a timestamp ending in ...10s that appears before ....08s.****
>
> ** **
>
> ** **
>
> ** **
>
> On Thu, May 30, 2013 at 11:01 AM, Oates, Julie <Julie.Oates@...>
> wrote:****
>
> I am trying to download tracks from a GlobalSAT DG-100 data logger to the
> GPX XML format and get the following error:****
>
>  ****
>
> trackfilter-init: Track points badly ordered (timestamp
> 2013-05-21T21:06:10Z > 2013-05-21T21:06:08Z)!****
>
> Error running gpsbabel: Process exited unsucessfully with code 1****
>
>  ****
>
> Does anyone know how to fix this?  ****
>
>  ****
>
> Thanks!  ****
>
>  ****
>
> Julie****
>
>
> ______________________________________________________________________
> Attention:
> This e-mail and any files transmitted with it from Hatch Mott MacDonald
> are confidential and intended solely for use of the individual or entity to
> whom they are addressed. If you have received this e-mail in error please
> immediately notify the sender.
> ______________________________________________________________________****
>
>
>
> ------------------------------------------------------------------------------
> Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET
> Get 100% visibility into your production application - at no cost.
> Code-level diagnostics for performance bottlenecks with <2% overhead
> Download for free and get started troubleshooting in minutes.
> http://p.sf.net/sfu/appdyn_d2d_ap1
> _______________________________________________
> Gpsbabel-misc mailing list http://www.gpsbabel.org
> Gpsbabel-misc@...
> To unsubscribe, change list options, or see archives, visit:
> https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc****
>
> ** **
>
>
> ______________________________________________________________________
> This email has been scanned by the Symantec Email Security.cloud service.
> For more information please visit http://www.symanteccloud.com
> ______________________________________________________________________****
>
> ______________________________________________________________________
> Attention:
> This e-mail and any files transmitted with it from Hatch Mott MacDonald
> are confidential and intended solely for use of the individual or entity to
> whom they are addressed. If you have received this e-mail in error please
> immediately notify the sender.
> ______________________________________________________________________
>

Yes, good point.  I will do that.

Thanks again!

Julie



From: robertlipe@... [mailto:robertlipe@...] On Behalf Of Robert Lipe
Sent: Thursday, May 30, 2013 11:06 AM
To: Oates, Julie
Cc: gpsbabel-misc@...
Subject: Re: [Gpsbabel-misc] trackfilter-init: Track points badly ordered

speed relies on time moving forward. (Think about the math...)  If your GPS really is creating successive positions with non-linear times, you should probably file a bug report with GlobalSAT on that.

Enjoy.
RJL

If you find GPSBabel useful, especially if a feature was added or fixed for you, please consider supporting its development at http://www.gpsbabel.org/contribute.html



On Thu, May 30, 2013 at 12:47 PM, Oates, Julie <Julie.Oates@...>> wrote:
Yes, I did have the "Speed" and "Course" boxes checked in the Track Filters.  Apparently that wasn't necessary.  I unchecked them and ran it again and it worked fine.  Thank you so much for your help!

Julie

From: robertlipe@...> [mailto:robertlipe@...>] On Behalf Of Robert Lipe
Sent: Thursday, May 30, 2013 10:06 AM
To: Oates, Julie
Cc: gpsbabel-misc@...>
Subject: Re: [Gpsbabel-misc] trackfilter-init: Track points badly ordered

You're trying to do something more than download and convert to GPX, but you didn't say *what*.  That message is coming from the track filter, so you're doing some additional filtering on it that you did not describe.  You're attempting to perform some operation on track data that requires time to move forward, but as you see from the error, you have a trackpoint with a timestamp ending in ...10s that appears before ....08s.



On Thu, May 30, 2013 at 11:01 AM, Oates, Julie <Julie.Oates@...>> wrote:
I am trying to download tracks from a GlobalSAT DG-100 data logger to the GPX XML format and get the following error:


trackfilter-init: Track points badly ordered (timestamp 2013-05-21T21:06:10Z > 2013-05-21T21:06:08Z)!

Error running gpsbabel: Process exited unsucessfully with code 1

Does anyone know how to fix this?

Thanks!

Julie

______________________________________________________________________
Attention:
This e-mail and any files transmitted with it from Hatch Mott MacDonald are confidential and intended solely for use of the individual or entity to whom they are addressed. If you have received this e-mail in error please immediately notify the sender.
______________________________________________________________________

------------------------------------------------------------------------------
Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET
Get 100% visibility into your production application - at no cost.
Code-level diagnostics for performance bottlenecks with <2% overhead
Download for free and get started troubleshooting in minutes.
http://p.sf.net/sfu/appdyn_d2d_ap1
_______________________________________________
Gpsbabel-misc mailing list http://www.gpsbabel.org
Gpsbabel-misc@...>
To unsubscribe, change list options, or see archives, visit:
https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc


______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________

______________________________________________________________________
Attention:
This e-mail and any files transmitted with it from Hatch Mott MacDonald are confidential and intended solely for use of the individual or entity to whom they are addressed. If you have received this e-mail in error please immediately notify the sender.
______________________________________________________________________


______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________

______________________________________________________________________
Attention:
This e-mail and any files transmitted with it from Hatch Mott MacDonald are confidential and intended solely for use of the individual or entity to whom they are addressed. If you have received this e-mail in error please immediately notify the sender.
______________________________________________________________________

We have no explicit support for any Nobeltec files.  Without a sample, we
can't guess if it's likely to work with our unicsv format
http://www.gpsbabel.org/htmldoc-development/fmt_unicsv.html or if it's a
likely candidate to be implemented via
http://www.gpsbabel.org/htmldoc-development/Styles.html


On Wed, May 22, 2013 at 6:13 AM, Renaud ... <royale3@...> wrote:

> Hi...
>
> I have a data from the navigation software NOBELTEC in .txt format....
>
> I would like to know if its possible to convert this data in GPX format
> with GPSBABEL
>
> Thanks you for your reply....
>
> *Renaud *
>
>
> ------------------------------------------------------------------------------
> Try New Relic Now & We'll Send You this Cool Shirt
> New Relic is the only SaaS-based application performance monitoring service
> that delivers powerful full stack analytics. Optimize and monitor your
> browser, app, & servers with just a few lines of code. Try New Relic
> and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may
> _______________________________________________
> Gpsbabel-misc mailing list http://www.gpsbabel.org
> Gpsbabel-misc@...
> To unsubscribe, change list options, or see archives, visit:
> https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc
>
>

That format is not going to work with any of our "easy" methods.
Supporting it would require a programmer to work out the details and add
support in a new c++ module.
On May 23, 2013 11:02 AM, "Renaud ..." <royale3@...> wrote:

> Hi!!!
>
> Nobeltec Files sample....
>
> dont work with unicsv....
>
> Thank you for your help
>
> *Renaud *
>
> ------------------------------
> Date: Wed, 22 May 2013 13:42:24 -0700
> Subject: Re: [Gpsbabel-misc] Convert Nobeltec Data
> From: robertlipe@...
> To: royale3@...
> CC: gpsbabel-misc@...
>
> We have no explicit support for any Nobeltec files.  Without a sample, we
> can't guess if it's likely to work with our unicsv format
> http://www.gpsbabel.org/htmldoc-development/fmt_unicsv.html or if it's a
> likely candidate to be implemented via
> http://www.gpsbabel.org/htmldoc-development/Styles.html
>
>
> On Wed, May 22, 2013 at 6:13 AM, Renaud ... <royale3@...> wrote:
>
> Hi...
>
> I have a data from the navigation software NOBELTEC in .txt format....
>
> I would like to know if its possible to convert this data in GPX format
> with GPSBABEL
>
> Thanks you for your reply....
>
> *Renaud *
>
>
> ------------------------------------------------------------------------------
> Try New Relic Now & We'll Send You this Cool Shirt
> New Relic is the only SaaS-based application performance monitoring service
> that delivers powerful full stack analytics. Optimize and monitor your
> browser, app, & servers with just a few lines of code. Try New Relic
> and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may
> _______________________________________________
> Gpsbabel-misc mailing list http://www.gpsbabel.org
> Gpsbabel-misc@...
> To unsubscribe, change list options, or see archives, visit:
> https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc
>
>
>

Our format named "csv" is rarely the best fit for CSV files hocked up by
Excel.  Generally letting it write CSV files with the first line naming the
fields and feeding it to our unicsv reader is a better match.  The
supported column headers are described in the doc at
http://www.gpsbabel.org/htmldoc-development/fmt_unicsv.html

If you didn't provide an extension, we won't make one up.  It's up to you
to name the file as you need it.


On Tue, May 21, 2013 at 8:18 AM, Rich Rodenberg <rodenber@...:

> I have 2 Lowrance HDS 7 Generation 1 chartplotter/fishfinders.  They
> transfer data with SD cards.  Lowrance told me the units would accept data
> in USR or GPX formats.  I downloaded GPS Babel and tried to import a CSV
> and a XLS file with waypoints, descriptions, etc.  The file are from the
> state of Alabama and are supposed to be for import to GPS units.  I did the
> input for both the CSV and XLS files.  I set the outputs for GPX XML and
> also tried USR.  When I click apply I get a files successfully transferred
> message.  When I go to the GPS Babel files in the programs part of my
> computer I find an file with no extension and it is small.  This happened
> on all formats.  I tried uploading them to my units but they would not
> recognize the files.  I must be doing something wrong.  This would seem to
> be a very simple task but I can’t figure it out.  Do I need to modify the
> CSV file?  I did not find any mapping selection where you assign the
> columns to the output format.  Any suggestions?****
>
> ** **
>
> RR ****
>
>
> ------------------------------------------------------------------------------
> Try New Relic Now & We'll Send You this Cool Shirt
> New Relic is the only SaaS-based application performance monitoring service
> that delivers powerful full stack analytics. Optimize and monitor your
> browser, app, & servers with just a few lines of code. Try New Relic
> and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may
> _______________________________________________
> Gpsbabel-misc mailing list http://www.gpsbabel.org
> Gpsbabel-misc@...
> To unsubscribe, change list options, or see archives, visit:
> https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc
>
>

Earth includes its own copy of gpsbabel.  I can't recall if it's still
true, but at one time Earth's GPSBabel was built to use a libexpat that was
incompatible with the one that GPSBabel shipped with, so mixing them wasn't
practical.  But if you've clobbered Earth's GPSBabel with our official one,
re-installing Earth should get you back on track.  Then install GPSBabel in
its own default location to keep the copies separated.

Functionally, I think Earth 7.[012] is pretty darned close to GPSBabel
1.4.4.


On Tue, May 14, 2013 at 6:30 AM, Michael Manzenreither <
hfgnapzh7h@...> wrote:

> Hi,
>
> I just installed GPSBabel v1.4.4 on WinXP-SP3.
>
> After this I dropped a GPX file in GoogleEarth, and I get an error
> "gpsbabel.exe failed". (the GPX-file was not created with GPSBabel and
> worked before with GoogleEarth).
>
> I now scanned my system and found out, that there are 5 gpsbabel.exe files.
> - documents and settings
> - programs\Google\Google Earth
> - propgrams\GPSBabel
> - \WINDOWS\system32\config\systemprofile\local
> settings\Temp\._msige60\program files\Google\Google Earth\client\
> - \WINDOWS\system32\config\systemprofile\local
> settings\Temp\._msige61\program files\Google\Google Earth\client\
>
> any hint, how I get back Google Earth displaying GPX-files?
>
> thanks
> Michi
>
>
> ------------------------------------------------------------------------------
> AlienVault Unified Security Management (USM) platform delivers complete
> security visibility with the essential security capabilities. Easily and
> efficiently configure, manage, and operate all of your security controls
> from a single console and one unified framework. Download a free trial.
> http://p.sf.net/sfu/alienvault_d2d
> _______________________________________________
> Gpsbabel-misc mailing list http://www.gpsbabel.org
> Gpsbabel-misc@...
> To unsubscribe, change list options, or see archives, visit:
> https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc
>

Turning off all the options (all the xxx=0) certainly handicaps our ability
to read the files.  Don't specify those unless you need to force it to
ignore sentences.

$ ./gpsbabel -i nmea -f /tmp/xx -o gpx -F - | head -25
<?xml version="1.0" encoding="UTF-8"?>
<gpx
  version="1.0"
  creator="GPSBabel - http://www.gpsbabel.org"
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xmlns="http://www.topografix.com/GPX/1/0"
  xsi:schemaLocation="http://www.topografix.com/GPX/1/0
http://www.topografix.com/GPX/1/0/gpx.xsd">
  <time>2013-04-26T17:46:17Z</time>
  <bounds minlat="48.270950650" minlon="16.160488400" maxlat="48.270950650"
maxlon="16.160488400"/>
  <trk>
    <trkseg>
      <trkpt lat="48.270950650" lon="16.160488400">
<ele>455.800000</ele>
        <time>2008-12-28T00:00:48.600Z</time>
        <course>nan</course>
        <speed>0.000000</speed>
        <url></url>
        <fix>3d</fix>
        <sat>5</sat>
        <hdop>2.300000</hdop>
        <vdop>2.600000</vdop>
        <pdop>3.400000</pdop>
      </trkpt>
      <trkpt lat="48.270950650" lon="16.160488400">
<ele>455.800000</ele>


BTW, 1.4.4 is the current version.


On Fri, Apr 26, 2013 at 1:56 AM, kaefert <kaefert@...> wrote:

> I've used the search, and found this:
> http://gpsbabel.2324879.n4.nabble.com/NMEA-to-GPX-not-working-td4128.html
>
> But by browsing my NMEA-log I can defenitly see positions here:
>
> ...
> $GPGGA,000048.6,4816.257039,N,01609.629304,E,1,05,2.3,455.8,M,0,M,,*75
> $GPVTG,nan,T,,M,0.0,N,0.0,K,A*42
> $GPRMC,000048.6,A,4816.257039,N,01609.629304,E,0.0,,281208,,,A*4E
> ...
>
> I've got gpsbabel from my default system repos -> Linux Mint 14 = Ubuntu
> 12.10
> Package Version of gpsbabel & gpsbabel-gui = 1.4.3-1ubuntu1
>
> $ gpsbabel -V
> GPSBabel Version 1.4.3
>
> This is the output that the gpsbabelfe gui gave me:
>
> gpsbabel -w -t -i
>
> nmea,gprmc=0,gpgga=0,gpvtg=0,gpgsa=0,get_posn=0,append_positioning=0,gisteq=0
> -f /path/file.bin -o
> gpx,suppresswhite=0,logpoint=0,humminbirdextensions=0,garminextensions=0 -F
> /path/file.gpx
>
> Translation successful
>
> Here's an example of my NMEA log files:
> http://pastebin.com/xmET8hED
>
> This is the resulting gpx file:
> <?xml version="1.0" encoding="UTF-8"?>
> <gpx
>   version="1.0"
>   creator="GPSBabel - http://www.gpsbabel.org"
>   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>   xmlns="http://www.topografix.com/GPX/1/0"
>   xsi:schemaLocation="http://www.topografix.com/GPX/1/0
> http://www.topografix.com/GPX/1/0/gpx.xsd">
> <time>2013-04-26T06:26:01Z</time>
> </gpx>
>
>
>
> --
> View this message in context:
> http://gpsbabel.2324879.n4.nabble.com/NMEA-to-GPX-result-empty-gpx-tp10180.html
> Sent from the GPSBabel - General mailing list archive at Nabble.com.
>
>
> ------------------------------------------------------------------------------
> Try New Relic Now & We'll Send You this Cool Shirt
> New Relic is the only SaaS-based application performance monitoring service
> that delivers powerful full stack analytics. Optimize and monitor your
> browser, app, & servers with just a few lines of code. Try New Relic
> and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr
> _______________________________________________
> Gpsbabel-misc mailing list http://www.gpsbabel.org
> Gpsbabel-misc@...
> To unsubscribe, change list options, or see archives, visit:
> https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc
>

Thanks for this quick and accurate response!!
I've now used gpsbabel directly via the command line, without all those
extra options that gpsbabelfe produced automagically.

So with this:
gpsbabel -w -t -i nmea -f /path/file.bin -o gpx -F /path/file.gpx

I can produce the gpx files that I wanted.

Maybe this gui wrapper "gpsbabelfe" should be modified in a way that it does
not use those options by default.

Thanks again for the great support, and thanks to all the developers for
creating this wonderful tool!



--
View this message in context: http://gpsbabel.2324879.n4.nabble.com/NMEA-to-GPX-result-empty-gpx-tp10180p10183.html
Sent from the GPSBabel - General mailing list archive at Nabble.com.

1.  I don't see any problem with "height is converted without the 
decimal part"
2. The speed element was dropped from gpx 1.1, thus it is only output 
for gpx 1.0.  You were forcing gpx 1.1 (gpxver=1.1).
3. Your use of the track data filter (-x track.speed) causes speed to be 
computed from the position and times.  This overwrites the speeds from 
your input file.

gpsbabel -t -i unicsv -f test.csv -o gpx -F test.gpx

results in:
> <?xml version="1.0" encoding="UTF-8"?>
> <gpx
>   version="1.0"
>   creator="GPSBabel - http://www.gpsbabel.org"
>   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>   xmlns="http://www.topografix.com/GPX/1/0"
>   xsi:schemaLocation="http://www.topografix.com/GPX/1/0 
> http://www.topografix.com/GPX/1/0/gpx.xsd">
> <time>2013-04-13T13:36:15Z</time>
> <bounds minlat="36.118837000" minlon="-115.173909000" 
> maxlat="36.120097000" maxlon="-115.172764000"/>
> <trk>
> <trkseg>
> <trkpt lat="36.118854000" lon="-115.172849000">
>   <ele>788.400000</ele>
>   <time>2013-04-01T06:51:05Z</time>
>   <speed>3.000000</speed>
>   <desc>1</desc>
> </trkpt>
> <trkpt lat="36.118837000" lon="-115.172834000">
>   <ele>787.800000</ele>
>   <time>2013-04-01T06:51:06Z</time>
>   <speed>6.100000</speed>
>   <desc>2</desc>
> </trkpt>
> <trkpt lat="36.118890000" lon="-115.172808000">
>   <ele>787.600000</ele>
>   <time>2013-04-01T06:51:13Z</time>
>   <speed>8.300000</speed>
>   <desc>3</desc>
> </trkpt>
> <trkpt lat="36.118933000" lon="-115.172827000">
>   <ele>787.600000</ele>
>   <time>2013-04-01T06:51:14Z</time>
>   <speed>10.600000</speed>
>   <desc>4</desc>
> </trkpt>
> <trkpt lat="36.118904000" lon="-115.172764000">
>   <ele>787.400000</ele>
>   <time>2013-04-01T06:51:17Z</time>
>   <speed>13.600000</speed>
>   <desc>5</desc>
> </trkpt>
> <trkpt lat="36.118962000" lon="-115.172792000">
>   <ele>786.900000</ele>
>   <time>2013-04-01T06:51:20Z</time>
>   <speed>17.799999</speed>
>   <desc>6</desc>
> </trkpt>
> <trkpt lat="36.119001000" lon="-115.172821000">
>   <ele>786.200000</ele>
>   <time>2013-04-01T06:51:21Z</time>
>   <speed>22.700001</speed>
>   <desc>7</desc>
> </trkpt>
> <trkpt lat="36.119073000" lon="-115.172874000">
>   <ele>785.500000</ele>
>   <time>2013-04-01T06:51:22Z</time>
>   <speed>27.799999</speed>
>   <desc>8</desc>
> </trkpt>
> <trkpt lat="36.119178000" lon="-115.172931000">
>   <ele>784.800000</ele>
>   <time>2013-04-01T06:51:23Z</time>
>   <speed>32.299999</speed>
>   <desc>9</desc>
> </trkpt>
> <trkpt lat="36.119231000" lon="-115.172960000">
>   <ele>784.400000</ele>
>   <time>2013-04-01T06:51:24Z</time>
>   <speed>35.700001</speed>
>   <desc>10</desc>
> </trkpt>
> <trkpt lat="36.119345000" lon="-115.173057000">
>   <ele>784.200000</ele>
>   <time>2013-04-01T06:51:25Z</time>
>   <speed>37.900002</speed>
>   <desc>11</desc>
> </trkpt>
> <trkpt lat="36.119505000" lon="-115.173158000">
>   <ele>784.300000</ele>
>   <time>2013-04-01T06:51:26Z</time>
>   <speed>38.700001</speed>
>   <desc>12</desc>
> </trkpt>
> <trkpt lat="36.119684000" lon="-115.173331000">
>   <ele>784.400000</ele>
>   <time>2013-04-01T06:51:35Z</time>
>   <speed>38.599998</speed>
>   <desc>13</desc>
> </trkpt>
> <trkpt lat="36.119950000" lon="-115.173668000">
>   <ele>784.700000</ele>
>   <time>2013-04-01T06:51:37Z</time>
>   <speed>37.799999</speed>
>   <desc>14</desc>
> </trkpt>
> <trkpt lat="36.120008000" lon="-115.173727000">
>   <ele>784.900000</ele>
>   <time>2013-04-01T06:51:38Z</time>
>   <speed>36.700001</speed>
>   <desc>15</desc>
> </trkpt>
> <trkpt lat="36.119950000" lon="-115.173668000">
>   <ele>784.800000</ele>
>   <time>2013-04-01T06:51:40Z</time>
>   <speed>35.500000</speed>
>   <desc>16</desc>
> </trkpt>
> <trkpt lat="36.119991000" lon="-115.173717000">
>   <ele>784.300000</ele>
>   <time>2013-04-01T06:51:41Z</time>
>   <speed>34.299999</speed>
>   <desc>17</desc>
> </trkpt>
> <trkpt lat="36.119900000" lon="-115.173670000">
>   <ele>783.200000</ele>
>   <time>2013-04-01T06:51:43Z</time>
>   <speed>33.099998</speed>
>   <desc>18</desc>
> </trkpt>
> <trkpt lat="36.119934000" lon="-115.173744000">
>   <ele>781.100000</ele>
>   <time>2013-04-01T06:51:45Z</time>
>   <speed>31.700001</speed>
>   <desc>19</desc>
> </trkpt>
> <trkpt lat="36.120097000" lon="-115.173909000">
>   <ele>778.000000</ele>
>   <time>2013-04-01T06:51:47Z</time>
>   <speed>29.900000</speed>
>   <desc>20</desc>
> </trkpt>
> <trkpt lat="36.119678000" lon="-115.173451000">
>   <ele>773.800000</ele>
>   <time>2013-04-01T06:51:49Z</time>
>   <speed>27.799999</speed>
>   <desc>21</desc>
> </trkpt>
> <trkpt lat="36.119242000" lon="-115.173186000">
>   <ele>768.600000</ele>
>   <time>2013-04-01T06:51:58Z</time>
>   <speed>25.299999</speed>
>   <desc>22</desc>
> </trkpt>
> <trkpt lat="36.119183000" lon="-115.173127000">
>   <ele>762.600000</ele>
>   <time>2013-04-01T06:51:59Z</time>
>   <speed>22.500000</speed>
>   <desc>23</desc>
> </trkpt>
> <trkpt lat="36.119255000" lon="-115.173150000">
>   <ele>755.900000</ele>
>   <time>2013-04-01T06:52:24Z</time>
>   <speed>19.600000</speed>
>   <desc>24</desc>
> </trkpt>
> <trkpt lat="36.119175000" lon="-115.173236000">
>   <ele>748.900000</ele>
>   <time>2013-04-01T06:54:01Z</time>
>   <speed>16.700001</speed>
>   <desc>25</desc>
> </trkpt>
> <trkpt lat="36.119213000" lon="-115.173199000">
>   <ele>741.900000</ele>
>   <time>2013-04-01T06:54:23Z</time>
>   <speed>14.000000</speed>
>   <desc>26</desc>
> </trkpt>
> </trkseg>
> </trk>
> </gpx>


On 4/13/2013 2:58 AM, Achim Theobald wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hello,
>
> I would like to convert a *.csv file into a *.gpx file and use the
> unicsv import filter. But it doesn't work as expected. The position
> values​​, date and time would be correctly converted. But at the speed
> and the height, there are some problems.
> The speed is completely missing, and at the height is converted without
> the decimal part.
>
> Tested with this parameter:
>
> gpsbabel -D9 -t -i unicsv -f ./sorted4.csv -x track,speed -o
> gpx,gpxver=1.1 -F ./out4.gpx
>
> or:
>
> gpsbabel -D9 -t -i unicsv -f ./sorted4.csv -x track -o gpx,gpxver=1.1 -F
> ./out4.gpx
>
>
> CSV-Testfile ################
>
> comment, cont, date, time, lat, n/s, lon, e/w, alt, speed, notes, notes
> 1,7,2013/04/01,00:51:05.00,36.118854,N,115.172849,W,788.40,3.00,,
> 2,7,2013/04/01,00:51:06.00,36.118837,N,115.172834,W,787.80,6.10,,
> 3,7,2013/04/01,00:51:13.00,36.118890,N,115.172808,W,787.60,8.30,,
> 4,7,2013/04/01,00:51:14.00,36.118933,N,115.172827,W,787.60,10.60,,
> 5,7,2013/04/01,00:51:17.00,36.118904,N,115.172764,W,787.40,13.60,,
> 6,7,2013/04/01,00:51:20.00,36.118962,N,115.172792,W,786.90,17.80,,
> 7,7,2013/04/01,00:51:21.00,36.119001,N,115.172821,W,786.20,22.70,,
> 8,7,2013/04/01,00:51:22.00,36.119073,N,115.172874,W,785.50,27.80,,
> 9,7,2013/04/01,00:51:23.00,36.119178,N,115.172931,W,784.80,32.30,,
> 10,7,2013/04/01,00:51:24.00,36.119231,N,115.172960,W,784.40,35.70,,
> 11,7,2013/04/01,00:51:25.00,36.119345,N,115.173057,W,784.20,37.90,,
> 12,7,2013/04/01,00:51:26.00,36.119505,N,115.173158,W,784.30,38.70,,
> 13,7,2013/04/01,00:51:35.00,36.119684,N,115.173331,W,784.40,38.60,,
> 14,7,2013/04/01,00:51:37.00,36.119950,N,115.173668,W,784.70,37.80,,
> 15,7,2013/04/01,00:51:38.00,36.120008,N,115.173727,W,784.90,36.70,,
> 16,7,2013/04/01,00:51:40.00,36.119950,N,115.173668,W,784.80,35.50,,
> 17,7,2013/04/01,00:51:41.00,36.119991,N,115.173717,W,784.30,34.30,,
> 18,7,2013/04/01,00:51:43.00,36.119900,N,115.173670,W,783.20,33.10,,
> 19,7,2013/04/01,00:51:45.00,36.119934,N,115.173744,W,781.10,31.70,,
> 20,7,2013/04/01,00:51:47.00,36.120097,N,115.173909,W,778.00,29.90,,
> 21,7,2013/04/01,00:51:49.00,36.119678,N,115.173451,W,773.80,27.80,,
> 22,7,2013/04/01,00:51:58.00,36.119242,N,115.173186,W,768.60,25.30,,
> 23,7,2013/04/01,00:51:59.00,36.119183,N,115.173127,W,762.60,22.50,,
> 24,7,2013/04/01,00:52:24.00,36.119255,N,115.173150,W,755.90,19.60,,
> 25,7,2013/04/01,00:54:01.00,36.119175,N,115.173236,W,748.90,16.70,,
> 26,7,2013/04/01,00:54:23.00,36.119213,N,115.173199,W,741.90,14.00,,
>
> #################
>
> Exportet GPX file #################
>
> <?xml version="1.0" encoding="UTF-8"?>
> <gpx
>    version="1.1"
>    creator="GPSBabel - http://www.gpsbabel.org"
>    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>    xmlns="http://www.topografix.com/GPX/1/1"
>    xsi:schemaLocation="http://www.topografix.com/GPX/1/1
> http://www.topografix.com/GPX/1/1/gpx.xsd">
> <metadata>
> <time>2013-04-13T08:43:30Z</time>
> <bounds minlat="36.118837000" minlon="-115.173909000"
> maxlat="36.120097000" maxlon="-115.172764000"/>
> </metadata>
> <trk>
> <trkseg>
> <trkpt lat="36.118854000" lon="-115.172849000">
>    <ele>788.400000</ele>
>    <time>2013-03-31T22:51:05Z</time>
>    <desc>1</desc>
> </trkpt>
> <trkpt lat="36.118837000" lon="-115.172834000">
>    <ele>787.800000</ele>
>    <time>2013-03-31T22:51:06Z</time>
>    <desc>2</desc>
> </trkpt>
> <trkpt lat="36.118890000" lon="-115.172808000">
>    <ele>787.600000</ele>
>    <time>2013-03-31T22:51:13Z</time>
>    <desc>3</desc>
> </trkpt>
> <trkpt lat="36.118933000" lon="-115.172827000">
>    <ele>787.600000</ele>
>    <time>2013-03-31T22:51:14Z</time>
>    <desc>4</desc>
> </trkpt>
> <trkpt lat="36.118904000" lon="-115.172764000">
>    <ele>787.400000</ele>
>    <time>2013-03-31T22:51:17Z</time>
>    <desc>5</desc>
> </trkpt>
> <trkpt lat="36.118962000" lon="-115.172792000">
>    <ele>786.900000</ele>
>    <time>2013-03-31T22:51:20Z</time>
>    <desc>6</desc>
> </trkpt>
> <trkpt lat="36.119001000" lon="-115.172821000">
>    <ele>786.200000</ele>
>    <time>2013-03-31T22:51:21Z</time>
>    <desc>7</desc>
> </trkpt>
> <trkpt lat="36.119073000" lon="-115.172874000">
>    <ele>785.500000</ele>
>    <time>2013-03-31T22:51:22Z</time>
>    <desc>8</desc>
> </trkpt>
> <trkpt lat="36.119178000" lon="-115.172931000">
>    <ele>784.800000</ele>
>    <time>2013-03-31T22:51:23Z</time>
>    <desc>9</desc>
> </trkpt>
> <trkpt lat="36.119231000" lon="-115.172960000">
>    <ele>784.400000</ele>
>    <time>2013-03-31T22:51:24Z</time>
>    <desc>10</desc>
> </trkpt>
> <trkpt lat="36.119345000" lon="-115.173057000">
>    <ele>784.200000</ele>
>    <time>2013-03-31T22:51:25Z</time>
>    <desc>11</desc>
> </trkpt>
> <trkpt lat="36.119505000" lon="-115.173158000">
>    <ele>784.300000</ele>
>    <time>2013-03-31T22:51:26Z</time>
>    <desc>12</desc>
> </trkpt>
> <trkpt lat="36.119684000" lon="-115.173331000">
>    <ele>784.400000</ele>
>    <time>2013-03-31T22:51:35Z</time>
>    <desc>13</desc>
> </trkpt>
> <trkpt lat="36.119950000" lon="-115.173668000">
>    <ele>784.700000</ele>
>    <time>2013-03-31T22:51:37Z</time>
>    <desc>14</desc>
> </trkpt>
> <trkpt lat="36.120008000" lon="-115.173727000">
>    <ele>784.900000</ele>
>    <time>2013-03-31T22:51:38Z</time>
>    <desc>15</desc>
> </trkpt>
> <trkpt lat="36.119950000" lon="-115.173668000">
>    <ele>784.800000</ele>
>    <time>2013-03-31T22:51:40Z</time>
>    <desc>16</desc>
> </trkpt>
> <trkpt lat="36.119991000" lon="-115.173717000">
>    <ele>784.300000</ele>
>    <time>2013-03-31T22:51:41Z</time>
>    <desc>17</desc>
> </trkpt>
> <trkpt lat="36.119900000" lon="-115.173670000">
>    <ele>783.200000</ele>
>    <time>2013-03-31T22:51:43Z</time>
>    <desc>18</desc>
> </trkpt>
> <trkpt lat="36.119934000" lon="-115.173744000">
>    <ele>781.100000</ele>
>    <time>2013-03-31T22:51:45Z</time>
>    <desc>19</desc>
> </trkpt>
> <trkpt lat="36.120097000" lon="-115.173909000">
>    <ele>778.000000</ele>
>    <time>2013-03-31T22:51:47Z</time>
>    <desc>20</desc>
> </trkpt>
> <trkpt lat="36.119678000" lon="-115.173451000">
>    <ele>773.800000</ele>
>    <time>2013-03-31T22:51:49Z</time>
>    <desc>21</desc>
> </trkpt>
> <trkpt lat="36.119242000" lon="-115.173186000">
>    <ele>768.600000</ele>
>    <time>2013-03-31T22:51:58Z</time>
>    <desc>22</desc>
> </trkpt>
> <trkpt lat="36.119183000" lon="-115.173127000">
>    <ele>762.600000</ele>
>    <time>2013-03-31T22:51:59Z</time>
>    <desc>23</desc>
> </trkpt>
> <trkpt lat="36.119255000" lon="-115.173150000">
>    <ele>755.900000</ele>
>    <time>2013-03-31T22:52:24Z</time>
>    <desc>24</desc>
> </trkpt>
> <trkpt lat="36.119175000" lon="-115.173236000">
>    <ele>748.900000</ele>
>    <time>2013-03-31T22:54:01Z</time>
>    <desc>25</desc>
> </trkpt>
> <trkpt lat="36.119213000" lon="-115.173199000">
>    <ele>741.900000</ele>
>    <time>2013-03-31T22:54:23Z</time>
>    <desc>26</desc>
> </trkpt>
> </trkseg>
> </trk>
> </gpx>
>
>
>
> Any solution for this problems available?
>
> - -- 
> Cu
>
> Achim
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.19 (GNU/Linux)
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>
> iQEcBAEBAgAGBQJRaR4cAAoJEPFIdvDeETreZi0IAIBc4ifncrIuGuXDiGbNlj9f
> mLwwFls7h7R9HegJvuf0KN83GvhEr/Q/DToUFcFxn6gvO4Av/c3U6U7Ft5ax8uEg
> Sp3HeSSGwINUlTj8XlKYbMrztSd0zhFqFgi7r+OPMo2dHY1+lh5LyQb5GJqgp8PX
> wu2ly0fkxPEI0L/7NtwcdzG7fmcEy6NlaXwMuk+4Bd22/g9VAqjKC2OXWx60N9Cg
> 4OR0DQJJa6Lmk4wsAxnDKqyq8Jy2M/xOifJ4JgwWxYodchQUdwoBVpZD8xf8I9GK
> 8Pk12TBweihrFvwsll9jnS+XAFYrRfox+mz5QKr+qk6JrC5QlFTo95jwJ8I16AM=
> =Rt+B
> -----END PGP SIGNATURE-----
>
> ------------------------------------------------------------------------------
> Precog is a next-generation analytics platform capable of advanced
> analytics on semi-structured data. The platform includes APIs for building
> apps and a phenomenal toolset for data science. Developers can use
> our toolset for easy data analysis & visualization. Get a free account!
> http://www2.precog.com/precogplatform/slashdotnewsletter
> _______________________________________________
> Gpsbabel-misc mailing list http://www.gpsbabel.org
> Gpsbabel-misc@...
> To unsubscribe, change list options, or see archives, visit:
> https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 04/13/2013 03:46 PM, tsteven4 wrote:
> 1.  I don't see any problem with "height is converted without the
> decimal part"
> 2. The speed element was dropped from gpx 1.1, thus it is only output
> for gpx 1.0.  You were forcing gpx 1.1 (gpxver=1.1).

This was the solution for the main problem.

I love higher version number with a function downgrade :-\

Thank you

> 3. Your use of the track data filter (-x track.speed) causes speed to be
> computed from the position and times.  This overwrites the speeds from
> your input file.

- -- 
Cu

Achim
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJRaYEMAAoJEPFIdvDeETre9JEIAKJuBTp7Z9C4SPp3ovsunumK
IXIFRxU01WN9LfBldDtWgoFoef/1Fxes2SQGCCvTHpa31hx/56X3hCnuvndd9gOF
GGaJCy1BW0whyAnOk83s04fkW8zJPsK/jOQDPXPa0vOao9EzWBYl1LOjUn/qoQUt
gUO8P4iFvnWIkQrFuNaSUZ2W7/P+iMvEtrFz5HOurncWEvxb5isRKgAMy5rWhxEa
MAuDvEi0527h1aiMbSQ5OoYV57FYYBTNtRbgvw3RHf7Zuu3T5MoyZ3XH79WGo37S
J5Naz/FVzCvll94iMOBQX2QWKPUrBklrH9Da5hhmYVbXxI9e744H5mGXzSnNyHs=
=LoAM
-----END PGP SIGNATURE-----