Example 'unicvs' log (where name is actually GPS seconds): -- lat,long,alt,name 49.66167756437,-114.59122054052,1434.1903,584656.000
BESTPOSA,COM1,0,65.0,FINESTEERING,1518,584656.000,00040000,6145,3642;SOL_COMPUTED,WAAS,49.66167756437,-114.59122054052,1434.1903,-14.8000,WGS84,6.1673,2.6 840,9.4065,"135",4.000,0.000,12,4,0,0,0,2,0,1*9c519c8e I think you also need the week number which seems to be 1518, which fits for early 2009. To get unix seconds, it should just be unix timeval of beginning of GPS epoch + 86400 * 7 * week + gpstime + (19 - 34). The last term is converting to TAI and then UTC. These might be useful: http://www.gpstk.org/doxygen/classgpstk_1_1Epoch.html GPS epoch is 1980-01-06 0000 UTC http://tycho.usno.navy.mil/gpstt.html gpsd source say GPS epoch is 315964800 So poblano gdt 574 ~ > echo 1518 584656 | awk '{ print 315964800 + $1 * 86400 * 7 + $2 - 15}' 1234635841 poblano gdt 575 ~ > date -u -r 1234635841 Sat Feb 14 18:24:01 UTC 2009 poblano gdt 576 ~ > Is that right?
pgpWy4fPpDazZ.pgp
Description: PGP signature
_______________________________________________ talk mailing list [email protected] http://lists.openstreetmap.org/listinfo/talk
