AI Assistant
Notifications
Clear all

Split a obs file

23 Posts
9 Users
0 Reactions
1,809 Views
Williwaw
(@williwaw)
Posts: 3614
Member
Translate
English
Spanish
French
German
Italian
Portuguese
Russian
Chinese
Japanese
Korean
Arabic
Hindi
Dutch
Polish
Turkish
Vietnamese
Thai
Swedish
Danish
Finnish
Norwegian
Czech
Hungarian
Romanian
Greek
Hebrew
Indonesian
Malay
Ukrainian
Bulgarian
Croatian
Slovak
Slovenian
Serbian
Lithuanian
Latvian
Estonian
 

John Hamilton, post: 400574, member: 640 wrote: I also use a batch file. I typically end up with trimble T01 or T02 files. I have a program that will create a batch file with three entries for each .t02 or .t01 file, so I run the program from the command line, it creates a batch file in the directory where the files are, then I run the batch file from the command line.

here are the lines in the batch file (3 for each file):
runpkr00 -g -d 81103220.T01 (this converts the .T01 file to a .tgd file, which contains GPS and GLONASS)
runpkr00 -d 81103220.T01 (this converts the .T01 file to a .dat file, which only has GPS)
teqc.exe 81103220.tgd >81103220.16o (this converts the .tgd file to a rinex file, which has GLONASS and GPS)

Feel free to share any tips or tricks for parsing Rinex files using Notepad++. Like Loyal commented, I've managed to mangle my fair share and this is a subject I'm still much the student on. I usually don't have to delve into it until I've managed to get myself in the predicament where I need to do surgery to try and salvage something useful from my data rather than making a return trip which isn't always in the cards.


Just because I'm paranoid, doesn't mean they aren't out to get me.

 
Posted : November 21, 2016 5:10 pm
geeoddmike
(@geeoddmike)
Posts: 1556
Member
Translate
English
Spanish
French
German
Italian
Portuguese
Russian
Chinese
Japanese
Korean
Arabic
Hindi
Dutch
Polish
Turkish
Vietnamese
Thai
Swedish
Danish
Finnish
Norwegian
Czech
Hungarian
Romanian
Greek
Hebrew
Indonesian
Malay
Ukrainian
Bulgarian
Croatian
Slovak
Slovenian
Serbian
Lithuanian
Latvian
Estonian
 

https://www.unavco.org/software/data-processing/teqc/tutorial/tutorial.html#sec_13

I am always wary when editing long text files fearing a stray blank space or one-character indent. As others mention teqc is the tool to use. My link above is to the specific command line syntax.

Now you just need to find out how to open a command prompt and get teqc and the RINEX file in the same directory and other once commonly known manipulations. The command line can be powerful.


 
Posted : November 21, 2016 7:18 pm
paul-in-pa
(@paul-in-pa)
Posts: 6034
Member
Translate
English
Spanish
French
German
Italian
Portuguese
Russian
Chinese
Japanese
Korean
Arabic
Hindi
Dutch
Polish
Turkish
Vietnamese
Thai
Swedish
Danish
Finnish
Norwegian
Czech
Hungarian
Romanian
Greek
Hebrew
Indonesian
Malay
Ukrainian
Bulgarian
Croatian
Slovak
Slovenian
Serbian
Lithuanian
Latvian
Estonian
 

Good to see a resolution without me.

A bit of a busy weekend. Thursday went overtime in another office. Friday 198 mile roundtrip for a full day survey in he field, go jammed up on I-80 with a fatality blockage, had to backtrack and come home a different route. Saturday was on stand at 6:20 AM for archery hunting with my son, home for lunch, resolved Friday's field work, off to our nephew's for a TV tailgate and watch Penn State over Rutgers. Had to rough it for coffee, my nephew had barely a few drops left in the Courvoisier VSOP I had given him for his birthday and we had to settle for Makers Mark. The football game was continuing in freezing slushy rain and then the Big Ten network went off the air for most of 4th quarter, I would say probably due to the weather conditions at the game sight. Sunday morning at my wife's church by 7:30 AM to cook for a pancake breakfast, cleanup by 12:30. Home to wrap our grandson's birthday presents, off to our son's for the party. From there to my cousin's, recovering from pancreatic cancer surgery last week, then we drive her brother to the airport for flight back to Florida. Stopped at another cousins on way home for a water delivery, she does not drive. Did not really get to read the board last night, today was a longer than normal office day elsewhere as I helped another surveyor clean out his schedule before long Thanksgiving/rifle deer season break.

Paul in PA

As to teqc, I just got this email:

"The 2016Nov7 version has been available for almost two week now (as well as the earlier beta
version that was made available for the most popular builds in mid October).

Has anyone encountered any problems?

Next week, I'll summarize four bugs I know of, three of which were found and fixed this week.

cheers,
--lou

On 07-Nov-16 09:52 AM, Lou Estey wrote:dear All,

The next official version -- 2016Nov7 -- of teqc is on-line:
http://www.unavco.org/software/data-processing/teqc/teqc.html#executables
As usual, save a copy of your current executable in case there is some unexpected problem
with the new executable.

The main changes and fixes since 2016 Apr 1 are given in detail at
http://www.unavco.org/software/data-processing/teqc/log/log.html#2016Nov07
but here's a very brief summary about this release:

- is ready for the next UTC leap second insertion, which will occur at the end of Dec 2016

- does not require the '-max_rx_SVs' option regardless of the number of SVs being tracked
when reading any of the following raw data formats (i.e. all of the following formats include
a CRC or checksum for each record or message):
o BINEX
o Ashtech MBEN stream, R-file, and U-file
o CMC binary
o Javad JPS
o Leica LB2 and MDB
o Motorola Oncore
o NavCom SF 2050
o Rockwell Zodiac
o Septentrio Binary Format (SBF)
o Topcon TPS
o Trimble RT17 and RT27 stream format
o u-blox UBX

- has dynamic buffering when reading all raw data formats (which had been done for some
formats in the 2016Apr1 version and is now completed); this should prevent loss of data
as manufacturers add tracking of more constellations to full-GNSS data records or
messages and as some now incomplete GNSS constellations increase in size

- has a few fixes for the '-tbin' option (see July 12 & 13 and Oct 17 entries in log);
for more details, see http://postal.unavco.org/pipermail/teqc/2016/002127.html and
http://postal.unavco.org/pipermail/teqc/2016/002164.html

- has a floating-point fix for sub-second setting of time windowing with '-st', '-e',
and/or the delta options where the specified start and/or end times are meant to be
equivalent to the actual start and/or end times of the input; for more details, see
http://postal.unavco.org/pipermail/teqc/2016/002155.html

- has initial support for IRNSS (BINEX, Javad JPS, Septentrio Binary Format,
Trimble .tgd record 28 and RT27 0x55)

- has an overhaul of the parsing of Javad JPS and Topcon TPS, making it compatible
with new JPS messages (e.g. [rx], [RX], [0d], [DX], [cr]) and other changes with fw
3.6.0 and 3.7.0, including the move of Beidou B2/E5b observables from the [*5] and [5*]
messages to the [*2] and [2*] messages starting at fw 3.7.0

- fixes a long-standing bug when decoding the relative phase values from Javad JPS and
Topcon TPS messages [*p] (i.e. [1p], [2p], ...) Note: This particular issue will require
a separate email for a full explanation.

- is compatible with BINEX that is available from the Septentrio PolaRx5 receiver

- allows decimation of BINEX 0x7f-05 (though with no observation or SV filtering,
and no endian-reversal of 0x7f-05 with '-r')

- does reading of u-blox UBX RMX-RAWX message (generalized GNSS observation data)

- continues the new option paradigm for the options:
+O.sum, ++O.sum (though a couple minor differences from the others)
+diag, ++diag
+psp, ++psp (was previously +dep in experimental mode and +epp for a while)
+raw_nav, ++raw_nav
+ion_p, ++ion_p (was previously +dump_i)
+utc_p, ++utc_p (was previously +dump_u)
... adding to the previous suite:
+eds, ++eds
+event, ++event
+rx_state, ++rx_state
+slips, ++slips
... so please consult `teqc +help` if you use any of these options, e.g.
[1304] teqc +help | grep diag
+diag[nostics] . output parsing and other diagnostics to stdout
+diag[nostics] .. output parsing and other diagnostics to stderr
+diag[nostics] name output parsing and other diagnostics to file 'name'
++diag[nostics] name append parsing and other diagnostics to file 'name'
-diag[nostics] don't output parsing and other diagnostics (default)

- has '+rx_state' options expanded to read:
o BINEX record 0x7d ( http://binex.unavco.org/binex_record_7d.html )
o Trimble .tgd record 40
o Septentrio SBF message 4014 (ReceiverStatus) for temp, 4101 (PowerStatus) for voltages (PolaRx5)
o Leica MDB message 105 or older message 5 (Diagnostic): voltages in %

- has '+psp' options expanded to read:
o BINEX record 0x05 ( http://binex.unavco.org/binex_record_05.html )
o Trimble .tgd record 29 and RT27 streaming 0x57-7
o Septentrio SBF messages 4006, 4007 (and older 5903, 5904)
o Javad JPS and Topcon TPS: [rE], [rV], [rT]; [ST], [TO], [DO], [PG], [PO], [PV], [VE], [VG]
o Leica MDB 10 & 110, 11 & 111, 12 & 112 (initial reference position only), 13 & 113: but no clock info
o u-blox UBX-NAV-SOL (0x0106) and UBX-NAV-PVT (0x0107): no clock info yet

- allows the O.sum options to stdout, stderr, or a non-RINEX file to be used
with '+mds' or '+meta' on one or more input files (note: '+meta' is not currently
defined for RINEX navigation or meteorological files)

- has numerous corrections/clarifications in the '+help' option

One small functional change that I want you in particular to note:

- the O.sum options remove any observable columns where there are no observables,
including using '+all' with raw data and if the input has no observables, you
should get a single output line stating this

As with the 2016Apr1 version, some builds are not available with this release:

- any HP-UX builds (due to a lack of access an HP-UX system for compiling)
- the Borland build for Windows; instead, use the Mingw-32 bit build
- the Mac OSX i5 gcc 4.2 64-bit build; instead, use the OSX i5 gcc 4.3 64-bit build
- Solaris Sparc 5.9 builds

If you have any questions, please let me know.

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
WWW: http://www.unavco.org/&apos ;"> http://www.unavco.org http://jules.unavco.org/&apos ;"> http://jules.unavco.org

"If the universe is the answer, what is the question?"
-- Leon Lederman
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
_______________________________________________
teqc mailing list
[email protected]
http://postal.unavco.org/mailman/listinfo/teqc


 
Posted : November 21, 2016 8:25 pm
Page 2 / 2