Thread: [Gpsbabel-misc] "iBlue747 csv" to NMEA conversion replacing date/timefields with 000000
Brought to you by:
robertl
From: Tony V. <adv...@ho...> - 2011-06-22 00:52:59
|
Hi there, Hoping someone can help me. I'm having some trouble converting an iBlue747 CSV log file from my iBlue757 device to the NMEA format for importing into RaceChrono. The problem I am finding is that the conversion seems to leave the date and time fields as zeros in the NMEA file. As an example, the first 5 lines of the CSV file are as follows: INDEX,RCR,DATE,TIME,VALID,LATITUDE,N/S,LONGITUDE,E/W,HEIGHT,SPEED,DISTANCE 3308,T,14/05/2011,4:15:11,DGPS,-33.803645,S,150.880499,E,99.859 m,0.207 km/h, 0.28 m 3309,T,14/05/2011,4:15:12,DGPS,-33.803645,S,150.880499,E,100.137 m,0.362 km/h, 0.28 m 3310,T,14/05/2011,4:15:13,DGPS,-33.803644,S,150.8805,E,100.416 m,0.302 km/h, 0.30 m 3311,T,14/05/2011,4:15:14,DGPS,-33.803644,S,150.880501,E,100.678 m,0.211 km/h, 0.27 m 3312,T,14/05/2011,4:15:15,DGPS,-33.803644,S,150.880501,E,100.942 m,0.201 km/h, 0.27 m And the resulting NMEA file from the GUI version of GPSBabel 1.4.2 is: $GPRMC,000000.000,A,3348.219,S,15052.830,E,0.11,0.00,000000,,*10 $GPGGA,000000.000,3348.219,S,15052.830,E,1,00,0.0,99.859,M,0.0,M,,*4B $GPVTG,0.000,T,0,M,0.112,N,0.207,K*57 $GPGSA,A,3,,,,,,,,,,,,,0.0,0.0,0.0*32 $GPRMC,000000.000,A,3348.219,S,15052.830,E,0.20,0.00,000000,,*12 $GPGGA,000000.000,3348.219,S,15052.830,E,1,00,0.0,100.137,M,0.0,M,,*7B $GPVTG,0.000,T,0,M,0.195,N,0.362,K*5A $GPGSA,A,3,,,,,,,,,,,,,0.0,0.0,0.0*32 $GPRMC,000000.000,A,3348.219,S,15052.830,E,0.16,0.00,000000,,*17 $GPGGA,000000.000,3348.219,S,15052.830,E,1,00,0.0,100.416,M,0.0,M,,*7D $GPVTG,0.000,T,0,M,0.163,N,0.302,K*55 $GPGSA,A,3,,,,,,,,,,,,,0.0,0.0,0.0*32 $GPRMC,000000.000,A,3348.219,S,15052.830,E,0.11,0.00,000000,,*10 $GPGGA,000000.000,3348.219,S,15052.830,E,1,00,0.0,100.678,M,0.0,M,,*77 $GPVTG,0.000,T,0,M,0.114,N,0.211,K*56 $GPGSA,A,3,,,,,,,,,,,,,0.0,0.0,0.0*32 $GPRMC,000000.000,A,3348.219,S,15052.830,E,0.11,0.00,000000,,*10 $GPGGA,000000.000,3348.219,S,15052.830,E,1,00,0.0,100.942,M,0.0,M,,*71 $GPVTG,0.000,T,0,M,0.109,N,0.201,K*5B $GPGSA,A,3,,,,,,,,,,,,,0.0,0.0,0.0*32 Do you have any ideas as to what might be causing the dates and times to be missed? Am I doing something wrong? Note that I did try using Excel to put the correct dates and times into the NMEA sentences but didn't work either - the waypoints seem to be all out of order. Another strange thing is that while I specify only GPRMC and GPGGA in the options, it still returns the VTG and GSA sentences anyway. Thanks in advance for your help and for this great piece of software. Cheers, Anthony |
From: Robert L. <rob...@gp...> - 2011-06-22 01:26:55
|
On Tue, Jun 21, 2011 at 7:48 PM, Tony Vel <adv...@ho...> wrote: > Hi there,**** > > ** ** > > Hoping someone can help me. I’m having some trouble converting an iBlue747 > CSV log file from my iBlue757 device to the NMEA format for importing into > RaceChrono. > Apparently they changed the file format between the 747 and the 757. (Be sure and send them a thank you letter...) If you look at the iblue747.csv file in our reference/tracks/ directory, you'll see it starts: $ head -5 track/iblue747.csv INDEX,RCR,DATE,TIME,VALID,LATITUDE,N/S,LONGITUDE,E/W,HEIGHT,SPEED,DISTANCE, 1,T,2005/05/01,10:12:47,Unknown,51.311770,N,12.413179,E,146,0.0,0.000000 2,T,2005/05/01,10:13:04,Unknown,51.311807,N,12.412898,E,146,4.2,0.019979 3,T,2005/05/01,10:13:13,Unknown,51.311885,N,12.412773,E,147,4.9,0.032214 4,T,2005/05/01,10:13:57,Unknown,51.312158,N,12.412265,E,142,3.8,0.078821 The good news is that this should be easy for you to compensate for. Take the iblue747.style from our source tree and adapt it to this new format. (Or see if there's some setting that lets you use YYYY/MM/DD instead of DD/MM/YYYY.) It'll be a while before I can get to it. But if you do it and can provide a paragraph of doc and send it back to us, I'll check it in for the next 757 user. RJL > **** > > The problem I am finding is that the conversion seems to leave the date and > time fields as zeros in the NMEA file. As an example, the first 5 lines of > the CSV file are as follows:**** > > ** ** > > INDEX,RCR,DATE,TIME,VALID,LATITUDE,N/S,LONGITUDE,E/W,HEIGHT,SPEED,DISTANCE > **** > > 3308,T,*14/05/2011*,*4:15:11*,DGPS,-33.803645,S,150.880499,E,99.859 > m,0.207 km/h, 0.28 m**** > > 3309,T,14/05/2011,4:15:12,DGPS,-33.803645,S,150.880499,E,100.137 m,0.362 > km/h, 0.28 m**** > > 3310,T,14/05/2011,4:15:13,DGPS,-33.803644,S,150.8805,E,100.416 m,0.302 > km/h, 0.30 m**** > > 3311,T,14/05/2011,4:15:14,DGPS,-33.803644,S,150.880501,E,100.678 m,0.211 > km/h, 0.27 m**** > > 3312,T,14/05/2011,4:15:15,DGPS,-33.803644,S,150.880501,E,100.942 m,0.201 > km/h, 0.27 m**** > > ** ** > > And the resulting NMEA file from the GUI version of GPSBabel 1.4.2 is:**** > > ** ** > > $GPRMC,*000000.000*,A,3348.219,S,15052.830,E,0.11,0.00,*000000*,,*10**** > > $GPGGA,*000000.000*,3348.219,S,15052.830,E,1,00,0.0,99.859,M,0.0,M,,*4B*** > * > > $GPVTG,0.000,T,0,M,0.112,N,0.207,K*57**** > > $GPGSA,A,3,,,,,,,,,,,,,0.0,0.0,0.0*32**** > > $GPRMC,000000.000,A,3348.219,S,15052.830,E,0.20,0.00,000000,,*12**** > > $GPGGA,000000.000,3348.219,S,15052.830,E,1,00,0.0,100.137,M,0.0,M,,*7B**** > > $GPVTG,0.000,T,0,M,0.195,N,0.362,K*5A**** > > $GPGSA,A,3,,,,,,,,,,,,,0.0,0.0,0.0*32**** > > $GPRMC,000000.000,A,3348.219,S,15052.830,E,0.16,0.00,000000,,*17**** > > $GPGGA,000000.000,3348.219,S,15052.830,E,1,00,0.0,100.416,M,0.0,M,,*7D**** > > $GPVTG,0.000,T,0,M,0.163,N,0.302,K*55**** > > $GPGSA,A,3,,,,,,,,,,,,,0.0,0.0,0.0*32**** > > $GPRMC,000000.000,A,3348.219,S,15052.830,E,0.11,0.00,000000,,*10**** > > $GPGGA,000000.000,3348.219,S,15052.830,E,1,00,0.0,100.678,M,0.0,M,,*77**** > > $GPVTG,0.000,T,0,M,0.114,N,0.211,K*56**** > > $GPGSA,A,3,,,,,,,,,,,,,0.0,0.0,0.0*32**** > > $GPRMC,000000.000,A,3348.219,S,15052.830,E,0.11,0.00,000000,,*10**** > > $GPGGA,000000.000,3348.219,S,15052.830,E,1,00,0.0,100.942,M,0.0,M,,*71**** > > $GPVTG,0.000,T,0,M,0.109,N,0.201,K*5B**** > > $GPGSA,A,3,,,,,,,,,,,,,0.0,0.0,0.0*32**** > > ** ** > > Do you have any ideas as to what might be causing the dates and times to be > missed? Am I doing something wrong?**** > > Note that I did try using Excel to put the correct dates and times into the > NMEA sentences but didn’t work either – the waypoints seem to be all out of > order.**** > > Another strange thing is that while I specify only GPRMC and GPGGA in the > options, it still returns the VTG and GSA sentences anyway.**** > > ** ** > > Thanks in advance for your help and for this great piece of software.**** > > ** ** > > Cheers,**** > > Anthony**** > > > ------------------------------------------------------------------------------ > Simplify data backup and recovery for your virtual environment with > vRanger. > Installation's a snap, and flexible recovery options mean your data is > safe, > secure and there when you need it. Data protection magic? > Nope - It's vRanger. Get your free trial download today. > http://p.sf.net/sfu/quest-sfdev2dev > _______________________________________________ > 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 > > |