BACKGROUND
I have long term experience using Star*Net. Have recently started work at new company that uses FieldGenius data collectors with Leica GS15 GNSS receivers. Have downloaded a demo copy of Star*Net and am attempting adjustment of RTK vectors for control project. Will probably buy but need issue resolved.
THE PROBLEM
Importing GPS vectors to StarNet from FieldGenius 6.0.2.5 .raw file. G0 and G1 lines are written to the .gps file, but G2 and G3 lines (the covariance data) are not. In the .raw file I'm seeing the lines:
--GNSS Profile Tolerance RT: Obs=180,Solution=RTK Fixed,Elev=13,PDOP=4.0,SVs=5,RefID=Any,StdDevH=0.09',StdDevV=0.09'
--GNSS Profile Tolerance PP: Not Active
--GNSS Statistics RT: Obs=180,Solution=RTK Fixed,PDOPMax=1.39,SVMin=14,StdDevH=0.01',StdDevV=0.01',RefID=, RefLat=N35°12'09.27140",RefLon=W97°28'34.84661",RefHgt=1072.40',RefFormat=
--GNSS Statistics PP: Not Active
Which suggests to me that the covariance data is not in the raw file. In other data files from an earlier version of Field Genius I get the following lines:
EP,TM15:21:37.0000, LA35.30511476669,LN-97.50063354481,HT1088.9706,RN0.0189, RE0.0189,RV0.0265,DH1.0,DV1.6,GM4,CL1
BL,DCROVER,PN2002,DX-515.5452, DY71.0530,DZ-18.5511,--177,GM4,CL1,HP0.019,VP0.027
CV,DCROVER,SV11,SC1, XX0.00013759815,XY0.00000920602,XZ-0.00001596125, YY0.00049737433,YZ-0.00022673839,ZZ0.00033628542
GS,PN2002,N 111452.2788,E 2117511.5445,EL1176.5192,--177
Which looks like the covariance data I'm looking for. The StarNet importer does write the G2 and G3 data when importing these old files.
THE QUESTION
How do I get Field Genius to record the covariance data to the .raw file?
I have no idea, but why don't you contact MicroSurvey? They have always been very helpful to me.
I don't know much but I do know the converter in Microsurvey scrambles the THs in a conventional Field Genius raw file. We were having to manually unscramble them (well not me, I was using a TDS dc with StarNet's converter which worked fine, the other crew was using Field Genius).
Now that we are using Trimble Access, I convert to TDS RW5 then use the StarNet converter. No scrambled THs.
Don't ask me how this stuff gets through beta testing.
Don't ask me how this stuff gets through beta testing.
If you haven't noticed we are the beta testers for all the software manufacturers.
And if you find ten or more problems then you can claim the title of "master beta tester".
Sorry G.B. for the theft.
Just in case those covariance values were not recorded you can add an inline option and do get your data adjusted without G2 and G3 lines. You can try something like this:
#Set Hz Std Err to 0.010m + 1ppm, Set Vert Std Err to 0.020m + 2ppm
#--------------------------------------------------------------------
.GPS WEIGHT STDERRCORR
.GPS DEFAULT 0.010 1 VERT .020 2
Its on page 8 of the StarNet Pro manual and also available in MircrSurvey Starnet.
Have a good day now,
Terry L. Nygaard / Tx TPLS
I don't know the answer, BUT agree with Hillbilly, they now own both products, so there is no excuse, they need to make it work!
SHG
> ... they need to make it work!
I have put in a helpdesk request to Microsurvey. But I have a very high opinion of the user segment on SurveyorConnect.
> #Set Hz Std Err to 0.010m + 1ppm, Set Vert Std Err to 0.020m + 2ppm
> #--------------------------------------------------------------------
> .GPS WEIGHT STDERRCORR
> .GPS DEFAULT 0.010 1 VERT .020 2
Unless I'm mistaken, this part ".GPS WEIGHT STDERRCORR" is not needed - that would be telling it to expect G2 and G3 lines containing standard errors and correlations and would be immediately superseded by the ".GPS DEFAULT" option anyway. Just put ".GPS DEFAULT [stderr] [ppm] VERT [stderr] [ppm]", or simply set the default in the project options (if all your vectors are of the same quality), and only give G1 lines. It would still be better to find out how to get the software to give you the covariances.
> Don't ask me how this stuff gets through beta testing.
I once had a conversation with Ron Sawyer in which he related that the data convertors were the biggest headache he had. Seems the manufacturers would add "features" almost at will and not document them to outside developers like him. His days were filled with reverse engineering the data formats of multiple vendors.
Since StarNet is now under the Leica umbrella I wouldn't expect cooperation from Trimble to improve.
Hillbilly,
I believe both methods will work - the one I presented assumes there are no G2 and G3 lines. Here is some example data that does work:
#Set Hz Std Err to 0.010m + 1ppm, Set Vert Std Err to 0.020m + 2ppm
#--------------------------------------------------------------------
.GPS WEIGHT STDERRCORR
.GPS DEFAULT 0.010 1 VERT .020 2
#-------------------------NEW Base ID: A861--------------------------
#DC File: T:_Field_StoreT268002A.rw5
C 100 ":141
G0 'V2345 07-11-2003 XX:XX BaseAH 2.000m ARP / RoverAH 2.000m ARP
G1 A861-100 -21.746958 -60.417659 -112.886521
#DC File: T:_Field_StoreT268002A.rw5
C 405 ":102
G0 'V2346 07-11-2003 XX:XX BaseAH 2.000m ARP / RoverAH 2.000m ARP
G1 A861-405 -17.467398 1.432179 -0.665426
Have a good day,
Terry L. Nygaard / Tx RPLS (got it right this time)
After import my FieldGenius data looks like this:
.GPS WEIGHT COVARIANCE
.Units FeetUS DMS
G0 'V1 01-22-2013 14:55:30.0000 130122-bgrtk-13011.raw
G1 2-50 42.836245 -135.071024 -180.117611
G0 'V2 01-22-2013 14:58:18.0000 130122-bgrtk-13011.raw
G1 2-50 42.849815 -135.079413 -180.121613
G0 'V3 01-22-2013 15:05:24.0000 130122-bgrtk-13011.raw
G1 2-49 34.042028 -198.076260 -274.007961
Which adjusts without difficulty based on default standard errors set in the GPS tab of the Option menu. But that's suboptimal.
This is really a FieldGenius/Leica issue, not a StarNet issue.
> THE QUESTION
> How do I get Field Genius to record the covariance data to the .raw file?
I got a call from Tim Johnson of Microstation. They know of the problem and blame Leica for failing to share. Someday it may be fixed. In the meantime it's just the way it is.
> I got a call from Tim Johnson of Micro[survey?]. They know of the problem and blame Leica for failing to share. Someday it may be fixed. In the meantime it's just the way it is.
It's difficulties like this that dissuaded me from buying Leica equipment. How difficult can it be to figure out that if you make software that no one will want to use if presented with a choice, you need to assist other developers who are selling software that people actually want to use?
It seems to me I recall hearing that Leica had declined to furnish information about their data formats that was needed to write a utility to convert native Leica format conventional data to Star*Net format.
Ron Sawyer's converter works fine.
The problem was the converter inside Microsurvey.
> It seems to me I recall hearing that Leica had declined to furnish information about their data formats that was needed to write a utility to convert native Leica format conventional data to Star*Net format.
Its all the more perplexing since Leica now owns Microsurvey.
> > It seems to me I recall hearing that Leica had declined to furnish information about their data formats that was needed to write a utility to convert native Leica format conventional data to Star*Net format.
>
> Its all the more perplexing since Leica now owns Microsurvey.
To be fair, the difficulties getting data format information from Leica that I mentioned pre-dated even MicroSurvey's acquisition of Star*Net. However, now that Leica owns MicroSurvey, it's just plain crazy/stupid that these conversion problems linger on.
Leica doesn't own MicroSurvey. Hexagon owns both Leica Geosystems and MicroSurvey. There are still silo walls separating the separate entities.
