Is there any legitimacy to the argument, "We use Civil3D because we are an engineering firm and it makes sharing files with other design firms easier."?
I have heard that argument many times before, but, until this year, hadn't had any experience with C3D in a production setting. Now working for a civil engineering firm forcing the survey department to make the switch from Carlson to C3D, I am struggling just to keep productivity from tanking. The biggest reason is the file/drawing compatibility with other design firms. I don't recall ever having any issue opening and manipulating the data I needed when I received a file from the civil engineer, architect, or other surveyors...
@ShaneMcDaniel wrote:
Is there any legitimacy to the argument, "We use Civil3D because we are an engineering firm and it makes sharing files with other design firms easier."?
I have heard that argument many times before, but, until this year, hadn't had any experience with C3D in a production setting. Now working for a civil engineering firm forcing the survey department to make the switch from Carlson to C3D, I am struggling just to keep productivity from tanking. The biggest reason is the file/drawing compatibility with other design firms. I don't recall ever having any issue opening and manipulating the data I needed when I received a file from the civil engineer, architect, or other surveyors...
C3D 2013, 2014, 2015, and 2016 are all backwards compatible.
File sharing with other C3D sers can be very powerful but it also can be problematic when compatabilty issues are encountered as you have noted. The data shortcut paradigm also gets to be a challenge when you exchange design updates.