What is Wrong with this File?

I would convert the .dat file to RINEX and "clean it up" into a simple "Static (or Rapid Static)" format.

Loyal

rberry5886, post: 437184, member: 232 wrote: OPUS kicks it back saying
FILE: 85041973.DAT OP1500221648954

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

This is my text file of same job...

File: C:Trimble Geomatics OfficeProjects71617Checkin85041973.DAT

+ + + ORIGINAL INFORMATION + + +

GENERAL INFORMATION
Date : 01.06.80
Sync rate : 0.0
Elevation mask : 0
NP version : 5.15
SP version : 0.00
Download version : 03.11.01
Receiver type : R8 Model 3
Receiver serial : 5018426599

15:52:34.000 : ANTENNA INFORMATION [1958,057154.000]
: Type: R8 GNSS/SPS88x [I5]
: Method: Bottom of antenna mount
: Serial number:

: Measurement cycle (seconds): 00.0
: Min tracking requirement (minutes 4,5,6+): 00 00 00
: Cur continuous tracking (seconds 4,5,6+): 00000 00000 00000
: Max continuous tracking (seconds 4,5,6+): 00000 00000 00000
: End code: 1 (OK, sufficient data collected)

00:00:-0.001 : <<< END FAST STATIC OCCUPATION [1958, -0.001] <<<

15:53:00.000 : FIRST MEASUREMENT [1958, 57180.000]

15:53:00.000 : >>> BEGIN STOP AND GO OCCUPATION [1958, 57180.000] >>>

: Station ID: 300
: Station Name: 300
: Antenna Height: 2.000 [Uncorrected]
: Feature Code: cp

16:10:45.000 : <<< END STOP AND GO OCCUPATION [1958, 58245.000] <<<

16:10:45.000 : LAST MEASUREMENT [1958, 58245.000]

I've found the easiest way to avoid this problem is to occupy the point as a base even if it is not a base. This avoids kinematic information in the header that messes up OPUS. Your only choice now is to do as Loyal suggests.

Thanks everyone....

I'm so used to using the VRS network that I was using rover instead of base....duh...

John1Minor2, post: 437188, member: 404 wrote: I've found the easiest way to avoid this problem is to occupy the point as a base even if it is not a base. This avoids kinematic information in the header that messes up OPUS. Your only choice now is to do as Loyal suggests.

Yes Trimble Faststatic measure points tends to do that but there is a setting in the Trimble Rinex converter which will delete any kinematic observations in the file. As you say I always use Faststatic base which eliminates the problem.

Dave Karoly, post: 437237, member: 94 wrote: Yes Trimble Faststatic measure points tends to do that but there is a setting in the Trimble Rinex converter which will delete any kinematic observations in the file. As you say I always use Faststatic base which eliminates the problem.

Hey Dave
Thanks for the tip about the rinex converter. I hadn't noticed that before!

Good tip, thanks Dave....