Zime zone makes no sense for NMEA
Brought to you by:
mdeweerd
Menu
▾
▴
#4 Zime zone makes no sense for NMEA
When creating a GMAP file, the time zone (e.g. UTC+1) makes sense,
but when creating a NMEA file, the time zone should be ignored, as NMEA times are always UTC.
And IMO the time zone should also be ignored, when creating a CSV file, as this should contain the raw data.
Logged In: YES
user_id=149951
Originator: NO
I can understand your argument for the NMEA file. Maybe I should use the 'GPX UTC Offset 0' setting to determine what the user wants (and change the label for this setting).
For the CSV file, this is less obvious. The end user might want to see the local time in this file. As it is not really standardize, the reasoning as for the NMEA file does not really hold.
In the end, you can always get a UTC offset of 0 ;-).
You could start a thread on the discussion forum to see what other users think for the CSV file.
Logged In: YES
user_id=1169208
Originator: YES
I am working like this:
* Convert BIN to CSV.
* Edit the CSV file to my needs (i.e. removing lines, which I don't need).
* Convert CSV to NMEA and GMAP.
And for some of these conversions (BIN->CSV, CSV->NMEA) I have to set UTC+0,
but when converting to GMAP I have to set my local time zone.
And I often forget to change this.
Maybe the command line mode (see my other request) could provide the possibility to specify the time zone.
Then I could create BAT files with commands like these:
CALL run_rxtx -TZ=UTC+0 x.bin x.csv
CALL run_rxtx -TZ=UTC+0 x.csv x.nmea
CALL run_rxtx -TZ=UTC+1 x.csv x.html
This is now partially done as it is configureable in the command line interface.