I am wondering how many download a coordinate file only from the data collector versus downloading the raw data file and running it through an adjustment. I have seen a lot of both, so I am wodering what is most common.
Raw data to TBC or Carlson, export pointdata with codes and notes from there, then CAD.
Too many field mistakes would slip through with just a coordinate file. Raw data is the only way to go for QA/QC.
I am another adjustment person. All data, even a 1 station topo, goes through Star Net. Not because it needs adjusting sometimes, but because using the same process every time is easier. And usually, it does need some adjusting.
Ken
I rarely accept the coordinate file without at least examining the raw data. I "adjust" it, using StarNet, most of the time. The only times I might not is if I am solely occupying previously adjusted control to collect topo or do stakeout. And even then I usually do.
I've worked in quite a number of places and, in my experience, a majority of people rely on the coordinates dumped from the dc. Many have no idea there is any other way. They wouldn't have a clue how to do an adjustment. The thing is - those people are not likely to be visiting this website to answer questions like this. So the response you get here is skewed.
*"adjusting" is frequently not really adjusting at all, but rather recalculating after amending rod busts and descriptor problems.
We download the raw data files to back them up on our drive, but we typically only use the coordinate file. We bring in the coordinate file through the survey database in AutoCAD Civil 3D, which creates our symbols for cogo points and linework for survey figures.
If we need to make an adjustment (translation and elevation adjustment), based on an OPUS solution on one of our control points for example, we use the translate survey database function.
Curious to know what type of adjustment others are mentioning. Is this a daily adjustment of survey data based on check shots of site control?
Each place I've worked has done it a little differently. Most wanted a copy of the raw data and a coordinate file everyday, but some only worked with the raw data at the beginning of a project and then coordinate files after that.
Raw data into TBC, coordinate values into CAD.
@ john-hamilton
We've been adjusting raw data (traverse point elevations - for a topo) in our data collector and coordinate data (traverse point N, E - for a traverse adjustment) in our CAD software. The best thing you can do for yourself is to keep a record of setups and point blocks in your field book. We download .txt, .RW5, .fbk, and .mjf files daily.
Raw database processed and adjusted in Infinity then coordinates and linework exported to C3D. I have been doing this since the late 80's. The processing software has changed a bit from WildSoft through LisCAD to Infinity. Processing raw data lets me mix and match terrestrial and GNSS data as well as provides a good opportunity for QA/QC of the data collected.
There are few occasions when I will just output coordinates and linework straight from the DC. For instance, if I'm just collecting a few specific fill-in points for an engineer from known control or RTK. But these occasions are far and few between.
I am with @MightyMoe
All raw data imported to TBC. Coordinates exported for downstream use.
I have always imported the RAW files into Carlson. The only way to QC and adjust in survnet.
I can look back at RAW files and see what and how the field work was done. Looking at old coordinate files all you see is points, nothing else.
Never understood why so many surveyors just download the coordinates from the data collector and just throw away the field notes.
