From time to time I plan to invite people who have an interesting perspective (based on real world experience) that reinforces some of the themes that I have been focusing on to contribute to this blog. Sharing spatial data especially between CAD and GIS has been a theme of several of my blogs, and I invited Charlie Crocker who has worked in the geospatial arena for over 15 years in the western US, to give his perspective.
Separation of GIS and Engineering
To manage and maintain a current and accurate record of infrastructure, a GIS specialist in a city’s public works department is commonly required to work through an extensive backlog of field updates and as-built information about the precise locations and details of city buildings, roads, bridges, sewer systems and other infrastructure. This data is seldom readily accessible from the CAD system in the Engineering department and requires time consuming processes to translate and transform into GIS data.
GIS professionals know how hard this task really is in most cities. You need to request the information from someone in another department and then convert the data from one format to another format. It is a process that can take days—or even weeks. It likely requires some custom programming. What’s more, it often leaves the resulting information full of holes. Have you ever exported a true arc from CAD to a Shapefile or tried to maintain attributes transferring data from GIS to CAD?
There’s not just a physical wall between GIS and Engineering departments. There’s a “wall of mystery” that has separated the CAD and GIS worlds for years, a cultural divide leaving practitioners on both sides wanting more and often feeling alienated by the other.
From a technology standpoint, CAD engineers have been blessed with intelligent, powerful graphical tools that allow them to produce highly detailed design specifications of buildings, bridges, machinery, utility assets, and even spacecraft. Whereas, GIS specialists take advantage of incredibly robust spatial databases, perform sophisticated spatial analysis, and generate compelling “beautiful maps”.
Here are three of the many benefits of tools that merge CAD and GIS capabilities and organizations where Engineering and GIS departments work together:
Benefit 1: Leveraging Existing Resources
By working together CAD and GIS teams have a lot to gain. GIS teams can leverage the abundance of CAD-trained domain experts to help maintain data and provide a detailed understanding of specific workflows, and data relationships. CAD teams can leverage centralized GIS databases to efficiently store and share valuable infrastructure information. There is no need for either the GIS or CAD teams to prescribe the tools that the other should use. The technology is available to allow each team to utilize the toolsets and environment they are familiar with.
Benefit 2: Stomping Out Data Redundancy and Conversion Errors
There is great value in providing CAD engineers robust, native access to spatial datastores like Oracle Spatial, My SQL, and ArcSDE and giving GIS professionals direct access to object-based design data stored in CAD files. Native data access means no conversion, no data loss, no data copies, and best of all no stale data. This can mean not more hunting around for the most current version of the data or making decisions based on information that might be out of date.
Benefit 3: Streamlined Workflows
By leveraging the power of both CAD and GIS, asset management, utility companies, engineering consulting firms, public works departments, and more are able to build more efficient workflows. For example, a project moves more quickly when an engineer can easily pre-populate a new design with current base map data from a central GIS—such as property lines, curb information, and other associated data. And by using simple theme mapping and legend based map controls, a CAD designer has much more flexibility stylizing objects and ordering layers in a CAD drawing. GIS specialists can leverage powerful precision editing tools in a CAD system to more easily edit and maintain GIS data.
CAD/GIS Integration Brings Engineering and GIS Together
Infrastructure development and management companies are beginning to understand the need to use both engineering-design tools and mapping technology together and to seamlessly work with CAD and GIS data together in a single. Integrated CAD/GIS tools lets you directly access spatial databases, like Oracle Spatial and ArcSDE, and GIS data and work with them in a hybrid CAD and GIS environment. With a combination of smart, spatial databases and intelligent CAD-based graphical editing tools, organizations can recoup lost productivity, improve data accuracy, and streamline workflows.
And best of all, by blending the two technologies you gain the benefits of working with high precision data in a seamless map-based environment. Imagine being able to seamlessly search for a parcel and also being able to precisely locate the utility connections and detailed design information related to structures on the property. Or, why settle for a single polygon representing an entire airport when detailed design drawings are available?
Typically, organizations have invested in both CAD and GIS. They bought powerful, industry standard CAD tools for engineers and drafters to precisely design roads, buildings, and other assets and deliver detailed specification, as well as traditional GIS application suites to conduct spatial analysis and generate maps of more generalized information. Each group developed its own separate workflows, standards, and data – despite the fact they often managed similar data and both had a skilled workforce of spatial data practitioners.
The Spatially Enabled Engineer
Let’s consider a civil engineer who needs spatial information for context and a starting point for the location and engineering design of a new bridge. How does he work with his GIS counterpart? They improvise. The engineer makes a request to the GIS department; data is compiled, converted and maybe even digitized. Through a lengthy and convoluted workflow, chances are good they’ve also introduced errors, stroked arcs, missed attributes, and lost valuable precision.
CAD and GIS professionals alike are beginning to see the advantages of each others technology and of working together share data, processes, and personnel. Engineering departments have teams of data management professionals (called engineers, designers, or CAD drafters) who manage large quantities of spatial asset information using CAD-based tools. It is not uncommon to find an engineering department with 50-100 CAD trained professionals in an organization with 1-3 GIS professionals. Providing CAD engineers with mapping functionality and native access to spatial databases opens the door to a much larger spatial data workforce that can be leveraged to support the expanding role of spatial information.
In today’s competitive environment and shrinking budgets both public and private organizations are finding it costly to maintain separate CAD and GIS functions. It is expensive to manage multiple types of software, convert data, synchronize systems, and keep design and operations disconnected. And it is also difficult and expensive to purchase new software and retrain CAD or GIS professionals to use the others technology.
I have worked with several public works departments and both public and private utilities that have small GIS departments scrambling to keep up with work orders, and the constant stream of as-built drawings and changes from the field. In many cases these same well-trained and experienced GIS specialists and managers are not domain experts when it comes to the infrastructure they are asked to manage. These same organizations have a well-trained CAD workforce that are domain experts, understand the utility network, how it is built, what issues need to be addressed and what needs to be tracked. What is even more compelling is that the GIS managers are finding it difficult to hire and retain well-trained GIS professional, especially any with specific domain expertise. These GIS managers are beginning to look inside their own organizations to find domain experts with an understanding of spatial data and finding a large pool of potential in their organizations engineers, designers, and CAD drafters.
By bringing these two worlds together, CAD and GIS professionals can work together to share information—geospatial and design data—transparently among project team members. If needed, the data can travel to downstream users, such as operations managers, facility managers, and field technicians - even to the general public via web sites. With CAD/GIS integration, organizations can use existing resources, reduce data redundancy and errors, and streamline workflows. As a result, they complete projects faster—and at lower cost.
Engineering and GIS professionals need tools that bridge the divide between CAD and GIS without necessarily asking either the CAD or GIS professional to give up the tools they have been using for years. In other words, it means bringing GIS and mapping functionality into the precision data capture, creation, and maintenance tools in a CAD environment, including native access to spatial databases. And, in addition, it means providing the GIS environment with the ability to access and work with object-based design information stored in CAD drawing without losing precision through data conversion.
Integrated CAD/GIS offers tools for engineers and designers to use their design-rich CAD environment to customize, manage and publish designs, and easily bring them into company's GIS system. A common data access API provides a bridge between the CAD design environment and GIS data stored in many leading formats like Oracle Spatial, SHP, ArcSDE, SDF, and MySQL. (To make this easier Autodesk recently provided the code for many of its FDO providers to the open source community available free for anyone to use or contribute to, see http://www.osgeo.org.)
Essentially, the technology supports a streamlined workflow. People can create and edit with CAD tools, and store the data in a central place for other people and applications, including GIS applications, to access. This type of data organization and workflow leverage the best technologies without losing valuable information by translating data from one format to another.
Conclusion
There has been a cultural divide between CAD and GIS propagated by the “wall of mystery” surrounding GIS. CAD/GIS integration provides the ability to seamlessly work with both CAD and GIS data within a single environment and the power to blend powerful CAD design tools with robust, well-managed geospatial database is no longer a mystery. It is easier than ever for engineers and GIS professionals to work together, leverage each other’s domain expertise, and share information. We all work in hybrid IT environments with many different applications and databases. Our success is predicated on our ability to work together to blend our technologies, experience, and understanding. We will not be successful if we build walls and eschew technological diversity. The longer the “wall of mystery” remains, the deeper the divide with grow. Now that the technology is out there, it is demolition time.
Hi Geoff,
Nice Article. Great read. The environment in my company is exactly like you had discussed above. We just bought copies of AutoCAD Map 2007 for our users. Given that AutoCAD Map 2007 can now do many of the ArcGIS functionalities, how do you ArcGIS being used? In your opinion can AutoCAD Map 2007 replace ArcGIS? Is ArcGIS's use limited only to database administartion(ArcSDE). I would appreciate your opinions on the matter.
Thank You,
Vish
Posted by: Vish | June 05, 2006 at 12:48 PM
Great article Geoff.
I really like the phrase "wall of mystery". Years ago computer analysts were dark priests, mumbling incantations to keep the system running. GIS professionals are the current day equivalent. Now that GIS has gone mainstream IT, it's even harder to find people that understand both worlds.
It's good job security though. Can we avoid demolishing the wall if we move it away from the data, and put some nice decorations on it? :)
Vish, I really respect where Map 3D has come with the latest release, but it still doesn't hold a candle to ArcGIS. It's missing some basic items such as a metadata system, advanced cartography, strong analytical modelling capabilities, and raster analysis. There is still a need for a fully-featured desktop GIS package (ArcGIS, MapInfo, etc) in most organisations.
Jason
Posted by: Jason Birch | June 06, 2006 at 02:44 PM
Vish
I appreciate the feedback, these are very good questions.
1) A very important thing that has happened in 2005/2006 is that geospatial has now joined the IT club, and is no longer an isolated niche off by itself. What this means practically is that for people in organizations that have been using AutoCAD for design or who prefer Autodesk Map3D as a create/edit tool, there is now another option to going out an buying a traditional GIS product like ArcGIS. Autodesk Map3D provides excellent create and maintenance capabilities for geospatial data stored in different data stores including ArcSDE. In addition for organizations responsible for maintaining network infrastructure, there are very important operational benefits from an integrated CAD/GIS solution. For example, I have discussed the as-built problem in earlier blogs.
2) Another important thing that has happened in 2005/2006 is that customers are no longer locked into a single geospatial vendor (vendor lock-in). What has happened is analogous to the old mainframe days, when if you bought IBM h/w, then you were locked into IBM applications. One of the main reasons for this change in the geospatial arena are standards like SQL and SQL/MM and the fact that Oracle, IBM, PostGIS/PostgreSQL, and other RDBMS vendors now support spatial data types. First of all this means that you don't really need a "GIS datastore" like ArcSDE to store and manage geospatial data because RDBMS's from Oracle, IBM, open source,and I expect in the future MS SQLServer can do this. But it also means that customers can buy best of breed applications and share data between different vendor's applications in a common spatially-enabled datastore. For example, many people like MapInfo's anaytical capabiliites or the capabilities of other geospatial applications, as Jason has made clear. The important thing that has happened is that now there is no barrier preventing the design and records groups from using Autodesk Map3D for design and geospatial data creation and maintenance, the planning group using the same information with MapInfo, and the environment group using Geomedia, all sharing data in a commn datastore. This is important and real. As I mentioned previously at GITA this year two municipalities, Tacoma and San Jose, described how they had done this.
Geoff
Posted by: Geoff | June 07, 2006 at 08:29 AM