Navigation
Neue Forenbeiträge
Newsfeeds
Export csv and gpx
The logger is well, the software too. But the output file have to be in a way to import in other Software.
For example Pathaway oder KDR (freeware).
Unfortunately the import is not easy, because interface is no standard. Therefore it is necessary to adjust the export file.
For example csv
MTK747-CSV-Export
INDEX,RCR,DATE,TIME,LATITUDE,N/S,LONGITUDE,E/W,HEIGHT(m),SPEED(km/h),PDOP,HDOP,VDOP,
55746,B,2010/03/15,06:15:43.000,49.038997,N,8.362408,E,162.931,67.790,1.32,0.90,0.96,
55781,B,2010/03/15,06:16:51.000,49.054425,N,8.368599,E,155.533,103.845,1.31,0.90,0.95,
55818,B,2010/03/15,06:18:04.000,49.063809,N,8.390870,E,153.466,104.479,1.37,0.93,1.00,
and so on
Import KDR GPS Tracker
55776,49.052176,8.367576,155.702
55779,49.053688,8.368202,155.393
55784,49.055859,8.369517,155.209
and so on
It should be possible to reformating and sequencing the export-file according to import-interface.
Analog the gpx-export.
Need a basic waypoint-file => <wpt lat, lon> and <ele> - Nothing else
Need a basic track => <trk> with only one <trkseg> and many <trkpt lat, lon> <ele>
The header is also a problem. Many programs need a special header. Some programs need no header. Only <gpx>, <trk>, <trkseg> and <trkpt lat, lon>
It should be possible to reformating and sequencing the export-file according to import-interface.
Best Regards
Skater
- Anmelden um Kommentare zu schreiben
Hi It is currently possible
Hi
It is currently possible to limit the output fields in the 'Output Settings'. Select only the fields you want to see.
I try to be as 'standard' as possible.
One solution could be to add some type to the pull-down menu with predefined output settings (somewhat like I do for the upload to OSM which is a tuned GPX file).
gpx - sorry - I find out my
gpx - sorry - I find out my mistakes
Filters - Trackpointfilter => trkpt
or / and
Filters - Waypointfilters => wpt
gpx => Full-Output
gpx for osm upload => basic output
So many filters and checkboxes!
csv
Advanced File Setting
CSV File Setting => Same as NMEA-File-Setting
MTK-nmea-file
$GPGGA,061517.000,4902.154896,N,00821.687723,E,,8,1.19,89.934,M,48.0,M,,*57
$GPRMC,061519.000,,4902.168291,N,00821.691738,E,22.605,,150310,,,A*3D
$GPGGA,061519.000,4902.168291,N,00821.691738,E,,8,1.19,90.510,M,48.0,M,,*54
$GPRMC,061527.000,,4902.211342,N,00821.706823,E,19.369,,150310,,,A*3F
and so on
Not compatible with GPSbabel or Routeconverter
Why?
GPSbabel-output-nmea
$GPRMC,090524.000,V,4636.388,N,01316.653,E,0.00,0.00,150210,,*18
$GPGGA,090524.000,4636.388,N,01316.653,E,0,00,0.0,781.946,M,0.0,M,,*63
$GPRMC,090526.000,V,4636.369,N,01316.636,E,0.00,0.00,150210,,*16
$GPGGA,090526.000,4636.369,N,01316.636,E,0,00,0.0,795.522,M,0.0,M,,*66
look similar
Best Regards
Skater
Hi Possibly GPSbabel or
Hi
Possibly GPSbabel or Routeconverter do not like that some fiels are present or missing.
The NMEA standard says that fields can stay empty. So in GPRMC, 'V' is missing in BT747 output because the value is not really known or valid in itself and 'A' is present at the end. GPGGA is probably ok, but field is missing in BT747 after 'E'.
For GPS babel, I am willing to add some kind of compatibility mode. We would have to check which field is the issue.
All the filters and stuff are there for tuning because as you notice, the tools out there are quite diverse and requests specific.
Also when you uncheck values in the output settings box, these will no longer appear in the NMEA either!