31.07.2013, 15:19
Hello (1st time here 
!
I've been playing with the data download from my Qstarz GPS data logger and with different programs I've been getting all kind of possible versions and precisions of either NMEA or GPX data. It seemed I could resolve all this format issues with RouteConverter, but then I discovered a bug when parsing NMEA file with RouteConverter. First entry of NMEA file wasn't parsed properly because of rounding errors when comparing values. It also seems that the comparison of entry's time to cover all entries which belong together was missing.
So I cloned the git repository, modified the code to my wishes and now I can read the NMEA file, convert it to GPX and then back to NMEA. The new NMEA file will have the same entries regarding the position/altitude/speed as the original NMEA file (no rounding errors). This of course requires some violation of the length of the fraction digits, but I think most modern GPS programs (not the hardware, I guess) are adaptable to different fraction digits in values. The length of the fraction digits can be specified in preferences/registry and if not, they get the default/original values.
The modified code is available on https://github.com/mrihtar/RouteConverter. For the moment it requires the directives for Maven to ignore test errors/failures (I know this is bad and I will fix the tests as soon as I am sure everything works OK):
!I've been playing with the data download from my Qstarz GPS data logger and with different programs I've been getting all kind of possible versions and precisions of either NMEA or GPX data. It seemed I could resolve all this format issues with RouteConverter, but then I discovered a bug when parsing NMEA file with RouteConverter. First entry of NMEA file wasn't parsed properly because of rounding errors when comparing values. It also seems that the comparison of entry's time to cover all entries which belong together was missing.
So I cloned the git repository, modified the code to my wishes and now I can read the NMEA file, convert it to GPX and then back to NMEA. The new NMEA file will have the same entries regarding the position/altitude/speed as the original NMEA file (no rounding errors). This of course requires some violation of the length of the fraction digits, but I think most modern GPS programs (not the hardware, I guess) are adaptable to different fraction digits in values. The length of the fraction digits can be specified in preferences/registry and if not, they get the default/original values.
The modified code is available on https://github.com/mrihtar/RouteConverter. For the moment it requires the directives for Maven to ignore test errors/failures (I know this is bad and I will fix the tests as soon as I am sure everything works OK):
Code:
-Dmaven.test.failure.ignore=true -Dmaven.test.error.ignore=true