They taught us a whole bunch of stuff about useless features. Like the survey database, and creating traverse networks and equipment databases. We don't use the Survey database at all. The engineers aren't going to tamper with our control points since they are XREFing what we are doing. We are still creating our traverses as polylines and adjusting from there. How to work with field book files (which we don't use). They didn't show us what we needed to know (but have since learned on our own), entering a deed, for example. They showed us traverse adjustments (which we rarely perform textbook adjustments). I guess the most useful portion was learning about description key sets. But they covered NOTHING about generating points for staking all of the wonderful designs that C3D can do which was the primary question we had. 9 out of 10 people who offer up C3D training seem to know little to nothing about surveying in the real world. It is a shame.
Yeah, I don't know why they bothered with the Equipment Database. That stuff is already handled by the data collectors, as it should be. We in the office have no desire at all to worry about that stuff. Plus, if you work for a company where not all the survey equipment uses the same values, there is always the chance of using the wrong values when importing data. Meanwhile, if this is handled in the data collector itself, it's always right. Talk about wasted effort.
Working with FBK files can be useful. If you are currently "connecting the dots" when you do a design survey, then the FBK files can save you HUGE amounts of time. However, the entire FBK import process is extremely clunky, and very poorly designed. There's a program called "Stringer", written by CadApps in Australia, that does a much better job. It must be purchased separately, however. But it is probably worth the price for full-time surveyors. We haven't bought it yet, but we've been considering it, because Autodesk's FBK is so unpalatable.
The big reason we can't use the Survey Database is that it has absolutely no knowledge of GPS. Most of our jobs these days end up being a combination of GPS and conventional equipment, and C3D doesn't even know GPS exists. When GPS is used, the Survey Databases idea of a "survey network" becomes useless.
So we only use the Survey Database to import FBK files, and get linework in our drawing. Unfortunately, the Survey Database is designed with this incredibly stupid assumption that you will only ever create one EG surface in your project. Don't know how they managed to get this program through five releases, and still have that problem. We hit it IMMEDIATELY upon trying to use C3D. Laurie (again at CadApps in Australia) came up with one possible workaround for this issue,
found here. But it's sort of clunky. And since we aren't using the Vault (another misguided portion of C3D), we simply create a new Survey Database for each EG surface we create in the project. Again, this means we can't use most of the features in the Survey Database, since we now use multiple Survey Databases per project, but we weren't using those features anyway. So no big loss, but it really makes us wonder what Autodesk is thinking. They keep giving us solutions to non-problems, and ignoring the stuff we REALLY NEED...