getub()
LEAD-IN of 0x8F01, 0x8F02 - same as SiRF MID 0x5D SID 1,2
fix indentation
LEAD-IN of 0x82 is part of SiRFbinary MID 64 (0x40) - Nav Library, SID 1 GPS Data
LEAD-IN of 0x8501 is part of SiRFbinary MID 8 (0x08) - 50 BPS data subframe, extract leap-second from this
LEAD-IN of 0x8e02 equivalent to SiRFbinary MID 92 (0x5C) - CW Controller Output, SID 2! Maybe 0x8e01 to 0x5c/0x01?
txt update
Merge branch 'master' of https://github.com/hrvach/gsd4t_parser
LEAD-IN of 0x85xx is (sometimes multiple) part of SiRFbinary MID 8 (0x08) - 50 BPS data subframe, extract leap-second from this
reintroduce float.pl for testing coordinates
try permutations
nicer output
SiRF MID 0x02 more detailed info
use Geo::ECEF to convert ECEF x,y,z to lat,lon,height. result seems to not be perfect, we get:
lat=43.7248849001017, lon=15.7995159586422, HAE=54.9794641761109
gpsd(8) prints just lat=43.72 lon=15.80 alt=13.29
but SLC debug gives: 43.724897,15.799583,55.54
OSP MID 0x02 GPS time parse (partially)
FIXMEs
Merge pull request #3 from mnalis/master

Merge :)