CAD to GIS to BIM Interoperability

Confusion here comes from expecting one tool to do another's job. Each has a clear purpose.

CAD (AutoCAD, and the DWG/DXF formats) is for precise geometry. It draws lines, arcs and solids to fine tolerance in a local coordinate space, usually measured from an arbitrary origin. It knows shape exquisitely; it does not know where on Earth the shape sits, or carry a table of facts behind each line.

GIS is for location plus information on the real Earth. Every feature has a coordinate reference system, so it sits at true world coordinates, and every feature carries attributes you can query. GIS is weaker at fine drafting; it is unmatched at context, analysis and answering 'where'.

BIM (Building Information Modelling; Revit and the open IFC format) is for the semantic building - not just geometry but meaning: this object is a wall, of this material, with this fire rating, connected to these systems. BIM knows a building deeply; it knows almost nothing about the neighbourhood around it. CAD draws it, GIS places it, BIM describes it.

The everyday bridge is bringing a CAD drawing into GIS. Both QGIS (through the open GDAL/OGR engine) and ArcGIS Pro read DXF and DWG directly. But two CAD habits fight the transfer, and you must tame them.

First, layers and geometry types get mixed. A CAD file happily keeps text, hatching, dimension lines and real linework on tangled layers, and a single DXF entity table blurs points, lines and polygons. On import you split it into clean, single-geometry GIS layers - the roads as lines, the plot as a polygon - and discard the drafting furniture (dimensions, title block) that has no place in a spatial dataset.

Second, CAD carries no attributes in the GIS sense - the meaning lived in the drafter's head and the layer names. Expect to rebuild an attribute table by hand or from those layer names. The import gets you geometry; the information half of 'Geographic Information System' you add yourself.

The speck-at-the-origin problem is a georeferencing problem. The CAD file's coordinates are honest metres, but measured from a local 0,0 that means nothing globally. To place it, you tell the GIS how the drawing's local coordinates map to real-world coordinates - a move, rotate and (if scales differ) scale, so the survey lands on the actual plot.

Two routes exist. If the surveyor recorded real control points - known survey marks with true coordinates - you transform the drawing to fit them, which is accurate and defensible. If not, you place it by eye against a base map, matching a corner or a road, then confirm the fit. Either way, you assign the correct projected CRS for the site (a metre-based one - for peninsular India, EPSG:32643 or 32644) so that lengths and areas stay true. A CAD import without georeferencing is just a floating doodle; georeferenced, it becomes a measurable part of the model.

Moving buildings (not just lines) between BIM, GIS and 3D city models needs richer, open formats.

IFC (Industry Foundation Classes) is the open, vendor-neutral BIM exchange format - the way a Revit model leaves Revit without losing that a wall is a wall. It is building-centric and extremely detailed, in the building's own coordinate space.

CityGML is the open OGC data model for semantic 3D city models - many buildings across a city, each simplified to an agreed level of detail, with meaning attached, sitting in a real CRS. It is the city-scale counterpart to IFC's building scale. Bridging the two - taking detailed IFC buildings into a coherent CityGML city model - is an active field precisely because their scales and assumptions differ. For streaming heavy 3D to the web there is the OGC 3D Tiles community standard. You do not need to master these formats yet; recognise IFC as 'the building leaving BIM' and CityGML as 'the city holding many buildings', both open so no vendor owns your model.

Put together, the tools form a round trip, not a hierarchy. You start in GIS to understand the site: slope, context, roads, plots, constraints, catchments - the evidence a concept must answer to. You hand that context to CAD and BIM to design the building precisely, with a georeferenced site so your model sits in the real world from day one. And the finished building can return to GIS - as a georeferenced footprint, or a CityGML entry - to join the city model, feed an urban-design study, or support a development-control review.

The skill is not mastering all three tools equally; it is knowing which world owns which part of the job, and keeping the bridges - georeferencing, clean layers, open formats like GeoPackage, IFC and CityGML - intact so nothing is lost in crossing. A designer fluent in these bridges argues from a model that spans site to city; one who is not spends every project rebuilding the same survey.