Modify ↓

Opened 9 months ago

Closed 5 months ago

#177 closed defect (fixed)

RTCM3.1 vs binex observables are differentes in BNC v.2.13

Reported by: ivonne@… Owned by: ivonne@…
Priority: normal Component: BNC
Version: Keywords:
Cc:

Description

I am getting streaming data from same Trimble NetR9 receiver but using different format, basically binex and RTCM 3.1.
The observable in rinex file that I get are differents and I can no t figure out the reason.
Could you help me, please?

Attachments (2)

MAR10570.24O_fromBinex​ (105.2 KB ) - added by ivonne@… 9 months ago.
MAR10570.24O.fromRTCM​ (167.4 KB ) - added by ivonne@… 9 months ago.
Rinex file created from RTC streaming

Download all attachments as: .zip

Change History (4)

by ivonne@…, 9 months ago

Attachment: MAR10570.24O_fromBinex​ added

by ivonne@…, 9 months ago

Attachment: MAR10570.24O.fromRTCM​ added

Rinex file created from RTC streaming

comment:1 by stuerze, 9 months ago

Owner: changed from stuerze to ivonne@…
Status: new → needinfo

Dear Ivonne,

I have no experiences with BINEX data so far but with respect to RTCM and RINEX I can say: Only the so called RTCM Multiple Signal Messages (MSM) allow a maximum compatibility with RINEX version 3/4. Lagacy RTCM messages as well as RINEX version 2 have limitations. In more detail MSM5 is able to transmit a full set of RINEX observables and MSM7 does the same with extended resolution. Maybe you can check your source format in more detail.

Best regrads, Andrea

comment:2 by stuerze, 5 months ago

Resolution: → fixed
Status: needinfo → closed

Modify Ticket

Change Properties
Action
as closed The owner will remain ivonne@….
The resolution will be deleted. Next status will be 'reopened'.

Add Comment
E-mail address and name can be saved in the Preferences .
Attachments ↑ Description ↑
 
Note: See TracTickets for help on using tickets.