In a previous thread, I asked for advice on work flow getting data through the DC into Traverse PC...The focus was on redundant data gathering, and the thread got sucked towards using LSA on the control file, and how to use that control file going back into the field.
I tried a few of the ideas and got bogged down in data pretty quickly, given that I'm still learning both the SurvCE and TraversePC platforms. I should point out that the folks at TraversePC have been exceptionally helpful; I'm continuing to rely on them for support, along with the tutorials, and a lot of trial and error.
But now, I'm realizing that my window of opportunity to gather data in the woods is closing in on me before the thick underbrush, pricker bushes etc. start growing rampantly, and I want to finish gathering data for both control and topo quickly, and worry about reducing it, applying LSA, plotting it, etc. I can do that later, when I get more able with the software.
At this point, I just want to make sure that my data gathering procedures are good enough for what the software is capable of, and I don't find myself wanting to go back and hack my way uphill through 1/4 mile of woods in a month or so because I missed something.
Therefore, does anyone have experience with SurveCE and TraversePC generally, or, more specifically as it pertains to redundant measurements? This is total station work only...no GPS.
More specifically, I'm talking about the convention TraversePC uses to log redundant measurements using different point numbers.
See this raw data from SurvCE:
And this reduced version (no LSA yet--I think it's using SurvCE's "mean" data):
For LSA to work apparently, the designation of another point ("301:1" for example), with the designation "=301" in the comment line, is required. Doing this seems to make virtually all of my points that I take redundant shots on, "new' points. It's very confusing.
Right now, my procedure (for other than topo side shots) is:
1. Create new file for each day, Set up on point's previously occupied; back sight also to established points
2. One or two sets of BD/FD FR/BR
3. Add the new traverse to the survey
4. Output ASCII to a file and import new points into the Control File and upload to the data collector.
5. Repeat 1-5.
Could anyone who has experience with this combo of software comment on this procedure? Again, I'm not concerning myself with processing the data yet; just a good gathering procedure that will not leave me wanting for something not gathered in the first place. Thanks in advance for thoughts.
If I read this correctly SurvCE wants to see the "=301" as a description. I believe this is the standard convention when using SurvNet and controllers that don't allow multiple observations to one point without storing a new coordinate. TraversePC doesn't require this to the best of my knowledge.
Just to be clear... you want to bring the SurvCE raw file into Traverse PC and use the Traverse PC LSA routine to adjust your control network, right?
> If I read this correctly SurvCE wants to see the "=301" as a description. I believe this is the standard convention when using SurvNet and controllers that don't allow multiple observations to one point without storing a new coordinate. TraversePC doesn't require this to the best of my knowledge.
>
> Just to be clear... you want to bring the SurvCE raw file into Traverse PC and use the Traverse PC LSA routine to adjust your control network, right?
Yes; precisely correct...don't need to know all the ins and outs of doing that for now, but want to make sure that I have the data collector set up correctly to give TPC what it needs. FYI, There is a record type in TPC called "OBS", which is a redundant measurement to the same point, but as I understand it, if you want to use LSA, it needs a different point with the "=xxx" description.
There's a popup dialog box when adding a traverse to a survey with 5 or 6 options for redundant points/observations, that I'm still trying to figure out, but as long as I have good raw data, I can always "dump" it and re-load it with the right settings.
Use different numbers designations and use = in the description for the redundant shot . When the least squares processing is done you will only have one point .
> Use different numbers designations and use = in the description for the redundant shot . When the least squares processing is done you will only have one point .
Ok, thanks. When I go back out, though, to set up on the last point in a traverse that may have had redundant shots, do I choose the original point? That is, The one without the: "xxx:x"? They'll still be in the file at that point (pun?).
Should not be any 301:1 , means you used the same point number when you shot your redundant shot. Use any pt number not used before, and the = in the description . Do not use the redundant obs designation if using least squares. Two different animals.
Again after least squares process you will end up only with the first point.
> Should not be any 301:1 , means you used the same point number when you shot your redundant shot. Use any pt number not used before, and the = in the description . Do not use the redundant obs designation if using least squares. Two different animals.
Yup. Got it. I meant that, because I haven't yet reduced the data, and uploaded all the points back into the DC from TPC, the redundant points are there. I've not used them for anything in the field, as you suggest. Either the last point traversed previously, or a brand new points, which *can* be the same as ones already there if I use the "=xxx" description.
Today I screwed up the point numbers by intermixing traverse points with side shots to intersect a line, but I need practice editing the raw data files anyway, so I think for now, it's all good. Thanks very much!
