The problem The Coordinate System Library used by Civil 3D, Map 3D, InfraWorks and ReCap only models horizontal coordinate reference systems. Vertical CRSs and compound CRSs (horizontal + vertical combined, as defined in the EPSG registry) simply do not exist in the library. As a result, a drawing knows exactly where it is in X and Y, but its Z values have no defined reference at all — the software cannot tell whether elevations are ellipsoidal heights, national leveling heights, or something else entirely. Why this matters more every year IFC and openBIM require it. IFC4.3 (IfcProjectedCRS) expects a compound CRS for 3D models, so that both the geodetic and the vertical datum can be unambiguously identified. Civil 3D is positioned as an infrastructure BIM tool, yet it cannot store or export the very piece of metadata the buildingSMART standard asks for. Clients and government agencies across Europe increasingly mandate correctly georeferenced IFC deliverables — vertical datum included. Practically every country has a compound code waiting to be used. Belgium: EPSG 6190 (Lambert 72 + Ostend height/TAW) and 8370 (Lambert 2008 + Ostend height). Netherlands: 7415 (RD New + NAP). Germany: 5555 (UTM 32N + DHHN92). UK rail: 9306 (HS2 grid + HS2-VRF). Surveyors and GIS platforms already speak this language; Civil 3D cannot. GNSS and drone workflows are now the norm. Ellipsoidal heights flow into projects daily. The Vertical Datum Transformation tool (a separate extension) can shift elevations using geoid models, but the result is not recorded anywhere: the drawing still carries no vertical CRS, so the information is lost the moment the file leaves your desk. It actively confuses users today. Search the library for "6190" and you get PGA98 — an Argentinian datum (the EPSG datum register happens to reuse that number), while the Belgian compound CRS with the same code is nowhere to be found. Search for "8370" and you get an empty list. Users reasonably conclude the library is broken or incomplete; in reality the data model has no place for these systems. The rest of the industry already supports it. Esri ArcGIS, QGIS/PROJ, Trimble and Leica office software all handle vertical and compound CRSs, including grid/geoid-based vertical transformations. Data arrives in Civil 3D with well-defined 3D georeferencing and leaves with only half of it. What we ask Add vertical CRSs and compound CRSs to the Coordinate System Library, searchable by their EPSG codes (6190, 8370, 7415, 5555, 9306, ...). Allow a drawing (and an InfraWorks model) to store a vertical CRS assignment alongside the horizontal one. Integrate the existing geoid-based vertical transformation into normal coordinate transformations (Map queries, IMX exchange, data connect), instead of leaving it in a separate opt-in extension. Carry the vertical datum through to IFC export (IfcProjectedCRS.Name as a compound code and/or the VerticalDatum attribute) and other exchange formats. Who benefits Everyone exchanging 3D data: surveyors delivering GNSS/drone data, designers exporting IFC to clients and public agencies, GIS teams consuming Civil 3D output, and Autodesk itself — because "where is my model, in 3D?" would finally have a complete answer inside its own ecosystem. If your projects involve national height systems (NAP, TAW, DHHN, NN2000, NGF-IGN69, NAVD88...), please add your vote and share your use case in the comments — the more real-world examples, the stronger the case.
Show More