The updates below have been made in ArcGIS GeoBIM.
General
General product updates include the following:
- ArcGIS GeoBIM now supports georeferencing Revit files using their internal coordinate system, if available.
- Revit 2026 models can now be ingested into ArcGIS GeoBIM as 2D features.
Note:
The Add Document Models tool does not support Revit 2026 models at this time.
Enhancements and bug fixes
The following enhancements and bug fixes were made:
- Support for georeferencing of Revit files using their internal coordinate system (WKID/EPSG), if available, combined with the coordinates of the Revit model, to accurately locate the model in the real world.
Note:
Revit files with internal WKT settings are not currently supported.
- ArcGIS GeoBIM now checks Autodesk Construction Cloud to identify the default view set for models and uses this to generate the geometry for the Models layer. This ensures consistent and reliable results of the Models layer output when executing the Add Document Models (Beta) tool.
Note:
If no default view is defined in ACC, ArcGIS GeoBIM will create its own.
- Creating a new issue in ArcGIS GeoBIM now requires an additional step of Autodesk authorization after clicking Create in the Create New Issue form.
- Uploading a Field Maps issue now requires an additional step of Autodesk authorization after:
- clicking the Upload button in the Table widget
- clicking the Upload button in the Edit issue form
Known issues
See the ArcGIS GeoBIM Esri Community page for a complete list of known issues and status. The following are the known issues in this release:
- The Add Document Models tool returns errors for Revit 2026 models as this version is currently not supported for generating the simplified 3D Models output. When this happens, the error log will list the failure with the message Exception: No 3D model available.
- Simplified IFC4 3D models, generated by the Add Document Models (Beta) tool, are positioned at the wrong elevation (Z-axis) when the height value is defined using the IfcMapConversion entity. The horizontal placement is correct, but the vertical placement is shifted downward - often appearing below ground level.
To work around this, use the editing tools in Scene Viewer to manually adjust the model's position along the Z-axis until it aligns with the expected ground level. Save the web scene to store the edits.
- Some simplified IFC4 3D models are positioned at the wrong XY-axis location when the XY coordinates are defined in the IfcMapConversion entity.
To work around this, use the editing tools to manually adjust the model's position along the XY-axis until it aligns with the expected horizontal placement. Save the web scene to store the edits.
- Some IFC models (versions 2.3, 4, and 4.3) fail to ingest in ArcGIS GeoBIM when the output spatial reference is set to WKID 3857 (WGS 1984 Web Mercator Auxiliary Sphere). This occurs when the IFC model does not have internal coordinates defined in the IfcMapConversion entity, but does include a .prj file and a .wld3 file.
To work around this, you will need to use a different spatial reference output.
- IFC models that only contain latitude and longitude coordinates, stored in the IFCSITE entity, will fail during the ArcGIS GeoBIM tool run as the models do not include an IfcMapConversion or IfcProjectedCRS entity to define spatial reference. When this happens, the Job Errors will identify the IFC models impacted and provide the error message Exception: No spatial reference available.
To work around this, embed the geolocation information directly within the IFC model by including the coordinates and specifying the coordinate system in the appropriate IFC entities.
- When processing Revit models that rely solely on an address for geolocation, the 2D bounding box is positioned approximately in the correct location whilst the 3D model output is placed far away from the address. This results in a significant misalignment between the 2D and 3D feature outputs.
To work around this, use one of the recommended georeferencing methods outlined in our Georeferencing workflows topic.
Note:
Avoid relying solely on the address information for georeferencing Revit files, as this is the least accurate method.
- Non-cloud Revit files uploaded to ACC without being detached from the central file will fail to ingest in ArcGIS GeoBIM. When this happens, the Job Errors will identify the Revit models impacted and provide the error message Exception: No 3D model available.
To work around this, open the Revit model in its source authoring tool, detach it from the central file, and then upload the detached version to ACC. To learn more, see How to detach central file from cloud and save as standard Revit file.
- The date format for the French-Canada (Fr-CA) locale is displayed as DD/MM/YYYY, instead of YYYY-MM-DD. There is currently no workaround for this.
Note:
This will be fixed when the ArcGIS Experience Builder version in GeoBIM is updated to v1.20.
- Google Photorealistic 3D basemaps (Beta) are not currently supported.