[teqc] teqc and BINEX metadata

Lou Estey lou at unavco.org
Wed Apr 27 10:35:07 MDT 2005


All,

Here are some handy things to know using any recent teqc
if you are dealing with BINEX metadata (as defined on
http://binex.unavco.org/binex_record_00.html ) -- and if
you are not interested in BINEX, you might want to skip to
the end of email for a bonus surprise.

You can extract metadata from lots of sources (e.g. raw
data files, RINEX, existing teqc config file, etc.) and
build a set of BINEX config file options for inputting
into teqc, e.g.

teqc +bcf {other options as needed} rawfile > bnx.cfg

For example, here's what I got using a random Topcon TPS
file laying around:

[420] teqc +bcf CP_1P_1R.jps 2> /dev/null
+CA_L1
+msec_phs_adj
# BINEX 0x00: 2005 Apr 27 16:06:05.000
-B.c[omment] "BIT 2 OF LLI FLAGS DATA COLLECTED UNDER A/S CONDITION"
-B.c[omment] " SNR is mapped to RINEX snr flag value [0-9]"
-B.c[omment] "  L1 & L2:  2-19 dBHz = 1, 20-27 dBHz = 2, 28-31 dBHz = 3"
-B.c[omment] "           32-35 dBHz = 4, 36-38 dBHz = 5, 39-41 dBHz = 6"
-B.c[omment] "           42-44 dBHz = 7, 45-48 dBHz = 8, >= 49 dBHz = 9"
-B.c[omment] "pseudorange smoothing corrections not applied"
-B.ma[rker] "IPMCE"
-B.ma_n[umber] "IPMCE"
-B.SO "-Unknown-"
-B.SO_i[nstitution] "-Unknown-"
-B.at[ype] "JPSLEGANT_E"
-B.an[umber] "-Unknown-"
-B.rt[ype] "TPS E_GGD"
-B.rn[umber] "AEQ818WRNK0"
-B.rf[irmware] "2.3 Nov,14,2002 SW"
-B.px[WGS84xyz,m] 2855648.7726 2196510.1459 5245815.4073
-B.pg[eo,ddm] 55.699090764 37.566792505 218.6661
# note: IGS log format= +554156.7268 +373400.4530 218.6661

(note: lines starting with a '#' are a comment.)
If you capture the output as a file, you could use it to build
a BINEX 0x00 metadata file:

[426] teqc +bcf CP_1P_1R.jps 2>/dev/null > bnx.cfg
[427] teqc +binex - -config bnx.cfg 2> /dev/null > 0x00.bnx

(note: "+binex -" means "output as BINEX, using the default record types")

and you can also "see" what is in BINEX file 0x00.bnx:

[428] teqc +bcf 0x00.bnx 2>/dev/null
# BINEX 0x00: 2005 Apr 27 16:12:15.000
-B.c[omment] "BIT 2 OF LLI FLAGS DATA COLLECTED UNDER A/S CONDITION"
-B.c[omment] " SNR is mapped to RINEX snr flag value [0-9]"
-B.c[omment] "  L1 & L2:  2-19 dBHz = 1, 20-27 dBHz = 2, 28-31 dBHz = 3"
-B.c[omment] "           32-35 dBHz = 4, 36-38 dBHz = 5, 39-41 dBHz = 6"
-B.c[omment] "           42-44 dBHz = 7, 45-48 dBHz = 8, >= 49 dBHz = 9"
-B.c[omment] "pseudorange smoothing corrections not applied"
-B.ma[rker] "IPMCE"
-B.ma_n[umber] "IPMCE"
-B.SO "-Unknown-"
-B.SO_i[nstitution] "-Unknown-"
-B.at[ype] "JPSLEGANT_E"
-B.an[umber] "-Unknown-"
-B.rt[ype] "TPS E_GGD"
-B.rn[umber] "AEQ818WRNK0"
-B.rf[irmware] "2.3 Nov,14,2002 SW"
-B.px[WGS84xyz,m] 2855648.7726 2196510.1459 5245815.4073
-B.pg[eo,ddm] 55.699090764 37.566792505 218.6661
# note: IGS log format= +554156.7268 +373400.4530 218.6661

or you can dissect the BINEX file with an octal dump and compare
the results with the 0x00 specification in the URL above.

------------

Bonus surprise:

One interesting side effect is that you access to a nice little
converter between WGS-84 XYZ positions (in meters) to the equivalent
in geographical coordinates (lat lon height):

[429] teqc +bcf -B.px 2855648.7726 2196510.1459 5245815.4073
# BINEX 0x00: 2005 Apr 27 16:18:46.000
-B.px[WGS84xyz,m] 2855648.7726 2196510.1459 5245815.4073
-B.pg[eo,ddm] 55.699090764 37.566792506 218.6661
# note: IGS log format= +554156.7268 +373400.4530 218.6661

[430] teqc +bcf -B.pg 55.699090764 37.566792506 218.6661
# BINEX 0x00: 2005 Apr 27 16:20:35.000
-B.px[WGS84xyz,m] 2855648.7726 2196510.1459 5245815.4073
-B.pg[eo,ddm] 55.699090764 37.566792506 218.6661
# note: IGS log format= +554156.7268 +373400.4530 218.6661

As an extra bonus, you also get the lon/lat/height in
the format required for IGS logs in the last comment.  (This part
was added by request from our UNAVCO field engineers, so please
thank them.)

--lou



More information about the teqc mailing list