While I'm in FULL agreement that the Survey Database is a flawed system that leaves MUCH to be desired, I'm having a hard time making the jump away from .fbk files.
For our GPS data, we already dump .csv files, and about 90% of our work is GPS, so its getting to be more and more of a moot point, however I just cant get away from wanting the raw measurements from the Total Station.
I guess its mostly one of those "we've always done it this way" things, wanting the raw measurements recorded so that you can track down any issues that arise later, and see the methodology that was followed along the way... I guess one could argue that the raw measurements that we were used to in the past are no longer collected in the same manner. Since everything gets measured in meters and radians, and viewing an Angle Right and Slope Distance in Feet is already introducing some level of conversion, so why not make the jump to dumping a .csv file?
Of course I'm writing this at the same time as I'm trying to generate a custom .frt file to export a slightly tweaked .fbk file from our new Total Stations that will generate linework the same way we used to when using TDS... So the more frustrated I get trying to generate that file, the more I'm leaning towards doing away with the .fbk files!
Thanks for your insight and assistance on the survey side of Civil3D!
There are some key areas where we want to see the raw data from within a DWG (since Autodesk has decided that that's their [limited] RDBMS system). Everyone wants to share DWG. External RDBMS systems add complexity to sharing data.
That's where we are, even if it's not where I wish we were.
There are times when we want to know certain information inside our C3D DWG, such as what shots come from which control points, and what the rod hight was, etc. And the SDB tends to support that information. But we also need to be able to graphically edit information, and the SDB does not allow that. So we're in a "quagmire"...