[teqc] extraction of XYZ data

Lou Estey lou at unavco.org
Fri Feb 1 10:58:04 MST 2019


hi Bill,

Whoa, let's back up here.  It sounds like you are mixing up capabilities in teqc.

The '+psp' option, discussed in the tip of week 1938,
https://postal.unavco.org/pipermail/teqc/2017/002231.html
is for extracting and displaying the differential ENU position for a starting
reference position from certain raw data formats if that format contains the
pertinent record type.  Currently, the list of formats and records supported are:

      o BINEX record 0x05 (defined June-August 2016)
      o Trimble .tgd record 29 and RT27 streaming 0x57-7
      o Septentrio Binary Format (SBF) messages 4006, 4007 (and older 5903, 5904)
      o Leica MDB 10 & 110, 11 & 111, 12 & 112 (initial reference position only), 13 & 113 (no clock info)
      o Topcon TPS and Javad JPS: [rE], [rV], [rT]; [ST], [TO], [DO], [PG], [PO], [PV], [VE], [VG]
      o u-blox UBX-NAV-SOL (0x0106) and UBX-NAV-PVT (0x0107): no clock info yet

What will be in the next release (and not in previous releases) will be an initial
line when using '+psp' that shows the reference position being used displayed in XYZ.

The '+psp' option is no use at all if you have RINEX.

However, you can use teqc's point-position calculation, if you only
want approximate position, during qc, which can now be done on RINEX
(as in the past) or when doing a qc on raw data files.  This requires
navigation messages for all SV systems that will be included in the
point-position calculations, and then using '+qc' (or '+qcq') along
with the '+eepx' option (for output in XYZ), as discussed in tip of
week 2026, https://postal.unavco.org/pipermail/teqc/2018/002564.html
With '+eepx' (or '+eepg' for outputting geographic coordinates) one
gets the full XYZ (or lat/lon/height) for each epoch (assuming good
and complete data).  And, as discussed in that tip, if the antenna is
moving significantly, then other options need to be included during the qc.

But, if your want reasonably precise XYZ, you should really just
post-process the RINEX file.

Hope this helps.

cheers,
--lou

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Louis H. Estey, Ph.D.              office:  [+001] 303-381-7456
UNAVCO, 6350 Nautilus Drive           FAX:  [+001] 303-381-7451
Boulder, CO  80301-5554            e-mail:  lou  unavco.org

"If the universe is the answer, what is the question?"
                                                -- Leon Lederman
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

On 01-Feb-19 10:07 AM, William Funderburk wrote:
> All,
> 
> I am trying to extract XYZ data from spliced Rinex files to model crustal deformation. Lou mentioned this feature would be added in the next 
> release of teqc using the +psp command. But until then, is there a way to derive it using the most recent release? Also, when is the new 
> release with this added feature come out?
> 
> Thanks,
> 
> Bill
> 
> William R. Funderburk
> 
> Field Applications Scientist


More information about the teqc mailing list