-
+
- BDS plots for L2 and L7, +
- Galileo plots for L1 and L5, +
- GPS plots for L1 and L2, +
- QZSS plots for L1 and L2, +
- GLONASS plots for L1 and L2, +
- SBAS plots for L1 and L5.
3.6.7 Set Edit Options - mandatory if 'Action' is set to 'Edit/Concatenate'
Once the 'Edit/Concatenate' action is selected, you have to 'Set Edit Options'. BNC lets you specify the RINEX version, a signal priority list when mapping RINEX Version 3 to Version 2, the sampling interval, begin and end of file, operator, observation types, comment lines, and marker, antenna, receiver details. Note that some specifications are only meaningful for RINEX Observation files but not for RINEX Navigation files. -
--
-
-
- The RINEX Version 2 format ignores signal generation attributes. Therefore, when converting RINEX Version 3 to Version 2 Observation files, BNC is forced to somehow map RINEX Version 3 to RINEX Version 2 although this can't be done in one-to-one correspondance. Hence we introduce a 'Version 2 Signal Priority' list of attributes (characters, forming a string) for mapping Version 3 to Version 2, see details in section 'RINEX Obserations/Version 2'. +
- The RINEX Version 2 format ignores signal generation attributes. Therefore, when converting RINEX Version 3 to Version 2 Observation files, BNC is forced to somehow map signals with attributes to signals without attributes although this can't be done in one-to-one correspondance. Hence we introduce a 'Version 2 Signal Priority' list of attributes (characters, forming a string) for mapping Version 3 to Version 2, see details in section 'RINEX Obserations/Version 2'.
- When converting RINEX Version 2 to Version 3 Observation files, the tracking mode or channel information in the (last character out of the three characters) observation code is left blank if unknown. This is a compromise, knowing that it is not in accordance with the RINEX Version 3 documentation. The default 'Version 2 Signal Priority' list of observation attributes when mapping RINEX Version 3 to Version 2 is 'CWPX_?', see again details in section 'RINEX Observations/Version 2'.
Once the 'Edit/Concatenate' action is selected, you have to 'Set Edit Options'. BNC lets you specify the RINEX version, a signal priority list when mapping RINEX Version 3 to Version 2, the sampling interval, begin and end of file, operator, observation types, comment lines, and marker, antenna, receiver details. Note that some of the specifications for editing and concatenation are only meaningful for RINEX Observation files but not for RINEX Navigation files. +
+ ++A note on converting RINEX Version 3 to RINEX Version 2 and vice versa: +
+ ++
-
+
Figure 9: Example for RINEX file editing with BNC in Post Processing mode.
+Figure 9: Example for RINEX file concatenation with BNC.
Figure 10: Example for creating RINEX quality check graphics output with BNC.
+Figure 10: Example for creating RINEX quality check analysis graphics output with BNC.
Figure 11: Example for satellite availability, elevation and PDOP plots as a result of a RINEX quality check with BNC.
+Figure 11: Example for satellite availability, elevation and PDOP plots as a result of a RINEX quality check analysis with BNC.
Figure 12: Sky plot examples for multipath.
+Figure 12: Sky plot examples for multipath, part of RINEX quality check analysis with BNC..
Figure 13: Sky plot examples for signal-to-noise ratio.
+Figure 13: Sky plot examples for signal-to-noise ratio, part of RINEX quality check analysis with BNC..
3.6.8 Command Line, No Window - optional