One thing that I'd be interested to learn from other Star*Net users who are importing GPS (including RTK GPS) vectors into Star*Net is how well various manufacturer's gear works toward that end.
I'm assuming that most GPS manufacturers will expect that users (aka "renters") will want to adjust GPS vectors in said manufacturers's proprietary software and won't facilitate the use of third-party software.
> One thing that I'd be interested to learn from other Star*Net users who are importing GPS (including RTK GPS) vectors into Star*Net is how well various manufacturer's gear works toward that end.
>
> I'm assuming that most GPS manufacturers will expect that users (aka "renters") will want to adjust GPS vectors in said manufacturers's proprietary software and won't facilitate the use of third-party software.
While in Oklahoma I discovered that Microsurvey FieldGenius data collection used to run a Leica GS15 receiver yields no standard error data with the vectors. Its not in the raw data file. The same data collection software used with Topcon GR3s does yield the standard error data. Go figure. Microsurvey knows about it because I told them - a number of times, in high tones - but no movement.
I've recently found that the converter for Spectra Precision Survey Pro raw files in StarNet v8 produces vectors in feet, which StarNet reads as meters no matter what. Luckily that data collector will also export files in the Trimble jxl format, and the converter for the jxl format works as advertised. The problem has been reported to Microsurvey but I've been told it it will be some time before it gets fixed.
> I've recently found that the converter for Spectra Precision Survey Pro raw files in StarNet v8 produces vectors in feet, which StarNet reads as meters no matter what. Luckily that data collector will also export files in the Trimble jxl format, and the converter for the jxl format works as advertised. The problem has been reported to Microsurvey but I've been told it it will be some time before it gets fixed.
That is exactly the sort of thing that would be a deal breaker for me.
I have exported processed vectors from Topcon Tools and TBC. Both worked with no problems.
> I have exported processed vectors from Topcon Tools and TBC. Both worked with no problems.
Does that include vectors in all forms: static, PPK, and RTK?
I've exported RTK and static from Topcon Tools but only static from TBC. It probably works, I just haven't done it.
> I've exported RTK and static from Topcon Tools but only static from TBC. It probably works, I just haven't done it.
Same here regarding TBC, I've never tried exporting anything but static.
> > I've exported RTK and static from Topcon Tools but only static from TBC. It probably works, I just haven't done it.
>
> Same here regarding TBC, I've never tried exporting anything but static.
Same here. I manually pull out the .t02 file and convert to RINEX.
We're running Trimble equipment currently. It is a bit dated (so I can't speak of newer Trimble equipment), but I can say that for conventional RAW data, Star*Net's Trimble converter works great with DC files.
During my demo of Carlson / StarNet I found one issue. The rover rod comes across in feet. A simple 'find replace' cleans it up.
Hopefully the manufacturers will continue to work with Microsurvey as competition heats up. With everybody and their cousin selling data collectors and software it's got to be hard keeping up...
> Same here. I manually pull out the .t02 file and convert to RINEX.
That would be an observation file. What Kent is referring to is the processed vector data with associated error estimates. In TBC this is accomplished by using the Trimble Data Exchange Format (TDEF) exporter, which produces a .asc file that Star*Net can read.
Thanks.
I should have waited to post until after cup of coffee #2. My reading comprehension skills increase exponentially after #2.
😛
>...it's got to be hard keeping up...
I once had a conversation with Ron Sawyer in which he said that the data converters where what took up all his time. He felt that - just maybe - the manufacturers where jimmying with their formats for no other reason than to make things hard for him.
In the case of the FieldGenius/Leica issue I reported above Microsurvey claimed to be stymied by non-cooperation from Leica. It was a problem between the Leica and the data collector. Their was nothing for the converter to convert. It had never worked and never would without input from sources out of their control.
In the case of the Spectra Precision problem the converter worked fine in V7 and was broken by V8. One work around proposed was to do the conversions in V7. I found an alternate and slightly more convenient work around.
Example of (3rd party) SurvCE RW5 GPS raw data file vectors (RTN):
--SurvCE Version 3.0.16
--Equipment: GRX2 SN:GRX1/U XXX-XXXXX
--Antenna Type: [SOKGRX2 NONE],RA0.0890m,SHMP0.0552m,L10.1112m,L20.1049m,--TPS p/n:01-090101-08
--GPS Scale: 1.00000000
--RTK Method: RTCM V3.0, Device: Internal Cellular, Network: NTRIP RT3V
BP,PN4095,LA00.515816790500,LN-00.184867975000,EL147.7940,AG0.000,PA0.000,--
--Entered HR: 1.9950, Vertical
LS,HR0.0000
GPS,PN4095,LA00.515816790500,LN-00.184867975000,EL147.794000,--BASE
--GS,PN4095,N XXXXXXX.7510,E XXXXXX.2534,EL184.0695,--BASE
--Entered HR: 1.9950, Vertical
LS,HR2.1062
GPS,PN1088,LA00.522003711121,LN-00.155166164235,EL147.097621,--HCM60
--GS,PN1088,N XXXXXXX.2549,E XXXXXX.3056,EL181.2459,--HCM60
G0,2013/09/24 18:23:31,(Average) - Base ID read at rover: 4095
G1,BP4095,PN1088,DX3796.72137,DY1194.73530,DZ486.12831
G2,VX0.00001526,VY0.00007650,VZ0.00006017
G3,XY-0.00000547,XZ0.00000568,YZ-0.00005274
--GT,PN1088,SW1759,ST239016000,EW1759,ET239027000
--Valid Readings: 10 of 10
--Fixed Readings: 10 of 10
--Nor Min: XXXXXXX.2483 Max: XXXXXXX.2573
--Eas Min: XXXXXX.3021 Max: XXXXXX.3089
--Elv Min: 181.2425 Max: 181.2487
--Nor Avg: XXXXXXX.2549 SD: 0.0026
--Eas Avg: XXXXXX.3056 SD: 0.0020
--Elv Avg: 181.2459 SD: 0.0018
--HRMS Avg: 0.0055 SD: 0.0000 Min: 0.0055 Max: 0.0055
--VRMS Avg: 0.0110 SD: 0.0000 Min: 0.0110 Max: 0.0110
--HDOP Avg: 0.6233 Min: 0.6233 Max: 0.6233
--VDOP Avg: 1.2437 Min: 1.2433 Max: 1.2441
--PDOP Avg: 1.3912 Min: 1.3908 Max: 1.3915
--Number of Satellites Avg: 16 Min: 16 Max: 17
--HRMS:0.006, VRMS:0.011, STATUS:FIXED, SATS:17, PDOP:1.392, HDOP:0.623, VDOP:1.244, TDOP:0.723, GDOP:1.568
GPS,PN1098,LA00.521807618411,LN-00.153334141551,EL137.524084,--HCM648
--GS,PN1098,N XXXXXXX.3558,E XXXXXX.4643,EL171.6714,--HCM648
G0,2013/09/24 18:46:51,(Average) - Base ID read at rover: 4095
G1,BP4095,PN1098,DX4205.13916,DY1236.52009,DZ435.86289
G2,VX0.00001346,VY0.00007767,VZ0.00006917
G3,XY-0.00000254,XZ0.00000393,YZ-0.00005299
--GT,PN1098,SW1759,ST240416000,EW1759,ET240427000
--Valid Readings: 10 of 10
--Fixed Readings: 10 of 10
--Nor Min: XXXXXXX.3542 Max: XXXXXXX.3580
--Eas Min: XXXXXX.4619 Max: XXXXXX.4680
--Elv Min: 171.6660 Max: 171.6757
--Nor Avg: XXXXXXX.3558 SD: 0.0012
--Eas Avg: XXXXXX.4643 SD: 0.0017
--Elv Avg: 171.6714 SD: 0.0034
--HRMS Avg: 0.0059 SD: 0.0002 Min: 0.0057 Max: 0.0063
--VRMS Avg: 0.0112 SD: 0.0006 Min: 0.0108 Max: 0.0121
--HDOP Avg: 0.6581 Min: 0.6384 Max: 0.7039
--VDOP Avg: 1.2530 Min: 1.2088 Max: 1.3558
--PDOP Avg: 1.4153 Min: 1.3670 Max: 1.5276
--Number of Satellites Avg: 16 Min: 15 Max: 17
--HRMS:0.006, VRMS:0.011, STATUS:FIXED, SATS:17, PDOP:1.367, HDOP:0.638, VDOP:1.209, TDOP:0.715, GDOP:1.543
GPS,PN1099,LA00.522548926787,LN-00.153402432428,EL149.216821,--HCM649
--GS,PN1099,N XXXXXXX.7437,E XXXXXX.4058,EL183.3623,--HCM649
G0,2013/09/24 18:53:52,(Average) - Base ID read at rover: 4095
G1,BP4095,PN1099,DX4162.17729,DY1381.19169,DZ608.90517
G2,VX0.00001451,VY0.00006387,VZ0.00006495
G3,XY-0.00000517,XZ0.00000537,YZ-0.00004577
--GT,PN1099,SW1759,ST240838000,EW1759,ET240848000
--Valid Readings: 10 of 10
--Fixed Readings: 10 of 10
--Nor Min: XXXXXXX.7403 Max: XXXXXXX.7466
--Eas Min: XXXXXX.4036 Max: XXXXXX.4106
--Elv Min: 183.3543 Max: 183.3662
--Nor Avg: XXXXXXX.7437 SD: 0.0021
--Eas Avg: XXXXXX.4058 SD: 0.0019
--Elv Avg: 183.3623 SD: 0.0033
--HRMS Avg: 0.0057 SD: 0.0001 Min: 0.0057 Max: 0.0058
--VRMS Avg: 0.0105 SD: 0.0002 Min: 0.0103 Max: 0.0107
--HDOP Avg: 0.6475 Min: 0.6393 Max: 0.6556
--VDOP Avg: 1.1859 Min: 1.1668 Max: 1.2051
--PDOP Avg: 1.3512 Min: 1.3305 Max: 1.3719
--Number of Satellites Avg: 15 Min: 15 Max: 16
--HRMS:0.006, VRMS:0.010, STATUS:FIXED, SATS:16, PDOP:1.330, HDOP:0.639, VDOP:1.167, TDOP:0.695, GDOP:1.501
Example of imported (Carlson GPS) vectors into Starnet (PRO, v8 with highly advanced technical capability to include point code/description):
.GPS WEIGHT COVARIANCE
G0 'V1 2013/09/24 18:23:31,(Average) - Base ID read at rover: 4095
G1 4095-1088 3796.721370 1194.735300 486.128310 0.000/2.106 'HCM60
G2 1.526000000000E-005 7.650000000000E-005 6.017000000000E-005
G3 -5.470000000000E-006 5.680000000000E-006 -5.274000000000E-005
G0 'V2 2013/09/24 18:46:51,(Average) - Base ID read at rover: 4095
G1 4095-1098 4205.139160 1236.520090 435.862890 0.000/2.106 'HCM648
G2 1.346000000000E-005 7.767000000000E-005 6.917000000000E-005
G3 -2.540000000000E-006 3.930000000000E-006 -5.299000000000E-005
G0 'V3 2013/09/24 18:53:52,(Average) - Base ID read at rover: 4095
G1 4095-1099 4162.177290 1381.191690 608.905170 0.000/2.106 'HCM649
G2 1.451000000000E-005 6.387000000000E-005 6.495000000000E-005
G3 -5.170000000000E-006 5.370000000000E-006 -4.577000000000E-005