[teqc] Septentrio SBF translation - blank header detail

Sajan sajanmushini at gmail.com
Wed May 16 06:53:02 MDT 2018


Hi Neville

If the aim is just rinex creation, just wondering if you have used the
rxtools from Septentrio itself? It has sbf2rinex executable.

I use that and if I need to edit the header, then I just use teqc on the
rinex file.

Regards
Sajan

On Tue, May 15, 2018, 22:28 , <teqc-request at postal.unavco.org> wrote:

> Send teqc mailing list submissions to
>         teqc at postal.unavco.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         https://postal.unavco.org/mailman/listinfo/teqc
> or, via email, send a message with subject or body 'help' to
>         teqc-request at postal.unavco.org
>
> You can reach the person managing the list at
>         teqc-owner at postal.unavco.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of teqc digest..."
>
>
> Today's Topics:
>
>    1. Septentrio SBF translation - blank header detail (Neville Palmer)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 16 May 2018 04:28:24 +0000
> From: Neville Palmer <N.Palmer at gns.cri.nz>
> To: "teqc at postal.unavco.org" <teqc at postal.unavco.org>
> Subject: [teqc] Septentrio SBF translation - blank header detail
> Message-ID:
>         <
> SY3PR01MB20263D4D742F3DE624C18D83AB920 at SY3PR01MB2026.ausprd01.prod.outlook.com
> >
>
> Content-Type: text/plain; charset="windows-1257"
>
> I am attempting to generate RINEX data from Septentrio PolaRx5 SBF files
> that were recently recorded during 2 to 5 day campaign observations.
>
> This is the first time we have used Septentrio receivers and I am having
> issues with consistently populating the RINEX header information with the
> receiver information contained in the SBF file.
>
> I am using teqc version 2018Mar15 and have tried using both Windows 10 and
> a Linux with the same result.
>
> The following are examples of my results.
>
> The following command:
> teqc ++config 19270860.18_
> Correctly included the following in the output:
> -O.s[ystem] G
> -O.r[un_by] " "
> -O.o[perator] "GNS"
> -O.ag[ency] "GNS"
> -O.mo[nument] "GNS50"
> -O.mn "GNS50"
> -O.rn "3022413"
> -O.rt "SEPT POLARX5"
> -O.rv "5.1.2"
> -O.an "-Unknown-"
> -O.at "-Unknown-"
> -O.px[WGS84xyz,m] -4512138.7928 746727.7067 -4433251.1139
> -O.pe[hEN,m] 0.0000 0.0000 0.0000
> -O.leap 18
>
> However if I use the following command:
>                 teqc 19270860.18_ > 19270860.18o
> None of the above detail is included in the resulting RINEX header with
> most of the fields showing values ?-Unknown-? and all zeros for the approx.
> position xyz, as shown below:
>      2.11           OBSERVATION DATA    M (MIXED)           RINEX VERSION
> / TYPE
> teqc  2018Mar15                         20180516 03:21:16UTCPGM / RUN BY /
> DATE
> Linux2.6.32-573.12.1.el6.x86_64|x86_64|gcc|Win64-MinGW64|=+ COMMENT
> BIT 2 OF LLI FLAGS DATA COLLECTED UNDER A/S CONDITION       COMMENT
> -Unknown-                                                   MARKER NAME
> -Unknown-           -Unknown-                               OBSERVER /
> AGENCY
> -Unknown-           -Unknown-           -Unknown-           REC # / TYPE /
> VERS
> -Unknown-           -Unknown-                               ANT # / TYPE
>         0.0000        0.0000        0.0000                  APPROX
> POSITION XYZ
>         0.0000        0.0000        0.0000                  ANTENNA: DELTA
> H/E/N
>      1     1                                                WAVELENGTH
> FACT L1/2
>      7    L1    L2    C1    P1    P2    S1    S2            # / TYPES OF
> OBSERV
> SNR is mapped to RINEX snr flag value [0-9]                COMMENT
>   L1 & L2: min(max(int(snr_dBHz/6), 0), 9)                  COMMENT
>   2018     3    27     0     0    0.0000000     GPS         TIME OF FIRST
> OBS
>     18                                                      LEAP SECONDS
>                                                             END OF HEADER
>
> If I instead use the tbin option as follows:
>                 teqc -tbin 1h TEMP +obs + 19270860.18
> The header of the first RINEX file generated looks identical to the
> example above. The second and all subsequent files have complete and
> correct header information similar to the following:
>      2.11           OBSERVATION DATA    M (MIXED)           RINEX VERSION
> / TYPE
> teqc  2018Mar15                         20180516 03:19:47UTCPGM / RUN BY /
> DATE
> Linux2.6.32-573.12.1.el6.x86_64|x86_64|gcc|Win64-MinGW64|=+ COMMENT
> BIT 2 OF LLI FLAGS DATA COLLECTED UNDER A/S CONDITION       COMMENT
> GNS50                                                       MARKER NAME
> GNS50                                                       MARKER NUMBER
> GNS                 GNS                                     OBSERVER /
> AGENCY
> 3022413             SEPT POLARX5        5.1.2               REC # / TYPE /
> VERS
> -Unknown-           -Unknown-                               ANT # / TYPE
> -4512138.7928   746727.7067 -4433251.1139                  APPROX POSITION
> XYZ
>         0.0000        0.0000        0.0000                  ANTENNA: DELTA
> H/E/N
>      1     1                                                WAVELENGTH
> FACT L1/2
>      7    L1    L2    C1    P1    P2    S1    S2            # / TYPES OF
> OBSERV
>     18                                                      LEAP SECONDS
> SNR is mapped to RINEX snr flag value [0-9]                COMMENT
>   L1 & L2: min(max(int(snr_dBHz/6), 0), 9)                  COMMENT
>   2018     3    27     1     0    0.0000000     GPS         TIME OF FIRST
> OBS
>                                                             END OF HEADER
>
> Is it possible to consistently have teqc correctly populate the header
> information of the first RINEX file generated using the information
> contained in the raw SBF file?
>
> A little further investigation has shown that for 3 SBF files (out of 56
> files recorded at 13 stations) the header information does get included in
> the RINEX file when using just a basic ?teqc <filename>? command. All the
> other 53 files resulted in ?-Unknown-? values in the headers. The three
> successful files all came from the same receiver (all data was recorded
> with two identically configured receivers). These 3 files were all the
> first file of a multi day occupation. 5 other stations were observed with
> the same receiver. The three ?successful? files still had all zeros for the
> approx. position xyz.
>
> Thanks
> Neville
>
> Neville Palmer  I  Geodetic Surveyor
> GNS Science  I  Te P? Ao
> 1 Fairway Drive, Avalon, Lower Hutt 5010
> PO Box 30 368, Lower Hutt 5040, New Zealand I Ph +64 4 570 1444
> DDI +64 4 570 4714  I  Mob +64 27 221 8845
> Web: http://www.gns.cri.nz/  I  Email: n.palmer at gns.cri.nz<mailto:
> n.palmer at gns.cri.nz>
>
> Notice: This email and any attachments are confidential and may not be
> used, published or redistributed without the prior written consent of the
> Institute of Geological and Nuclear Sciences Limited (GNS Science). If
> received in error please destroy and immediately notify GNS Science. Do not
> copy or disclose the contents.
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> http://postal.unavco.org/pipermail/teqc/attachments/20180516/76e94eaa/attachment.html
> >
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> teqc mailing list
> teqc at postal.unavco.org
> https://postal.unavco.org/mailman/listinfo/teqc
>
> ------------------------------
>
> End of teqc Digest, Vol 168, Issue 4
> ************************************
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://postal.unavco.org/pipermail/teqc/attachments/20180516/4cbf6d47/attachment-0001.html>


More information about the teqc mailing list