We are currently collecting with survey pro software and exporting .raw and .job files then converting .raw file using acad’s survey link to field book file (.fbk) for import into acad Civil 3D we are able to code it such that it does come in very nice with line work, labels, blocks and layers, adjustments are awkward in C3D but they work. The problem I am having is it seems the collectors could be doing much more and I am still converting to a file format(.fbk) from 2003. I don’t know maybe it’s still the way to go? I recently learned we have the ability to use the .survey data file which seems would be great for the field crews production and flexibility. But how do you work it with C3D? Thanks for any help here……………
I wouldn't complain much about the .fbk file format. I am not currently using LDT or C3d but I still sometimes convert my raw data to that format just because it is much more readable than any other.
And for that matter, the formats of StarNet (.dat), TDS (.rw5), and who knows what others haven't changed, save for a few tweaks, in a couple of decades.
If you are using Survey Pro 5.xx export the file to a job & raw file. Then everything is the same as you have been using.
> We are currently collecting with survey pro software and exporting .raw and .job files then converting .raw file using acad’s survey link to field book file (.fbk) for import into acad Civil 3D we are able to code it such that it does come in very nice with line work, labels, blocks and layers, adjustments are awkward in C3D but they work. The problem I am having is it seems the collectors could be doing much more and I am still converting to a file format(.fbk) from 2003. I don’t know maybe it’s still the way to go? I recently learned we have the ability to use the .survey data file which seems would be great for the field crews production and flexibility. But how do you work it with C3D? Thanks for any help here……………
Since C3D 2010 (I think, maybe 2011), you don't have to convert your RAW files to FBK files to import linework, symbols, etc. Most of the time, at least in my experience, the FBK files are junk. Civil 3D has a big problem with fieldbooks if you delete points that linework goes through or perform any transformations/translations in the data collector. There's more problems that I've incurred but can't really remember them now that we don't use the fieldbooks anymore.
You can simply import your point files (txt, csv, asc) into the C3D survey database and if the descriptions are coded correctly according to your Linework Code Set, it will generate linework very well and will stylize them and place them on layers according to the Figure Prefix Database. The same goes for your points. If coded correctly and C3D is setup to look for that certain description, it will insert blocks and put them all on the layer you choose.
It sounds like you've already setup Civil 3D to do all of this with your fieldbooks; however, you can simply use an exported point file to do the same without the hassle of converting to a fieldbook.
The only major difference, if it matters to you, is that by using simple text files instead of fieldbooks you lose the ability to modify traverses and setups. And you don't get the the awesome survey animation. If you're interested in that then you must stick with the terrible fieldbooks.
Corbitt
we do as Mr. Corbitt does as described above.
Thanks for the comments.....just wondering if we don't use the fieldbook import what program would you use in conjunction with the survey pro software to do your adjustments and still have the ability to ouput the pnezd file to C3d with full function? Thanks..............
Under your 'Home' tab, you should see a pull down box with 'Create Ground Data' Choose Survey Data Collection Link, and import your .txt file
There are different ways you can then improt that .txt file into C3D.
Joe
We also use that method, and simply import a CSV file. We lay out control first, then do the data collection later, so the data doesn't need to be adjusted. It means we can't collect data while setting control, so we go through the site twice, but we find it works better and faster overall. We also lose some of the raw information reports in C3D, such as rod HIs and which shots were taken from which control points, but find that information rarely useful, and can process the data in C3D far faster by using a CSV file. And should we ever need to access that other information, we can look into the job file (which happens VERY rarely).
This method also works better if we use GPS (with maybe our digital level, on some jobs) to set control points.
> Thanks for the comments.....just wondering if we don't use the fieldbook import what program would you use in conjunction with the survey pro software to do your adjustments and still have the ability to ouput the pnezd file to C3d with full function? Thanks..............
I like to try to keep everything as simple as possible. The more I put data into multiple programs the more chance something will get screwed up. Therefore I like to do all the adjustments in Survey Pro. The data collector can do just about everything you need and that eliminates a chance to screw up. Many, many times have I brought jobs into the computer, adjusted a traverse and translated points, and then sent a crew back out to the job without those adjustments because they didn't make it back into the collector. If the traverses are closed and points are translated before they make it to Civil 3D then I feel much better. That way both sets of data should jive. This process works for us 99% of the time. The Survey Database in Civil 3D can translate points without the need for a fieldbook; I also think you could get it do perform a traverse adjustment but it would not be nearly as easy if you had a fieldbook.
If you aren't having any trouble with the fieldbooks and find them easy to make, then I'd say continue to use them. I've just had too many problems with getting them to convert correctly.
I do the same thing. Adjust almost all my stuff in DC then import.
Now most of my surveys aren't over a very large area, so my adjustments are small, if any.
Joe
I have two data collectors with Survey Pro 5 one is new and the other was just upgraded. When I export to job/raw I get alot of invalid data lines in the raw file and cannot convert to fieldbook, any assistance on what I am doing wrong would be helpful not getting much help from Spectra.
All - I know that this is an older thread, but can somebody give me the quickest workflow/steps for preparing data for the data collector (as a .csv, .txt, etc.) for stakeout in the field and then for importing back into C3D?
Thanks!
How are you converting your Survey Pro Raw & Job files to FBK files? I can't figure out how to do this in this in the Data Collection link software we have in Civil 3D 2012, which is Survey Link DC 7.5.5. I can only convert them to ASCII files like the others on this thread are, which is fine most of the time - but there are times that I need to correct errors made in the field (such as a busted rod height or whatever) and I can do that pretty easily in an FBK file.
Never mind - I finally figured it out myself. 🙂