I have a dat file from my trimble 5700. Trying to submit to opus rs.
I recieved the fillowing error message:
FILE: 83040470.dat OP1333464512283
1014 The RINEX data submitted to OPUS contains data taken from more than one
1014 location. This can be verified by opening up your RINEX file and
1014 searching for "MARKER". OPUS will only process data taken from one
1014 location. Try separating the data into individual files and then
1014 re-submit the data
1014 Aborting...
1014
If someone would be so kind. I can send you the rinex file and let you look at it to see where i can edit it to get only one position.
Also if you could let me know what you did and how so i can do this in the future it would be appreciated.
Thanks in advance for your help.
my email is pmichael@msmva.com
open the rinex file in an editor (I use ultraedit). Remove any extra comments after the start of data.
A rinex file has a header section, and an observables section (i.e. data). Sometimes there is an epoch or two (or more), and then a comment record indicating the start of an occupation.
For example:
[pre]
2.11 OBSERVATION DATA G (GPS) RINEX VERSION / TYPE
teqc 2010Mar17 20120403 21:49:49UTCPGM / RUN BY / DATE
MSXP|IAx86-PII|bcc32 5.0|MSWin95->XP|486/DX+ COMMENT
BIT 2 OF LLI FLAGS DATA COLLECTED UNDER A/S CONDITION COMMENT
6207066 MARKER NAME
6207 MARKER NUMBER
-Unknown- -Unknown- OBSERVER / AGENCY
220136207 TRIMBLE 4700 NP 1.20 / SP 1.43 REC # / TYPE / VERS
00000000 TRM39105.00 NONE ANT # / TYPE
825515.9155 -4782700.4671 4124633.5633 APPROX POSITION XYZ
0.0000 0.0000 0.0000 ANTENNA: DELTA H/E/N
1 1 WAVELENGTH FACT L1/2
7 L1 L2 C1 P2 P1 S1 S2 # / TYPES OF OBSERV
15 LEAP SECONDS
SNR is mapped to RINEX snr flag value [0-9] COMMENT
L1 & L2: min(max(int(snr_dBHz/6), 0), 9) COMMENT
2012 3 6 15 52 0.0000000 GPS TIME OF FIRST OBS
END OF HEADER
12 3 6 15 52 0.0000000 0 7G05G15G18G21G26G27G29
142155.55157 88113.49055 23832451.5084 23832453.8134
43.0004 30.2504
1250.30558 755.31457 20155423.6564 20155422.1054
50.7504 45.5004
-93070.20758 -52972.07555 22106727.7504 22106724.8164
49.2504 35.0004
-100669.07457 -57678.17156 21282386.3834 21282383.7624
45.0004 37.5004
148315.62158 85304.59256 21242393.6564 21242392.5944
49.0004 37.7504
-78370.21157 -46532.41655 22500378.0864 22500378.9774
44.5004 31.2504
165543.41057 96211.06855 22558102.3594 22558103.7424
42.7504 31.5004
12 3 6 15 52 15.0000000 4 3
MARKER NAME
03016EA MARKER NUMBER
1.856 (antenna height) COMMENT
12 3 6 15 52 15.0000000 0 7G05G15G18G21G26G27G29
185645.83247 122001.92445 23840725.8524 23840729.3834
43.7504 30.7504
1883.80548 1248.92947 20155544.2894 20155542.5084
50.7504 45.0004
-119237.25848 -73361.99245 22101747.4384 22101745.5044
49.5004 35.0004
-129095.73447 -79828.80146 21276976.9774 21276973.8484
46.0004 37.7504
190817.91448 118423.24246 21250481.2424 21250480.3054
49.5004 38.0004
-110846.36747 -71838.50245 22494198.1484 22494199.4224
43.7504 31.7504
213204.93047 133349.87345 22567173.0704 22567172.4924
42.7504 31.0004
[/pre]
after the header, there is an epoch. Then a station name and HI. remove the 4 lines in bold above, save the file, and it should work.
Sometimes the OPUS error messages do not have much connection with reality, but for this DAT file the error message was spot on - there are two separate points in the DAT file.
Suggestion for Trimble users - If you are using a survey style based on the "FastStatic" survey type, use the "Start base receiver" option to create a file for submission to OPUS-S or OPUS-RS. That way you will be sure that there will be only one point in the file and there will be none of the Trimble-specific records that OPUS does not understand. In most cases files made this way can be submitted to OPUS without any editing whatsoever. If the point name you assign does not exist in the file you will likely be warned that you will need to provide coordinates for the point at processing time; you can disregard that warning.
The first order of business is to see what we can find out about the DAT file, so I started a new TGO (see below for reason for using TGO instead of TBC) project and imported the DAT file. The "DAT Checkin" dialog appears below -
This clearly shows that there were two points (Point 2 and Point 1) in the file, with some data logged before Point 2 started. The antenna may have been static during the "Roving Segment" but we do not really know so we will not use that data.
Accepted this data and the autonomous versions of Points 1 and 2 appeared on the screen. Inversed between the two points -
Since the two autonomous points are about 365 feet apart it seems a safe bet they were intended to be different points.
Now we look at the Timeline of the observations and see that the data appears to be clean, no tracking dropouts or the like.
This Timeline is the reason I used TGO - if there are problems with L2 data (the weaker and more-susceptible-to-interference data) it will clearly show up here. TBC has its "Time-Based View", but to date (TBC Version 2.60) that feature is fairly useless because it does not give any indication of L2 tracking problems. TBC's "Time-Based View" also requires two time-coincident files to work which is a bit of an irritation, but with the "Internet Download" feature it is pretty simple to get the second file.
Right-click on the yellow bar above the observations, then select Properties and we see this data was collected at 5-second epochs.
I do not know of any Trimble-supported method for splitting a multiple-occupation DAT file into individual files for each occupation, but Mr. Geoffrey Kirk has generously provided his FS2DATS utility that is supposed to do that task.
This is my first try with the FS2DATS utility, and while it did generate individual DAT files that TGO saw as having only the desired span of data (as shown in the DAT-Checkin dialog below), OPUS-RS still rejected both individual files (interestingly, OPUS-RS did produce a solution for an unedited RINEX file made directly from the individual file for Point 2, I suspect the fact that unedited RINEX file made from the individual file for Point 1 did not process is related to information that appeared in the header of that file??).
So now we will revert to brute-force editing.
Since TEQC's command-line interface intimidates most earthlings of 2012, we will convert the DAT file to RINEX format using Trimble's "Convert to RINEX" utility. (Had we used TEQC it would have been possible to decimate the data to 30-second epochs to match OPUS, but that is not a huge issue.)
Running "Convert to RINEX" creates a RINEX observation file named 83040470.12o. We make two copies of that file, naming them Point_1.12o and Point_2.12o so the file names relate to the points for which each contains data.
Open the file named Point_1.12o with our text editor and search for MARKER.
In Column 1 of both Lines 4 and 5, change the marker information to 1.
Then we find that the marker information for Point 1 is at Line 3599 and that the data for Point 2 begins at Line 3603.
Copy Line 3601 (labeled APPROX POSITION XYZ) and replace Line 9 with the copied line. (This step may not be absolutely necessary, but it will not hurt).
Delete Lines 31 through 3602, leaving only the data for Point 1 in this file. The data records should begin in the line following the END OF HEADER LABEL, as shown below -
2.11 OBSERVATION DATA GPS(GPS) RINEX VERSION / TYPE
cnvtToRINEX 2.12.0 Howard Inoe 04-Apr-12 19:55 UTC PGM / RUN BY / DATE
----------------------------------------------------------- COMMENT
1 MARKER NAME
1 MARKER NUMBER
Lon G. Toody Trimble OBSERVER / AGENCY
0220281914 5700 2.31 REC # / TYPE / VERS
TRM39105.00 ANT # / TYPE
1210680.0407 -4967598.4523 3800022.5521 APPROX POSITION XYZ
2.0000 0.0000 0.0000 ANTENNA: DELTA H/E/N
1 1 0 WAVELENGTH FACT L1/2
4 C1 L1 L2 P2 # / TYPES OF OBSERV
2012 2 16 14 8 5.0000000 GPS TIME OF FIRST OBS
2012 2 16 15 48 40.0000000 GPS TIME OF LAST OBS
0 RCV CLOCK OFFS APPL
15 LEAP SECONDS
11 # OF SATELLITES
G02 1173 1173 1173 1173 PRN / # OF OBS
G04 661 661 661 661 PRN / # OF OBS
G05 1173 1173 1173 1173 PRN / # OF OBS
G08 121 121 120 120 PRN / # OF OBS
G10 689 689 689 689 PRN / # OF OBS
G12 418 418 418 418 PRN / # OF OBS
G15 969 969 969 969 PRN / # OF OBS
G18 157 157 156 156 PRN / # OF OBS
G21 385 385 384 384 PRN / # OF OBS
G25 691 691 691 691 PRN / # OF OBS
G29 1173 1173 1173 1173 PRN / # OF OBS
CARRIER PHASE MEASUREMENTS: PHASE SHIFTS REMOVED COMMENT
END OF HEADER
12 2 16 14 45 50.0000000 0 6G02G04G05G15G25G29
21257286.344 7 18149.152 7 47388.87948 21257286.34448
24329824.828 5 57812.027 5 2760203.68046 24329824.82846
Go to the bottom of the file, and delete everything after the carriage return after the last line containing data (now Line 5255). Like John said, confirm there are not any extraneous comment lines mixed in with the data.
That file is now ready to send to OPUS-RS. (The careful reader will note that the TIME OF FIRST OBS, TIME OF LAST OBS, and "# OF OBS" records in the header are now wrong, but that does not affect OPUS processing.)
Now open the file named Point_2.12o with the text editor.
Search for MARKER until you get to the information for Point 1, then delete everything from immediate previous data record to end of file. Leave a carriage return after the last data record.
Search again for MARKER and find the first data record for Point 2 (happened to be Line 381 in this case). Delete Lines 31 through 380, and this file is also ready for sending to OPUS-RS.
OPUS-RS produced solutions for both of these edited RINEX files, using 88% of the observations in both cases, which is a little on the low side but probably acceptable. The normalized RMSs are a bit higher than I would like to see, may want to get another data set for comparison if these positions require high accuracy.
Run through this yourself and report back with your results and/or questions.
GB
