Auto Re-start and Static files

We have been finding the auto re-start/auto accept/cluster average features to be particularly useful in some of our difficult condition surveys. In fact, we have relaxed our action setup down to Precise Topo and collect 3-5 points.

It may take 20 minutes to get a reliable point(s) stored, but there are other thing to do, so no problem.

The one down side is that we end up with 3-5 shorter static logs for DPOS when we would prefer to have one long log associated with the first point.

We often have extra receivers out logging to post process a network, including the T2 and LS. Longer rinex files at the rover would process more successfully using our older software.

I can't figure out a work around in J-field, but maybe a feature request? If the auto re-start is toggled on, the first log won't be closed?
 

Nate The Surveyor

Well-Known Member
In my L-1 only days, i learned that super long static shots in deep woods, were often good.
The potential for this is good.

Just for discussion, it'd be good if:

It was logging a static file, and it noticed TILT of the LS, then it stops the static file, automatically. Or, sounds and flashed an alarm.
STATIC FILE LOGGING.
Or some mechanism, to keep you from logging, when you shouldnt be.
So, the question I'm bringing up is: "how to stop static file."
I can even see some situations, where you may wish to log a continous static file, while topoing a field.... If we had the software to support it, post processed.
Just thinking....
 

Nate The Surveyor

Well-Known Member
Thinking into the future....

Memory is getting less and less expensive...

NEXT generation LS, could possibly have huge memory.
Could have raw memory turned on by default. Always on...
This could make a complete trail, everywhere the LS goes.
This could become a historic part of the file... Ie, where the roads are, trails etc.
When integrated with USGS software, and google earth mapping... It could provide more info, about the job... 5 yrs from now, we could literaly see the the trail that was walked, or driven, points and places visited.
As of right now... It's simply leaving this out. In a sense, wasting it.
At some point, it'll be cost effective to USE, and SAVE this information.
It'll provide evidence, in the file, that we in fact visited certian corners, or places, during a particular survey...
I'm trying to encourage, promote, and suggest innovation, to a very progressive company...
As the lone ranger says, to Tonto "you have to stay ahead of 'em, if you want to win".
Nate
 
Top