Ok, on this new post processed hybrid dpos

Nate The Surveyor

Well-Known Member
Since we now will be using a 1" epoch rate at the base, this will multiply the size of the base file, by 30x or so.
This will mean that when we Return to base, and press "stop base, and download", that we will have larger base files.

What if, on the cogo dpos page, we had another menu, "modify base files", with several options there.
1.) Truncate base file to 30" rate.
2.) Truncate base file to 30" rate, EXCEPT where coresponding LS post process files are found.
Above option 2 would allow you to keep maybe your 1" data, where it's needed, but not clutter it up with huge file sizes. Where not needed. This would mean that most of the file is truncated to the 30" rate, except some parts, where it found coresponding static files in the LS, which stay at 1" rate.
3.) Truncate base file, to 30" rate, and prepare rinex file. This would be for ngs submission. This option would leave the original file intact. In that a rinex file gets renamed, with another extension.
I'm just thinking out loud. What do the rest of you think?
I used to use a 10" rate, with my old LOCUS L1 units.
I'm typing on my phone.
Nate
 

Nate The Surveyor

Well-Known Member
OK, I probably asked the wrong question first....
I should have asked this one:
At a 1" interval, how many 8 hr days, will the T2 hold?
And, is it possible to increase the memory size on a T2?
Just thinking. About the data flow, and how it all works.

Thanks.

Nate
 

Matt Johnson

Well-Known Member
5PLS
At a 1" interval, how many 8 hr days, will the T2 hold?

An option is being added to not store GNSS signals that aren't needed for post-processing. I think this will probably reduce the side of a 1 Hz raw data file to 25 to 30 MB for an 8 hour period. With 2 GBs of onboard memory this means the T2 could store approximately 66 to 80 of these files.

If you want to convert jps files to rinex files with 30 second intervals, you can use JPS2RIN to do this.
 
Top