Custom Query (104 matches)
Results (25 - 27 of 104)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#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. |
|||
#37 | fixed | bnc --version | ||
Description |
suggestion: bnc --version could output the bnc version. |
|||
#38 | fixed | bnc --key onTheFlyInterval "": seems to be ignored | ||
Description |
I'm trying to make the command line input override the configuration file with regard to the onTheFlyInterval setting. The config file has onTheFlyInterval=1 day while at the prompt I'm calling bnc -nw --key onTheFlyInterval "". I faced this problem using bnc to convert ntrip to rinex. Files were no longer being saved to disk after midnight UTC. I could get the intended behavior (files being saved uninterruptedly across day boundaries) changing the original setting onTheFlyInterval=1 day to onTheFlyInterval= in the config file. I could NOT get the intended behavior having onTheFlyInterval=1 day in the config file and bnc -nw --key onTheFlyInterval "" in the command line. It seems that the empty value "" is being ignored by bnc or perhaps even discarded by the shell itself. |