Custom Query (104 matches)
Results (25 - 27 of 104)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#15 | fixed | Orbit corrections are missing when broadcast corrections are stored | ||
Description |
When i save the broadcast corections only the clock corrections are saved the orbit corrections are missing. |
|||
#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 |
|||
#36 | fixed | skeleton documentation | ||
Description |
bnchelp.pdf says: Note the following regulations regarding personal RINEX header skeleton files:
The following is a skeleton example for a RINEX file: OBSERVATION DATA M (MIXED) RINEX VERSION / TYPE DUND MARKER NAME 50212M003 MARKER NUMBER Either the example should include record of type "PGM / RUN BY / DATE" or else it should be removed from the list of regulations. |