Comments on: Carlson Civil Suite Part Two - The Overview http://www.civil3d.com/2006/10/carlson-civil-suite-part-two-the-overview/ Tue, 06 Jan 2009 20:25:18 +0000 http://wordpress.org/?v=2.5.1 By: Jason Hickey http://www.civil3d.com/2006/10/carlson-civil-suite-part-two-the-overview/#comment-563 Jason Hickey Fri, 10 Nov 2006 02:32:30 +0000 http://www.civil3d.com/index.php/2006/10/carlson-civil-suite-part-two-the-overview/#comment-563 cadtag - to each his own, but there are issues with the "external database" theory as well. What happens when two people try to edit that database at the same time in Land Desktop? If you're able to do it, it creates really bad problems, sometimes corrupting the database and forcing a recreation of all the data in the process. I happen to be a fan of the object in Civil 3D, and with data shortcuts *or* Vault, have had no problems sharing that data to members of a workgroup. Once you get a workflow implemented that has been proven to work (as James is documenting right now), you'll have no problems with the objects being shared. Many people are using this with great success now - like what you will, but it's what we're going to. There are many advantages to this model, and things are only going to get better from here. cadtag - to each his own, but there are issues with the “external database” theory as well. What happens when two people try to edit that database at the same time in Land Desktop? If you’re able to do it, it creates really bad problems, sometimes corrupting the database and forcing a recreation of all the data in the process.

I happen to be a fan of the object in Civil 3D, and with data shortcuts *or* Vault, have had no problems sharing that data to members of a workgroup. Once you get a workflow implemented that has been proven to work (as James is documenting right now), you’ll have no problems with the objects being shared.

Many people are using this with great success now - like what you will, but it’s what we’re going to. There are many advantages to this model, and things are only going to get better from here.

]]> By: cadtag http://www.civil3d.com/2006/10/carlson-civil-suite-part-two-the-overview/#comment-561 cadtag Thu, 09 Nov 2006 13:01:08 +0000 http://www.civil3d.com/index.php/2006/10/carlson-civil-suite-part-two-the-overview/#comment-561 <blockquote cite="...I discover that we’ve left the Civil 3D theory that all data is stored in the drawing, and have gone back to the project database/external file structure.."> Jason, you say that as though it's a bad thing, when separating the alignment, surface, point, etc data from the dwg and storing it externally to the drawing file avoids the single largest architectural fiasco in Civil3D. The software design decision to store everything in the DWG as an 'object' is a poor choice, because it creates many more problems than it solves, and results in kludgey, fragile work-arounds such as Data Shortcuts in XML, and Great Chthulhu save us - Vault as a data sharing repository for alignements. External data on a network is inherently more useful and accessible to members of a workgroup. While LDT's implementation could have been improved in numerouse ways, thowing it out in favor of the C3D model is thwoing the baby out with the bathwater.

Jason, you say that as though it’s a bad thing, when separating the alignment, surface, point, etc data from the dwg and storing it externally to the drawing file avoids the single largest architectural fiasco in Civil3D. The software design decision to store everything in the DWG as an ‘object’ is a poor choice, because it creates many more problems than it solves, and results in kludgey, fragile work-arounds such as Data Shortcuts in XML, and Great Chthulhu save us - Vault as a data sharing repository for alignements.

External data on a network is inherently more useful and accessible to members of a workgroup. While LDT’s implementation could have been improved in numerouse ways, thowing it out in favor of the C3D model is thwoing the baby out with the bathwater.

]]>