Static Data

[tpchandler]

I do a lot of surveying in the woods. I have a hard time getting reasonable repeatability when working with points near and under canopy. I have my Triumph LS unit set to record static data. My hope has been that I would be able to download this static data and post process using either the GNSS Solutions or Topcon Tools post processing software I have. Unfortunately I have not been able to get the static data out of the Triumph LS. I've tried Justin link, but connecting to the LS has been sporadic, and when I can, I get error messages when trying to open projects. The idea is to let the unit collect data for 15 minutes or more, then post process and compare to RTK result (if it was able to get a fix at all). Thanks in advance to anyone that can help.

 

[Matthew D. Sibole]

When in heavy canopy and not sure if I will get a fix, I change my acceptable criteria to all with my rms and vrms to 1 meter. Make sure your record GNSS white button is on. Once it has collected at least one epoch I switch my criteria back to my normal fixed only and rms and vrms values back to 4cm and 10cm. (All while still collecting data).

By doing this it allows the LS to associate the static data to a point (whether it be fixed, float or stand alone). If and when it ever gets a fixed solution it will use it and throw out the stand alone point.

 

[Shawn Billings]

Matt is right regarding tolerance filters and static. Recording won't start until criteria are met (such as fixed only, float, stand alone). As for retrieving the file, use windows explorer. No need for Justin Link. Navigate to Mounted Volume, VS Data, Project Name, Raw Data.

 

[tpchandler]

Thank you both! I have a lot to learn. I located the raw data on the storage card in windows explorer.

How do I convert the *.jps file to other formats?

 

[Matt Johnson]

The simplest way to get the static files out of J-Field is with Project Achieve feature. I believe that you should see this as "Archive Current Project" in the Files screen of the current released version of J-Field. The screenshots I am posted are after some improvements have been made:

In the next version of J-Field that is released you will have an export option for "Project Archive File":

With this, options to only export the selected filetypes are available if you don't need the full project archive:

To convert jps files to rinex JPS2RIN is available.

 

[Javad]

What do you mean by "static"? Do you put the unit in Static mode? How? Where?

 

[tpchandler]

Thanks Matt. I was able to archive and export the project easily. I downloaded JPS2RIN and tried to convert the *.jps files but keep getting an error message after selecting the first file that states "can't create temp" "directory:\.........\tmp8477"

 

[tpchandler]

By static data I mean GNSS data. I have the "Record GNSS Data" feature enabled. I used to use a promark system where I would collect what I thought was called "static data" and then download and post-process. I thought maybe the GNSS data I was recording with the Triumph-LS could later be downloaded and post-processed to improve confidence in the "fixed" position(s) that were recorded. I was on a job Saturday where I was working in canopy (some light and some heavy). The Triumph-LS was taking some time to "fix" so I collected six separate observations. The individual observations of the same point were several feet apart. My strategy was to download the data from the base and the rover and post-process in the Topcon Tools or GNSS Solutions software that I used to use to determine the best coordinates of the point. Please let me know if my strategy is flawed. Thank you!

 

[Shawn Billings]

TP,
What settings are you using for collection? Are you using Verify with Resets and Consistency Counter?

 

[Matt Johnson]

Thanks Matt. I was able to archive and export the project easily. I downloaded JPS2RIN and tried to convert the *.jps files but keep getting an error message after selecting the first file that states "can't create temp" "directory:\.........\tmp8477"

You might try running it as administrator as see if you still get this error message. To do this right click on the shortcut, choose properties and then enable the "Run this program as an administrator":

I sometimes post process data when I can't get a fix under canopy too. I generally like to have at least 10 minutes of data when I do this. I find that is also useful to submit the data to DPOS for processing and checking positions.

 

[tpchandler]

R
Thanks. Run as administrator worked.

 

[tpchandler]

I was using accept only RTK solutions in fixed mode, at least 1 engine, All PDOP, All HRMS, All VRMS, at least 5 satellites in view, 1Hz record period, AFRM period = none, use data for up to 30 sec, 10Hz RTK/DGPS Rate, Ambiguity Fixing Confidence Level = medium. Verify settings are "Verify w/o V6 reset," Confidence guard 0.164 ft, Confidence level 3, consistency level 20.0, Max groups 3, Alarm on resets is off.

 

[Shawn Billings]

I was using accept only RTK solutions in fixed mode, at least 1 engine, All PDOP, All HRMS, All VRMS, at least 5 satellites in view, 1Hz record period, AFRM period = none, use data for up to 30 sec, 10Hz RTK/DGPS Rate, Ambiguity Fixing Confidence Level = medium. Verify settings are "Verify w/o V6 reset," Confidence guard 0.164 ft, Confidence level 3, consistency level 20.0, Max groups 3, Alarm on resets is off.

Hi TP,
With these settings you are missing almost all safeties against bad fixes. In open areas, this would be fine, in difficult areas, these settings will not allow for the filtering that J-Field provides against accepting bad fixes. In problematic areas, set Verify to "Verify with Resets". Use a minimum of 2 engines. The confidence level you mentioned is not applied when "Verify w/o Resets" is off. I would recommend between 5-10 for the confidence level. Consistency level of 20 is good. Soon, there will be another test that is applied "Validate", which will perform a final engine reset at the end of the session. If this last Validate reset agrees with the final session, the point passes, if not then validate will attempt to confirm again.

With these settings in place, you should have no worries with post processing, although I appreciate and encourage you to continue maintaining your own QC/QA as you are attempting. It's admirable and more surveyors should take notice. I believe that you will have an incredibly high degree of success with Verify with Resets with a Confidence Level of 5 or more, minimum of 2 engines, Consistency of 10 or more, and Validate with 2 or more engines. This will prevent bad fixes, but due to increased noise in the solution from signals rattling through trees, a return visit may help improve accuracy if necessary.

 

[tpchandler]

Post processing was successful. I'll change settings per your recommendations. Thanks again to all for prompt expert support!