Modify

Opened 12 months ago

Closed 7 months ago

Last modified 6 months ago

#110 closed defect (fixed)

Missing GLONASS slot numbers in RINEX

Reported by: ljbade Owned by: stuerze
Priority: normal Component: BNC
Version: BNC 2.2 Keywords:
Cc:

Description

I have BNC 2.12.6 generating RINEX 3 observation files for a number of stations that have RTCM MSM 4 streams.

The manual indicates that in order to decode the slot number I need to add an ephemeris stream with message 1020. I have added the RTCM3-MGEX IGS stream for this.

I can see I am getting GLONASS ephemerides as BNC will write out the RINEX 3 navigation file with this data.

However all my observation files have an empty GLONASS slot header:

0 GLONASS SLOT / FRQ #

Attachments (0)

Change History (5)

comment:1 Changed 12 months ago by stuerze

Thank you very much for this hint. I will try to solve that issue within the next upcomming version 2.12.7.

Best regards, Andrea

comment:2 Changed 7 months ago by stuerze

The information regarding GLONASS SLOT / FRQ # is now part of our skleton files and therefore part of the RINEX file header if the stream is comming from one of our Casters:
for example www.igs-ip.net, www.euref-ip.net.

comment:3 Changed 7 months ago by stuerze

Resolution: fixed
Status: newclosed

comment:4 Changed 7 months ago by ljbade

I'm a bit confused. Are you saying that we need to set up the correct GLONASS slot numbers in the skeleton file?

comment:5 Changed 6 months ago by stuerze

Not necessarily. We have done it for IGS, EUREF and MGEX stations, which are available on our broadcasters. BNC is able to scan the incoming RTCM messages (activation within the Misc panel) and a lot of informations per station are written out during this. For example the observation types, the antenna type, and the GLONASS slots.

19-05-09 07:29:08 ========== Start BNC v2.12.8 (LINUX) ==========
19-05-09 07:29:08 Panel 'Feed Engine' active
19-05-09 07:29:08 Panel 'Miscellaneous' active
19-05-09 07:29:08 ABMF00GLP0: Get data in RTCM 3.x format
..
19-05-09 07:29:11 ABMF00GLP0: Observation Types: R     6   C1C L1C S1C C2C L2C S2C
19-05-09 07:29:11 ABMF00GLP0: Observation Types: G     6   C1C L1C S1C C2W L2W S2W
19-05-09 07:29:11 ABMF00GLP0: GLONASS Slot:Freq R05:1
..
19-05-09 07:29:20 ABMF00GLP0: GLONASS Slot:Freq R05:1 R06:-4
.. 
19-05-09 07:29:30 ABMF00GLP0: Antenna descriptor TRM57971.00     NONE 
19-05-09 07:29:30 ABMF00GLP0: ARP (ITRF) X 2919786.4477 m
19-05-09 07:29:30 ABMF00GLP0: ARP (ITRF) Y -5383745.1776 m
19-05-09 07:29:30 ABMF00GLP0: ARP (ITRF) Z 1774604.7345 m
19-05-09 07:29:30 ABMF00GLP0: Antenna height above marker 0.0000 m
19-05-09 07:29:30 ABMF00GLP0: Receiver descriptor SEPT POLARX5 
19-05-09 07:29:30 ABMF00GLP0: GLONASS Slot:Freq R05:1 R06:-4 R09:-2
..
19-05-09 07:29:40 ABMF00GLP0: GLONASS Slot:Freq R05:1 R06:-4 R09:-2 R15:0
.. 
19-05-09 07:29:50 ABMF00GLP0: GLONASS Slot:Freq R05:1 R06:-4 R09:-2 R15:0 R16:-1
..
19-05-09 07:30:00 ABMF00GLP0 Observations: Mean latency 0.87 sec, min 0.57, max 2.92, rms 0.35, 51 epochs
..
19-05-09 07:30:00 ABMF00GLP0: Antenna descriptor TRM57971.00     NONE 
19-05-09 07:30:00 ABMF00GLP0: ARP (ITRF) X 2919786.4477 m
19-05-09 07:30:00 ABMF00GLP0: ARP (ITRF) Y -5383745.1776 m
19-05-09 07:30:00 ABMF00GLP0: ARP (ITRF) Z 1774604.7345 m
19-05-09 07:30:00 ABMF00GLP0: Antenna height above marker 0.0000 m
19-05-09 07:30:00 ABMF00GLP0: Receiver descriptor SEPT POLARX5 
19-05-09 07:30:00 ABMF00GLP0: GLONASS Slot:Freq R05:1 R06:-4 R09:-2 R15:0 R16:-1 R20:2
..
19-05-09 07:30:10 ABMF00GLP0: GLONASS Slot:Freq R05:1 R06:-4 R09:-2 R15:0 R16:-1 R20:2 R21:4
..
19-05-09 07:30:20 ABMF00GLP0: GLONASS Slot:Freq R04:6 R05:1 R06:-4 R09:-2 R15:0 R16:-1 R20:2 R21:4

To get all required informations, takes a while. Hence, these informations will be extracted only from the log file after a certain period of time and filled into our skeleton files.

The Caster has STReams, and these streams are part of a NETwork. Wthin the NET entry in the casters sourcetable a link is mentioned, where the skeleton of the respective Network can be found.

STR;ABMF00GLP0;Les-Abymes;RTCM 3.1;1004(1),1006(30),1008(30),1012(1),1013(30),1019,1020,1033(30);2;GPS+GLO;IGS;GLP;16.26;-61.53;0;0;SEPT POLARX5;none;B;N;2600;rgp-ip.ign.fr:2101/ABMF1(1)
NET;IGS;IGS;B;N;https://igs.bkg.bund.de/root_ftp/NTRIP/streams/streamlist_igs-ip.htm;https://igs.bkg.bund.de:443/root_ftp/IGS/station/rnxskl/;http://register.rtcm-ntrip.org;none

BNC download the skl files from there and has informations like observations types and GLONASS slots available to write a correct header.

By the way, the GLONASS slots are defined as optional within the RINEX documentation.
Hope, that helps.

Modify Ticket

Change Properties
Action
as closed The owner will remain stuerze.
The resolution will be deleted.

Add Comment


E-mail address and name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.