December 14, 2007

CAD Standards from GIS with Seed Files

As the assistant coach for my daughter’s high school basketball team I have the ability to influence, but not always to decide. I can make suggestions to strategy and present ideas, but ultimately the decisions belong to our head coach. He and I have our areas of expertise and because we have a good working relationship we submit to one another in those areas. One way to describe my role on our team is as the rear driver on the ladder truck. The head coach is driving the truck with everyone on-board to our destination. I am at the back steering to keep us on the road.

When working in organizations where there are distinct GIS and CAD related activities there is often one group that takes the lead and another one that supports the overall objectives of an organization. Certainly when the goal is to WIN the team functions better when the coaches aren’t taking things in different directions.

Coordinated efforts to move data back and forth can come from mandatory decrees that come from on high, working together (preferred) , or as a result of good unilateral planning as in the case of one strategy implemented by Truckee-Donner as a unilateral program where the CAD group is not under one authority, but rather is attempting to support any number of contractors not directly under their control.

One practical way for me as a CAD manager to get better CAD files from my GIS group is to sit down with my GIS manager and provide him with a CAD seed file that already contains my coordinate system and CAD layer and symbology standards as a template. This by itself can greatly enhance the readability and use of CAD data generated by the ArcGIS EXPORT TO CAD tool, or the ArcGIS Data Interoperability Extension. Both ESRI software tools that create CAD files from GIS content have the ability to explicitly define to exacting standard entity level symbology with a multitude of configurable CAD property designations. However, with my layer-based symbology standards I can supply my seed file in anticipation of CAD entities placed on those layers to greatly simplify the process. The GIS task to generate good CAD data then only requires that I push data out to the correct CAD layers, and I get the symbology I want.

4 Comments:

Blogger Detramental said...

Don,

firstly many thanks for your informative and well-written blog.
I am currently working as a business analyst for a UK utilities company which is looking at purchasing a drawing solution to utilise both vector and raster data. I am trying to find out whether a CAD seed file would allow the user to export raster imagery along with the features or if this activity would need to be carried out in a separate CAD package post export from Arc. Unfortunately the company doesnt have a single GIS solution and as a result there is no consistent data-format available. As a result we will probably opt for an ESRI standalone solution on the grounds of versatility but would be keen to generate drawings in a CAD format including all geo-referenced raster imagery. Can you shed any light on whether this is possible? Its a big software package and im still learning!

Rich

5:41 AM  
Blogger Don Kuehne said...

Tools in ArcGIS that export data into CAD files do not support the exporting of GIS imagery. However if you have an image in a seed file as an AutoCAD entity or a dependable link to a file on the disk say... Then that would be fine. If you would like to access Maps and imagery maintained in ArcGIS Server then check out ArcGIS for AutoCAD.

http://giscadblog.blogspot.com/2007/10/new-version-of-arcgis-for-autocad-2008.html

2:43 PM  
Anonymous Anonymous said...

Don,

Would I be able to use a Seed file to associate a point feature to a block object?

8:23 AM  
Blogger Don Kuehne said...

Yes, when using the EXPORT TO CAD tool which is now available at the ArcView license level, you can export feature classes with a field called REFNAME whose value correspond to AutoCAD block names. To override the default behaior of creating simple points your output feature class must also contain a field called ENTTYPE whose values are set to INSERT. If the seed file contains cooresponding block definitions you will get the correct blocks inserted rather than simple point.

Here is more about the subject:
http://giscadblog.blogspot.com/2006/07/exporting-attributed-data-to-cad-part_11.html

http://webhelp.esri.com/arcgisdesktop/9.3/index.cfm?TopicName=How%20export%20to%20CAD%20(Conversion)%20works

8:50 AM  

Post a Comment

<< Home

FREE hit counter and Internet traffic statistics from freestats.com