Carlson Raw File Traverse Editing

I never use the Traverse command, instead my last action (usually) at a station is Set Collection, FS to the next station ahead. 2 sets BSD-FSD-FSR-BSR. SurvNet seems to understand what I've done because it processes the rw5 OK, and computes the closure and compass adjustment OK too.

Yes, you can cut and paste your data to put the traverse at the end of the set up, but I've never had a problem like this. We usually measure traverse forward as the first task of a field set up, then shoot a back sight check as a sideshot, then shoot any other sideshots, including a final back sight check at the end of the set up. Carlson has never given me any attitude about this order of data in the file.

That is a dumb requirement, but I seldom use the traverse command in my SMI either. Almost always I shoot the traverse point as a side shot. By using the traverse command, after the shot the instrument point is moved forward, so you would have to move it back to add shots. Neither do I always shoot my side shots first. Quite often I am unsure how much I want from the setup so I may shoot a future traverse point or two first, then gather side shots. I may even shut down and look for other corner markers I may need. If found I may be able to shoot them from where I am, from an already set future traverse point or I may have to set a side traverse point to simplify my work. If it is late in the afternoon I may set multiple traverse points first and be unable to finish all side shots by end of day. That gives me the option of moving ahead on my traverse the next day, maybe even closing out the traverse and I may not get back for the missed side shots until the third day. Working as a one man crew, I keep a lot of options open. Because I do a lot of work in parking lots, quite often my last shot is to tie into a mag nail I had not seen when setting up, just in case when I come back, parked vehicles may block my first choice for a setup.

My max to date is to shoot a BS and 3 foresights in one setup using the SMI shots routine. I have even mixed D&R and 2D&2R shots in the same string. Start out with the BS shot for angle only, a foresight angle and distance to the backsight (separate point number, which I may or may not include in a LS if I even do an LS), then turn for each additional FS, flop scope and turn left all the way back on each point. Typically though I usually only haul around three bipods with 5' rod heights. It is easy to set a tripod for 5' rod height, especially when you remember to bring an adjustable height tribrach adaptor, I have one with an optical plummet included.

Last fall I had one setup where I eventually saw two mags within 6' of my TP on the third time that I had occupied that point. Excess gravel on asphalt hides a lot. I had an inkling that they were there somewhere because across the intersection I had occupied a found MAG because it was a more GPSable point than the TP I set.

Paul in PA

As a Carlson user I wonder why you do not process your data using SurvNet. One great advantage of least squares is that it doesn't matter (much) what order the data is entered.

I dont use the traverse command in the store points as it is only able to store one set. I normally collect 4 sets as it is the job requirement. So I use set collection to collect the traverse then switch to store points to do my topos after the sets are collected

I will try set collection instead of traverse next chance I get . . . thanks for the tips . . . how hard/easy is it to include GPS in SurvNet?

I just run it through SurvNet and never worry about the fancy commands.

I enter in old 2d fieldbooks all kinds of hacked apart and Carlson never recognizes anything near the closed loops, but SurvNet is quite happy. They surveyed weird back in the day... limited redundancy, POLs, ties into other traverses without re measuring those lines... but still had decent closures and the results usually import just fine. Except for last week when we used 5 bounds and 3 had moved position. One was noticeable and near a road. The other two were atop a retaining wall installed after the original survey... had to go out and get more to prove that it was not slop.

Peter Lothian - MA ME, post: 422477, member: 4512 wrote: Yes, you can cut and paste your data to put the traverse at the end of the set up, but I've never had a problem like this. We usually measure traverse forward as the first task of a field set up, then shoot a back sight check as a sideshot, then shoot any other sideshots, including a final back sight check at the end of the set up. Carlson has never given me any attitude about this order of data in the file.

Peter,
When I go to process the file, it gives me an error message about there being a wrong point number on a certain line. I will try to cut and paste, and see how it works. Thanks for the help.

Mark,
I will give SurvNet a try. I need to determine what reasonable weights are for my equipment. Thanks.

Dale Yawn, post: 422545, member: 492 wrote: Peter,
When I go to process the file, it gives me an error message about there being a wrong point number on a certain line. I will try to cut and paste, and see how it works. Thanks for the help.

Mark,
I will give SurvNet a try. I need to determine what reasonable weights are for my equipment. Thanks.

I don't know why it's giving everyone problems. I never use Traverse or Set Collection, and my last shot is almost never the closing shot. Also, I don't bother with editing/inserting Traverse or Closure commands. The software lets you choose the closing points and line in the processing.

I'm guessing there's something else causing the issues.

JPH,
It may be pilot error on my part.

Dale

Michael Arsitz, post: 422524, member: 12639 wrote: I will try set collection instead of traverse next chance I get . . . thanks for the tips . . . how hard/easy is it to include GPS in SurvNet?

Set Collection . . . that's the ticket . . . !

Add a back sight after the traverse shot.