ArcGIS Pro's November update brings OpenRoads corridor geometry into GIS
Esri's November ArcGIS Pro release brings Bentley OpenRoads Designer corridor geometry and TIN surfaces into GIS. It also lets analysts propagate Building Layer settings for more consistent setup and adds Fine, Medium and Coarse graphic detail options for Revit models.
This story was produced through MarketScale. See how Engineering & Construction teams put it to work with Partner & Channel Enablement.
Key takeaways
ArcGIS Pro now reads alignments, profiles, station equations and TINs from OpenRoads Designer, letting GIS teams combine corridor design data with Revit structures and Civil 3D site work in a single map
Preparation work for BIM-to-GIS conversion moves upstream to model setup: choices about graphic detail, fields, definition queries and coordinates now land with whoever configures the design before Esri does the conversion
GeoBIM’s new “3D ArcGIS” view workflow filters Revit content at the source, and ArcGIS Enterprise 12.2 adds a pre-sync analysis report to check georeferencing and coordinate system details, flag missing information and link to resources for fixes.
Free workspace
Turn your Engineering & Construction expertise into content.
Record interviews, organize footage, and write with AI on a free trial of the MarketScale platform for qualifying companies. No demo required, no credit card.
Road designs built in Bentley's OpenRoads Designer now have a direct audience in GIS. Product manager Michael Davidson, a licensed professional engineer in Florida with more than 10 years in civil engineering software development, laid out the changes in a Nov. 19 post on the ArcGIS Blog.
GeoInformatics covered the update a day later and described it as bringing transportation design data into BIM-GIS workflows with fewer conversion steps. That is the promise. The more useful question for a GIS lead on an infrastructure project is where the preparation work goes when ArcGIS Pro does less of the converting.
The choices that decide whether engineering data is usable in GIS (how much graphic detail to keep, which parts of a Revit model sync, whether the coordinates are right) are landing earlier, with whoever sets up the model.
Corridor geometry from OpenRoads
Transportation projects rarely live in one design tool. Davidson's post gives the typical mix: roadway, rail, bridge and site design authored across several engineering systems, with GIS teams expected to show how they relate. The November release gives ArcGIS Pro access to four kinds of OpenRoads Designer content: alignments, profiles, station equation information and TINs. TINs carry the existing and proposed ground surfaces.
Getting all four from OpenRoads means a corridor's design logic can arrive in GIS alongside the Revit-authored structures and Civil 3D site work around it. For a GIS team supporting a corridor where roadway design lives in OpenRoads and the bridges or stations live in Revit, that is the difference between a map of the pieces and a map of how they meet.
The November release also reads differently next to the one Esri shipped six months earlier. Davidson's May 14 post on ArcGIS Pro 3.7 focused on Autodesk and IFC content.
- May 2026 (ArcGIS Pro 3.7): the BIM File to Geodatabase tool accepts building layers as input, including definition queries
- May 2026: a new Create Terrain from BIM tool builds terrain datasets from TIN surfaces in Civil 3D and IFC files, including geological surfaces from GeoDin Ground
- May 2026: Revit piping systems (pipes, fittings, accessories, flex pipes) come in as linear feature classes that support network tracing
The terrain tool is the closest precedent for the new OpenRoads TINs. In May, Esri said bringing TIN surfaces into scenes had previously taken multiple steps to convert and prepare the data. Create Terrain from BIM lets analysts work with constituent surface data such as breaklines and boundaries, or derive elevation layers for a site-specific definition of ground. The piping change was pitched at a different job: moving as-built BIM content into asset management workflows as working spatial features.
The pattern suggests Esri is filling in civil and infrastructure formats one source at a time: Civil 3D and IFC surfaces in spring, OpenRoads corridor geometry in the fall. Neither post says what comes next, so teams with other design platforms in the mix should treat this as progress on specific formats, not general coverage.
Fewer repeated clicks, plus a detail dial
Building Layers hold dozens of component layers for architectural, structural, mechanical, electrical and other disciplines. Until now, tailoring one for a specific workflow meant making the same change layer after layer. The November release lets an analyst set fields, time settings and definition queries on one layer and then push those settings across the whole Building Layer or to a single discipline.
Davidson's post does not list which other layer properties, such as symbology, carry over, so testing that on a real model is worth an hour before anyone builds a workflow on it.
Esri pitches propagation as a consistency feature across complex BIM datasets, not only a time saver. It also lines up with the May release. Because BIM File to Geodatabase now accepts building layers, definition queries included, a query set once and propagated across a discipline could carry straight into the features written to the project geodatabase instead of being rebuilt layer by layer before conversion.
The second change is a choice of Fine, Medium or Coarse graphic detail for Revit models, which also applies when creating GIS content from BIM data. Esri pairs it with broader performance gains for BIM work and says lower detail can shrink derived GIS content when it fits the intended audience and use case.
Pick the detail level per deliverable, not per project. Agree up front who each published layer is for, and keep Fine for the people who need to read the model itself.
That qualifier is the counterpoint. Coarse makes sense for a context scene in front of a planning board. It makes less sense when the GIS layer is meant to stand in for the model in asset work, the use case the May piping-centerline feature was aimed at. Smaller files are only a saving if nobody has to go back to the source for the detail that was dropped.
The Revit view that decides what reaches the map
The clearest example of prep work moving upstream is on the Autodesk Forma side. In a Nov. 17 post, Esri's Geoff Cook and Nora Nanov described ArcGIS GeoBIM in ArcGIS Enterprise 12.2. Its Add Document Models tool can now sync a Revit model through a dedicated 3D view named "3D ArcGIS". Only the families and categories visible in that view come across.
The workflow starts in Revit: build the "3D ArcGIS" view, publish it to Autodesk Forma (formerly Autodesk Construction Cloud), and GeoBIM produces a filtered, simplified 3D model from it. Esri says a purpose-built view yields cleaner models focused on the most relevant project information and speeds up processing.
The same release adds a pre-sync analysis report that checks georeferencing and coordinate system information, flags what is missing and points to resources for fixing it. A post-sync error report explains why a sync failed or finished with errors, gathering job errors in one place and linking to troubleshooting material.
Viewing and contributing to shared GeoBIM projects takes a Contributor user type or above, in ArcGIS Online and ArcGIS Enterprise 11.4 and higher. Creating projects takes a Creator, Professional or Professional Plus user type plus Autodesk Forma licensing.
Two more 12.2 changes widen what can sync cleanly. GeoBIM now interprets location information more reliably across IFC versions, which Esri says makes IFC handoffs into GIS more predictable and cuts the risk of misplaced models. It also supports Revit 2026 and 2027 models in both 2D and 3D views, adding 3D to the 2D-only Revit 2026 support that arrived in Enterprise 12.1.
In ArcGIS GeoBIM, the Add Document Models tool syncs only the content visible in a Revit 3D view named "3D ArcGIS". That makes the view a reasonable thing to name in a BIM execution plan or a consultant's deliverable list, with an owner and a definition of what it should contain.
Coordinates are the other upstream decision. Esri's GeoBIM georeferencing documentation ranks the Revit options plainly. Linking a Civil 3D drawing with shared coordinates is the most accurate. Specifying coordinates at a known point suits projects with a reliable reference coordinate but no survey. Using Revit's geographic location is the least accurate and is meant for early phases when only an address or rough latitude and longitude exist.
The options also differ in what they ask for next. With a linked Civil 3D drawing, Revit inherits the real-world grid, and a projection file is needed only if the coordinate system has no EPSG or WKID code. The known-point method anchors a point by Easting, Northing and Elevation, optionally with an angle to True North, and always needs a projection file or a WKID. Geographic location needs neither, which is convenient, and Esri warns it can leave documents in the wrong real-world spot.
The documentation treats all of this as planning work. Before anyone runs GeoBIM, it calls for an information management plan with a standardized project coordinate system and consistent units. For CAD files it names Civil 3D as the primary georeferencing source when it is on the project, recommends ArcGIS for AutoCAD over native AutoCAD georeferencing tools, and covers selecting a coordinate system for .dgn files in Bentley MicroStation.
Units can move a model too. Esri's GeoBIM documentation notes that Revit defaults to feet, which nearly match international feet, and that mixing those with U.S. survey feet can shift a model by a few inches at large coordinate values. Revit's Feet (Survey) unit setting avoids the gap.
IFC files come with their own checklist. The documentation recommends IFC 4.3 or IFC4 where possible and confirming that the IFCSite, IFCProjectedCRS and IFCMapConversion entities exist in the model. When IFC bounding boxes land somewhere unexpected, it lists three likely causes: the wrong reference coordinate system chosen at export, shared coordinates not published to every file linked to a Revit model, or a model placed far from the origin. All three trace back to the authoring software, not to GIS.
The new pre-sync report checks the same georeferencing and coordinate details the documentation warns about. It catches problems sooner. Fixing them still happens in the authoring tool, by the people who set up the model.
What moves when teams upgrade
Esri recommends pairing companion versions of ArcGIS Pro and ArcGIS Enterprise, or staying within a range of two companion versions when that isn't possible. Teams running both products may want to check this before upgrading. The ArcGIS Pro 3.8 release notes list Enterprise 12.2, the version carrying the GeoBIM changes above, as its companion. ArcGIS Pro 3.7 pairs with Enterprise 12.1.
The 3.8 release notes also remove, move or deprecate several items that touch existing workflows:
- The Location Referencing tab is gone, with its tools moved to the Linear Referencing tab
- The Find Routes tool has been removed and replaced by Locate Route and Measures
- The Location Referencing toolbox is deprecated, with its tools and toolsets moved into the Linear Referencing toolbox
- PostgreSQL 14.x is no longer supported
- The CameraOrientation field in the oriented imagery table is deprecated; it still works, but Esri recommends other standard orientation parameters
- The utility network shortest path trace type is deprecated and will keep working until the next major release; Esri recommends the path trace type instead
The utility network item needs the most planning. Path trace returns the same shortest-path result and adds more ways to find paths, but it isn't yet supported on every platform, and some clients, APIs and SDKs will only pick it up in later releases. A team that runs shortest-path traces from more than one client may have to keep the old trace type in some places while it switches others.
The next dated change is already announced. In ArcGIS Pro 3.9, the DSM Mesh and 3D Mesh surface products will merge into a single Mesh option that picks the mesh type automatically, affecting the Reconstruct Surface tool and the reality mapping wizards. Teams that rely on either product can keep using it in 3.8, but Esri says workflows should be updated before the move to 3.9.
Sources
- What's New for BIM and CAD in ArcGIS Pro (November 2026) ↗
- ArcGIS Pro November 2026: BIM, CAD and OpenRoads support ↗
- ArcGIS Pro 3.7: Connected Workflows, Better Project Outcomes ↗
- What's New with ArcGIS GeoBIM in ArcGIS Enterprise 12.2 (November ... ↗
- Georeferencing workflows, ArcGIS GeoBIM - Documentation ↗
- Release notes for ArcGIS Pro 3.8 | ArcGIS Pro documentation ↗
Your experts belong here
Every story in MarketScale Engineering & Construction starts with a company putting its project engineers, superintendents, and estimators on the record. Buyers are already reading this topic. The only question is whose experts they find.
Owners shortlist firms they already trust, and your field leaders become the reason your name is on that list.
About the author
The MarketScale Newsroom reports on the companies, technologies, and trends shaping 16 B2B industries. It turns primary sources and expert commentary into clear, useful coverage for the people doing the work.