Modify ↓

Opened 2 months ago

Last modified 2 months ago

#177 needinfo defect

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@… 2 months ago.
MAR10570.24O.fromRTCM​ (167.4 KB ) - added by ivonne@… 2 months ago.
Rinex file created from RTC streaming

Download all attachments as: .zip

Change History (3)

by ivonne@…, 2 months ago

Attachment: MAR10570.24O_fromBinex​ added

by ivonne@…, 2 months ago

Attachment: MAR10570.24O.fromRTCM​ added

Rinex file created from RTC streaming

comment:1 by stuerze, 2 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

Modify Ticket

Change Properties
Action
as needinfo The owner will remain ivonne@….
as The resolution will be set. Next status will be 'closed'.
to The owner will be changed from ivonne@… to the selected user. Next status will be 'assigned'.
as duplicate The resolution will be set to duplicate. Next status will be 'closed'. The specified ticket will be cross-referenced with this ticket.
The owner will be changed from ivonne@… to anonymous. Next status will be 'accepted'.

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