search

REC-SPb-ETU / Gpstk-old

Other
3 stars 1 forks source link

Rinex nav codesL2 , double vs short #9

Closed jonyrock closed 9 years ago

jonyrock commented 9 years ago

see ftp://igscb.jpl.nasa.gov/pub/data/format/rinex211.txt table a4 and this https://github.com/jonyrock/Gpstk/blob/38f355122a8012f02eec9cf62d376b4e04294869/dev/ext/lib/FileHandling/RINEX3/Rinex3NavData.hpp#L170

So in gpstk we use short to store double.

@eugenyk what do you think ?

jonyrock commented 9 years ago

@eugenyk same thing with L2Pdata fitInt IODE IODC

But looks like this params are always zeros

jonyrock commented 9 years ago

It is our fault actually.

eugenyk commented 9 years ago

@jonyrock According to the standard and http://stcorp.nl/coda/doc/codadef/codadef-rinex.html - they are double. I think http://binex.unavco.org/binex_record_01.html can give us understanding of values thresholds and RtkLib https://github.com/tomojitakasu/RTKLIB/blob/master/src/rtklib.h tells us that they are int, not short