Thread: [Gpsbabel-misc] question on NMEA format
Brought to you by:
robertl
From: jwf <jw...@fo...> - 2004-05-01 00:12:01
|
Good evening: I am working with some data files a co-worker collected. They are NMEA sentences, but only contain the GPRMC and GPGGA messages. I am trying to convert them to Delorme Street Atlas, that's what I happen to have laying around, but any of the commercial softwares would be fine. The problem I have is when I run a conversion none of the data appears in the output file. I have tried the CSV formats, the HTML format, nothing appears. Is GPSBable capable of working with the incomplete NMEA dataset? I will attach an original dataset as log3.txt, and the results of the conversion to html output as log3.html. Thanks for the help! - Jason |
From: Robert L. <rob...@us...> - 2004-05-01 03:30:39
|
jwf wrote: > I am working with some data files a co-worker collected. They are NMEA > sentences, but only contain the GPRMC and GPGGA messages. I am trying By my understanding, there's a huge overlapt between those... > The problem I have is when I run a conversion none of the data appears > in the output file. I have tried the CSV formats, the HTML format, > nothing appears. Is GPSBable capable of working with the incomplete > NMEA dataset? I just took your 44 lines input which consisted of 44 lines of data with essentially a 100% redundancy, and got exactly what I expected - 22 trkpoints when I converted to GPX. $ gpsbabel -t -i nmea -f log3.txt -o gpx -F - | grep /trkpt | wc -l 22 Neither CSV nor HTML claim to support tracks, per http://gpsbabel.sourceforge.net/capabilities.html so it's not suprising to me that converting a track to those two formats resulted in less than satisfying results. I repeated with: ~/src/gpsbabel/gpsbabel -t -i nmea -f log3.txt -o mapsend -F /tmp/blah.trk and was able to slurp it in to Mapsend and see a 22 point track that showed you heading downhill toward Willis Creek in South PA area, so I don't know what part we didn't handle well. (As perspective, the NMEA streams don't contain dates or timezone info, so we can't do much about that...) |
From: jwf <jw...@fo...> - 2004-05-01 12:19:02
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type"> <title></title> </head> <body bgcolor="#ffffff" text="#000000"> Yes, there is certainly a large amount of overlap. I believe he needs the altitude from the GGA.<br> <br> I was able to reproduce your results with the gpx and mapsend formats. My earlier email was unclear, there were two formats in particular that I was not getting data from. When trying to do saroute I get: <br> <br> gpsbabel -t -i nmea -f log3.txt -o saroute -F log3.anr<br> saroute:Not enough information is known about this format to write it.<br> <br> which appears to be contrary to the website. Not sure if this message refers to not being able to write the format at all, or my incomplete data set not being enough to write it. <br> <br> When I try gpl I do not get an error, but a file of zero size. <br> <br> gpsbabel -t -i nmea -f log3.txt -o gpl -F log3.gpl<br> <br> If I could use one of those two formats (preferably the saroute) I could use my current Street Atlas software. Thanks!<br> <br> <br> -jw<br> <br> Robert Lipe wrote:<br> <blockquote cite="mid...@rj..." type="cite"> <pre wrap="">jwf wrote: </pre> <blockquote type="cite"> <pre wrap="">I am working with some data files a co-worker collected. They are NMEA sentences, but only contain the GPRMC and GPGGA messages. I am trying </pre> </blockquote> <pre wrap=""><!----> By my understanding, there's a huge overlapt between those... </pre> <blockquote type="cite"> <pre wrap="">The problem I have is when I run a conversion none of the data appears in the output file. I have tried the CSV formats, the HTML format, nothing appears. Is GPSBable capable of working with the incomplete NMEA dataset? </pre> </blockquote> <pre wrap=""><!----> I just took your 44 lines input which consisted of 44 lines of data with essentially a 100% redundancy, and got exactly what I expected - 22 trkpoints when I converted to GPX. $ gpsbabel -t -i nmea -f log3.txt -o gpx -F - | grep /trkpt | wc -l 22 Neither CSV nor HTML claim to support tracks, per <a class="moz-txt-link-freetext" href="http://gpsbabel.sourceforge.net/capabilities.html">http://gpsbabel.sourceforge.net/capabilities.html</a> so it's not suprising to me that converting a track to those two formats resulted in less than satisfying results. I repeated with: ~/src/gpsbabel/gpsbabel -t -i nmea -f log3.txt -o mapsend -F /tmp/blah.trk and was able to slurp it in to Mapsend and see a 22 point track that showed you heading downhill toward Willis Creek in South PA area, so I don't know what part we didn't handle well. (As perspective, the NMEA streams don't contain dates or timezone info, so we can't do much about that...) </pre> </blockquote> </body> </html> |
From: Robert L. <rob...@us...> - 2004-05-03 01:46:23
|
jwf wrote: > Yes, there is certainly a large amount of overlap. I believe he needs > the altitude from the GGA. Good. We prefer GGA over RMC when we have both for this very reason. > gpsbabel -t -i nmea -f log3.txt -o saroute -F log3.anr > saroute:Not enough information is known about this format to write it. > which appears to be contrary to the website. Not sure if this message The website was wrong. I've fixed it. This is a reverse-engineered format and while we (Ron) have figure out where the coords are, there's a bunch of extra goop that's unknown to us. To this is one of our rare "read-only" formats. > When I try gpl I do not get an error, but a file of zero size. > gpsbabel -t -i nmea -f log3.txt -o gpl -F log3.gpl The GPL module was broken. I've fixed it. The fix will appear in 1.2.3 which I'm in the process of closing down right now. Enjoy. RJL |
From: jwf <jw...@fo...> - 2004-05-03 10:50:45
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type"> <title></title> </head> <body bgcolor="#ffffff" text="#000000"> Awesome, thanks much!<br> <br> <br> -jw<br> <br> Robert Lipe wrote:<br> <blockquote cite="mid...@rj..." type="cite"> <pre wrap="">jwf wrote: </pre> <blockquote type="cite"> <pre wrap=""> Yes, there is certainly a large amount of overlap. I believe he needs the altitude from the GGA. </pre> </blockquote> <pre wrap=""><!----> Good. We prefer GGA over RMC when we have both for this very reason. </pre> <blockquote type="cite"> <pre wrap=""> gpsbabel -t -i nmea -f log3.txt -o saroute -F log3.anr saroute:Not enough information is known about this format to write it. which appears to be contrary to the website. Not sure if this message </pre> </blockquote> <pre wrap=""><!----> The website was wrong. I've fixed it. This is a reverse-engineered format and while we (Ron) have figure out where the coords are, there's a bunch of extra goop that's unknown to us. To this is one of our rare "read-only" formats. </pre> <blockquote type="cite"> <pre wrap=""> When I try gpl I do not get an error, but a file of zero size. gpsbabel -t -i nmea -f log3.txt -o gpl -F log3.gpl </pre> </blockquote> <pre wrap=""><!----> The GPL module was broken. I've fixed it. The fix will appear in 1.2.3 which I'm in the process of closing down right now. Enjoy. RJL </pre> </blockquote> </body> </html> |
From: Ron P. <ro...@pa...> - 2004-05-03 04:20:17
|
At 10:30 PM 4/30/2004, Robert Lipe wrote: >Neither CSV nor HTML claim to support tracks, per > http://gpsbabel.sourceforge.net/capabilities.html >so it's not suprising to me that converting a track to those two formats >resulted in less than satisfying results. XCSV doesn't claim to support tracks, but it does support them, at least for writing: xcsv_data_write(void) { [...] waypt_disp_all(xcsv_waypt_pr); route_disp_all(xcsv_noop,xcsv_noop,xcsv_waypt_pr); track_disp_all(xcsv_noop,xcsv_noop,xcsv_waypt_pr); |