Custom Query (105 matches)
Results (40 - 42 of 105)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #23 | fixed | Time Shift using orbit and clock corrections in Post Processing Mode | ||
| Description |
I used BNC (version 2.8 and 2.10) in post processing mode to validate my own software i am currently working on. When i compared the orbits and clocks i found a difference which is caused by the use of the orbit and clock corrections. I attached an advanced log file of BNC. As you can see it seems that their is a shift of one epoch between the orbit and clock corrections and the epoch processed. So in the first epoch at 00:00:00 the corrections of 00:00:30 are applied. In case of the orbits this has almost no effect but it hase a big effect on the clocks. But maybe i am just getting something wrong. Best regards, Fabian |
|||
| #27 | fixed | hints with respect to RINEX 3.02 default header | ||
| Description |
message from fgnievinski@…: There are a few issues when saving RINEX observation files, though. (a) Two mandatory header lines are missing (RINEX version 3.02):
(b) The default skeleton includes observation codes that could benefit from some improvement, as follows: (b.1) C5, D5, L5, S5 are invalid, as they lack the third character, denoting the attribute (tracking mode or channel); most commonly it's "X", thus C5X, D5X, L5X, S5X. (b.2) The modernized GPS L2 signal ("L2C") is being reported under observation codes C2C, D2C, L2C, S2C. Actually, the "C" attribute is reserved for the C/A signal (as in C1C, D1C, L1C, S1C), whose transmission in the L2 band remains a technical possibility (according to Table 3-III, "Signal Configuration", of the GPS ICD), even in pre-modernized or legacy GPS satellites, although as far as I know it is very rare. The L2C signal normally is reported under C2X, D2X, L2X, S2X. (b.3) The legacy GPS L2 signal ("L2-P(Y)") is being reported under observation codes C2P, D2P, L2P, S2P. This is only true when anti-spoofing is disabled, which again is very rare. Under encrypted broadcast, observation codes C2W, D2W, L2W, S2W are employed for civilians (and C2Y, D2Y, L2Y, S2Y for military receivers). (b.4) In summary, may I suggest the following new default GPS observation codes: G 20 C1C L1C D1C S1C C1W L1W D1W S1W C2X L2X D2X S2X C2W SYS / # / OBS TYPES
These correspond to the majority of stations, see, e.g.: <http://www.bernese.unibe.ch/publist/2013/post/SL_euref2013_rinex3.pdf> |
|||
| #35 | fixed | Strange gap in QC plotting | ||
| Description |
Hi! I have one issue with BNC when I try to plot QC for hourly RINEX file (pls see in attachment). I have found gap in observation. Alsow, this gap appears every hourly session in different time. But, I have checked it using the teqc - file does not have any gaps. How this issue can be solved? I'm using Debian 8 64bit and try to do it with BNC v2.11 shared and v2.11 static. Thanks for your help! |
|||
