The georeferencing of BIM has become increasingly important in ensuring spatial accuracy and effective integration with GIS. Georeferencing enables BIM models to be placed within a global coordinate system, facilitating their alignment with other geospatial data for urban planning, infrastructure development, and construction management. This section explores the critical concepts of georeferencing in both GIS and BIM, highlighting the different BIM types and their georeferencing needs. The capabilities of the IFC standard for supporting georeferencing are examined, along with the ongoing collaboration between industry and academia, to address the challenges of integrating BIM with geospatial systems. Furthermore, an overview of software tools for georeferencing BIM models is provided.
4.2. BIM Types and Georeferencing
In the field of surveying and laser scanning, terms such as as-designed, as-built, as-constructed, and as-is are sometimes used interchangeably, which can lead to confusion. However, each term has a specific meaning in the context of BIM and construction, and it is essential to distinguish them clearly. There is a connection between the various types of BIM models and the stage of the defined project. At the first step of the project, before starting the construction, the designer teams of BIM models will design the “as-designed BIM”, which includes initial design and specifications before construction begins. After progress in the project, based on pre-defined timelines, “as-constructed BIM” models will be generated to track the building state during construction, showing deviations from the design concept. The main benefit of this BIM model is resolving the conflicts of design and construction situations during the project. As-built BIM documents the completed state of the building post-construction, including changes made during the process. As-is BIM represents the current state of an existing building, especially when the original design documentation is unavailable [
29].
Figure 6 shows the definition of various types of BIM models and the traditional computer-aided design (CAD) and BIM examples for the provided definitions.
Figure 7 illustrates the connection between the different types of BIM models.
While many BIM models used for internal building management or design purposes may not initially include georeferencing, georeferenced BIM models are increasingly important for applications that involve integration with GIS or urban planning. The growing trend of creating georeferenced BIM models from the start helps bridge the gap between the BIM and GIS domains. Some methods enable the creation of georeferenced BIM models from the very beginning. For example, using advanced surveying techniques such as GNSS or LiDAR during data capture can directly embed spatial coordinates into the BIM model, facilitating seamless integration with GIS data. LiDAR and GPS technologies have been used to create georeferenced BIM models in the following areas: developing green infrastructure BIM models [
30], developing a historical building information modeling (HBIM) system for rehabilitation of the site [
31], automated unmanned aircraft system (UAS) based condition assessment of bridges [
32], and image-based deformation monitoring of bridges [
33]. Utilizing advanced surveying techniques early in modeling, such as LiDAR or GPS, addresses many georeferencing challenges. These methods ensure initial spatial accuracy, effectively bridging BIM and GIS domains. Their application in various sectors, as cited, underscores the value of integrating geospatial data from the onset.
Scan-to-BIM is a process that converts laser-scanned point clouds into BIM, which are then used by development, design, and construction teams. The process starts with a laser scanner, which can be mounted on a drone, a stationary tripod, or carried by a person around the site. The scanner captures points in space corresponding to the site’s geometry, including walls, doors, and other features, by recording their x-, y-, and z-coordinates. The final product is a point cloud enriched with metadata, which teams can use for project planning and revisions [
34]. The BIM reconstruction (as-is/as-built BIM) begins with acquiring a point cloud using laser scanning technology. Next, the following steps have to be conducted to generate the final as-is/as-built BIM, sometimes known as scan-to-BIM [
35]: data acquisition and preprocessing, segmentation and classification, and 3D modelling and BIM integration.
While traditional scan-to-BIM workflows often result in non-georeferenced models, advancements in technology now allow for direct georeferencing during data acquisition. Using mobile mapping systems, UAV-based LiDAR, and topographic scanners equipped with GNSS, point clouds can be accurately georeferenced in real time, minimizing the need for manual alignment in later stages. Sometimes the BIM users will transfer the georeferenced points clouds into the local coordinate systems. As a result, it is essential to preserve the georeferenced point clouds or at least a metadata document, which can be used later to perform georeferencing. Georeferencing point clouds are critical to accurately positioning and contextualizing data within a known coordinate system. Here are the standard methods used for georeferencing point clouds [
36]:
Direct georeferencing in the field: This method georeferences the point cloud at the time of capture using high-precision sensors. Some topographic scanners, mobile LiDAR systems, and unmanned aerial vehicle-based LiDAR (UAV-based LiDAR) equipped with global navigation satellite system (GNSS) and inertial measurement unit (IMU) can record accurate coordinates and orientation data in real time. Because the georeferencing happens during data collection, there is no need for additional alignment steps later. This makes the process faster and ensures spatial accuracy right from the start, which is especially useful for large-scale mapping, infrastructure surveys, and environmental monitoring.
GCPs: If the point cloud is not georeferenced, GCPs with known coordinates, such as physical markers or identifiable features, are added. Survey-grade instruments then measure these GCPs, and the point cloud is aligned and georeferenced based on their coordinates.
Register with existing models or plans: If georeferenced models, plans, or datasets exist for the area, the point cloud can be aligned to them using identifiable features. This alignment can be performed manually or with specialized software, indirectly georeferencing the point cloud based on the known data.
Registration in a previously georeferenced point cloud: If an existing georeferenced point cloud covers the same area, the new point cloud can be registered to it. Common features in both clouds are used for alignment, allowing the new point cloud to inherit the georeferencing from the already referenced cloud.
BIM community published a report about 3D scans to georeferenced BIM models, conducted from an interview with Stephane Hanich, project manager at Bouygues Bâtiment Île-de-France Public Works. Stephane Hanich mentioned that: “Georeferencing has enabled buildings to be precisely positioned within the campus and vis-à-vis other buildings, networks, and property boundaries. This method offers accuracy and reliability that is very difficult to achieve in other ways. The deliverable is easily integrated into our 3D model, can detect clashes earlier, and can make more rigorous studies. It is an undeniable gain of time. Not to mention that the 3D scan can be viewed on the cloud as a 360° photo in which we move. Whether for meetings in the study phase or for exploitation, it is a great communication tool” [
37]. When georeferenced scanning was initially introduced, it was still in its early stages, and only the latest versions of certain software could generate a georeferenced BIM model. However, the technology has since advanced significantly.
While various BIM types such as as-designed, as-constructed, and as-is/as-built models offer valuable insights throughout a project’s lifecycle, their georeferencing is often overlooked. This lack of georeferencing, particularly in scan-to-BIM workflows, creates challenges in integrating BIM models with the geospatial domain. However, advanced techniques like LiDAR, GPS, and GCPs provide solutions to bridge this gap, enabling the creation of georeferenced BIM models. As geospatial technology continues to advance, the potential for seamless BIM and GIS integration becomes more attainable, enhancing project accuracy and cross-domain collaboration.
4.3. Georeferencing Capabilities of the IFC Standard
The IFC is an international standard (ISO 16739-1:2018) and an open, object-based data model developed by buildingSMART [
38]. It promotes interoperability in the AEC industry, particularly within the realm of BIM. IFC’s primary function is to enable the exchange of construction models, primarily encompassing 3D representations of buildings. The International Alliance for Interoperability initially developed this widely recognized open standard for BIM, and it has since been taken over and maintained by buildingSMART to facilitate enhanced information interoperability among stakeholders [
39].
As research on BIM/GIS integration has grown, georeferencing BIM data have gained significance in achieving seamless integration between BIM and GIS. Consequently, newer versions of IFC have incorporated certain georeferencing concepts. To delve into the process of georeferencing within the IFC data format, it is essential to understand the concepts of coordinate systems and georeferencing levels in the IFC first. In the following, we comprehensively explain various relevant classes connected to georeferencing, elucidating their relationship to corresponding concepts in the GIS domain.
The IFC utilizes a system of relative placement known as the placement hierarchy. This hierarchy positions an object (child) with a higher class (parent). The placement hierarchy encompasses elements, stories, buildings, sites, and projects [
4]. The
project entity can include several connected or disconnected
Sites. The most superficial level of georeferencing information can be stored in the
IfcPostalAddress entity, which has the following attributes to represent the address of the project site:
InternalLocation,
AddressLine,
PostalBox,
Town,
Region,
PostalCode, and
Country.
IfcPostalAddress can be referenced by
IfcSite and
IfcBuilding, which have the attributes of
SiteAddress and
BuidlingAddress, respectively, with the type of
IfcPostalAddress. Every
Site can store a single geographic reference point in the form of
Latitude,
Longitude, and
Elevation of the World Geodetic System (WGS84) or European Petroleum Survey Group:4326 (EPSG:4326) for absolute placement in exchange with GIS world.
The Site’s attributes are RefLatitude,
RefLongitude,
RefElevation,
LandTitleNumber, and
SiteAddress.
RefElevation is relative to sea level, and it is impossible to define its datum. As outlined in the IFC standard, the geographical reference provided could pertain to either the precise location of the origin of the local placement of the
IfcSite or serve as an approximate position intended solely for informational use [
19].
One step further, the
IfcSpatialStructureElement entity is a general concept of all spatial elements (such as site, building, building story, and space), and
IfcLocalPlacement can define their relative placement. For the site, the
IfcLocalPlacement can be absolute (i.e., world coordinate system (WCS)), defined by the
IfcGeometricRepresentationContext entity. This entity has the following attributes:
WorldCoordinateSystem and
TrueNorth. The first attribute can be used to offset the project coordinate system from the global point of origin, and the latter attribute defaults to the positive direction of the Y-axis of the
WorldCoordinateSystem. Considering
IfcSite and
IfcGeometricRepresentationContext, it is possible to georeference IFC models, but these values are often set to zero, the wrong location, or rough approximations. This issue is further complicated by the inconsistent definitions of the positive direction for longitude in IFC2x3 and IFC4 [
19].
The most complete entity containing georeferencing information is
IfcMapConversion, which has been added to IFC version 4. It can be used to transform from an engineering coordinate system (ECS) into a coordinate reference system (CRS); however, it cannot deal with the projection of a map from the geodetic coordinate system.
Eastings (E),
Northings (N),
OrthonogalHeight (O),
XAxisAbscissa (XAA),
XAxisOrdinate (XAO), and
Scale (S) are the attributes of
IfcMapConversion. Salheb et al. (2020) developed a methodology to convert City Geography Markup Language (CityGML) to the IFC data format, which is needed to transfer the georeferenced data from global coordinates to local coordinates [
40]. They mentioned that the lack of supporting various coordinate systems can be a problem that has been addressed in the latest version of IFC. Georeferencing has two main steps: (1) establishing spatial reference and (2) obtaining coordinate transformation parameters and transforming coordinates. Based on the mentioned attributes, the coordinate transformation can be calculated using the affine transformation [
4,
11].
There are some studies investigating the capabilities of georeferencing in the IFC data format, which has some problems, including misinterpretation of the IFC geometry structure, the misunderstanding of IFC entities, and the misuse of IFC entities [
10,
13,
19]. They considered the
IfcSite as the highest geometry container of the IFC, whereas the
IfcProject is the highest container [
4]. The main issue of this consideration is that the geographic reference point of
IfcSite was mistakenly interpreted as the origin of the engineering system (project-level local coordinate system (LCS)), which leads to neglecting the relative placement of
IfcSite and
IfcProject.
Figure 8 shows the georeferencing entities and their relation.
In 2019, Ref. [
10] proposed six levels for storing georeferencing attributes, from level of georeferencing (LoGeoRef) 10 to LoGeoRef 60, based on the entities described above, which has been illustrated in detail in
Figure 9. The higher levels are more complex and contain more information. However, higher levels do not include lower-level data. These levels have been defined without focusing on infrastructure [
28]. Nonetheless, it is essential to clarify that these levels do not indicate the precision or quality of georeferencing but primarily pertain to how georeferencing data are structured and stored. In certain instances, like that of LoGeoRef30 and LoGeRef40, their accuracy can be identical as they are intended to represent the same values despite variations in their storage methods within the IFC file [
15]. As described in the IFC specification, all objects with a spatial context are derived from the class
IfcProduct, which has two attributes:
ObjectPlacement and
Representation. A placement can be absolute, relative, or in a defined grid [
15]. The absolute placement is with respect to the WCS of the project, which
IfcGeometricRepresentationContext defines. The objects in IFC can be placed relative to their superior objects. They supposed that the most superior object in IFC is
IfcSite, which can be placed with respect to the project WCS. However, it cannot directly refer to the geodetic CRS; the
IfcCoordinateOperation element can assign
IfcSite to the geodetic CRS [
41].
In a study by [
4], the georeferencing capabilities of the IFC data format were investigated, and the authors concluded that in defining these levels of georeferencing, the IFC entities have been misused because
IfcSite is not the highest object container. This involved two specific instances of misuse: (a) utilizing the relative placement attribute (represented by an
IfcAxis2Placement3D object) of
IfcSite to store its position relative to a CRS instead of the project-level LCS as specified in LoGeoRef30, and (b) employing the
WorldCoordinateSystem attribute (indicated by an
IfcAxis2Placement3D object) to record the relative placement with respect to a CRS by LoGeoRef40. The consequence of this misapplication of these IFC elements is the generation of extensive coordinate values, which can potentially lead to unforeseen issues when used with BIM tools, as highlighted in the reference. BIM models containing such misapplied elements become incompatible with BIM tools, rendering them unusable for their intended purposes.
Figure 10 illustrates the mapping between these proposed levels for storing georeferencing in the IFC data format.
Ref. [
15] investigated 57 IFC models derived from real-world practices to scrutinize the storage of georeferencing information within these models. This examination was prompted by the observed misalignment between the standards outlined in the IFC model specifications and the actual georeferencing data encountered in practice, resulting in several noteworthy issues. The analysis encompassed two critical aspects: the location where georeferencing information was stored and the quality of the stored data. The former aspect was assessed based on [
10] georeferencing levels, with the observation that this information could be stored multiple times and that there was a corresponding absence of a validation system for ensuring conformance to defined levels. A significant issue was identified in the lack of support for coordinate reference systems within the IFC2x3 version. Concerning the latter aspect, the storage quality was examined regarding North, East, and elevation data, with particular attention being paid to the direction of rotation, all of which were assessed and reported independently.
Table 5 reports the detailed results of the inspection with respect to georeferencing information.
Ref. [
43] transformed the 3D geometric information of CAD objects expressed by the IFC model into the Geography Markup Language (GML) model. The main focus of this study was on transformation from the swept solid models to the Boundary-representation (B-Rep) models, which included transferring coordinates from the local system to the real-world system. Their proposed method extracted the coordinates of vertices of the objects in the local coordinate system and transferred them to a real-world coordinate system by using affine transformation to generate the GML object model. They did not mention how they accessed the target coordinates in the real-world system. Ref. [
44] used an instance-based method to generate the mapping rules between IFC and CityGML. One of the major transformations of data from IFC to CityGML was the transformation of the local placement system in IFC to the world coordinate system in CityGML, in which they utilized the method proposed by [
43] to overcome it.
Ref. [
45] proposed a transformation path for converting IFC data models into CityGML using the Feature Manipulation Engine (FME) software (Version 2016.1) to support urban energy modeling on web visualization applications. One of the major steps in this study was handling the georeferencing of the IFC model during the transformation. The first step was defining a projected coordinate system for the IFC model to bring it from a 3D Cartesian coordinate system (CCS) into a 3D GCS-based model in CityGML. FME provides the
CRS_Transformer,
LocalCoordinateSystemSetter,
Scaler,
3DRotator, and
Offsetter transformation to support this translation. However, the important point to consider is the fact that in FME, the IFC files are read with a bounding box determined by the extent of the model, which is always perpendicular to the x- and y-axis of the drawing canvas. As a result, the rotation has to occur before the translation transformation in FME. After that, the model shifted to the correct location.
Ref. [
46] investigated the possibility of using IFC models in the geospatial environment to support the fire response management process and indicated the importance of geolocating the IFC models in the geospatial environment correctly. They suggested using the information obtained from the IFC attributes such as
IfcSite and
IfcGeometricRepresntationContext or utilizing a geospatial object as a template to extract some ground control points. Ref. [
26] proposed an economical approach to georeferencing the IFC model of a bridge using affine transformation. The process involved several steps: initially, selecting specific control points to establish connections between the IFC model and its corresponding representation in the GIS realm. Subsequently, the transformation parameters were computed, enabling the rectification of the model through affine transformation. Lastly, the z-values of individual vertices were adjusted utilizing a scaling factor. The critical point to achieve good accuracy depends on the number and location of the control points. Manual intervention and testing only on a simple bridge model are the limitations of this approach that need to be addressed in future works.
Implementing georeferencing at the application level (software) and the exchange level (suitable exchange formats) can lead to achieving interoperability of BIM and GIS. Refs. [
47,
48] focused on the exchange level, specifically the IFC data format version 4. They presented the current georeferencing capabilities of IFC4 and proposed extensions to address its limitations, including two new entities supporting geographic coordinate reference systems (GCRSs) and rigid transformation of BIM geometries. The current capabilities have been described in this section. The most important requirement of the BIM models is the possibility of using the IFC models without any manual intervention. As a result, they focused only on LoGeoRef50, the only level providing information about the CRS. They developed three solutions to provide complete georeferencing information in the IFC data format as follows:
CRS.
No breaking changes: The goal is to achieve the possibility of introducing a geographic CRS, which needs to modify the definition of IfcCoordinateReferenceSystme. GeodeticDatum and VerticalDatum have been moved to IfcProjectedCRS as they are unnecessary in a generic CRS. The new optional attribute WellKnownText has been added to IfcProjectedCRS. Also, a new entity, IfcGeographicCRS, can model the geographic CRS by having the following attributes: GeodeticDatum, PrimeMeridian, and Unit.
Breaking changes: The WellKnownText (WKT) attribute can be introduced to the abstract IfcCoordinateReferenceSystem entity, and the definition of IfcGeographicCRS remains the same.
Coordinate operations: With the introduction of new children to the abstract IfcCoordinateReferenceSystme, the usage of IfcMapConversion shall be restricted in the schema only to allow IfcProjectedCRS entities being referenced by the attribute TargetCRS. Thus, the SourceCRS referring to an IfcRepresentationContext uses projected coordinates with elevation.
In the beginning, BIM/GIS integration focused on integrating building models with GIS to support the design and development of smart cities. With significant progress in this field, the users are considering integrating infrastructure BIM data with GIS. Infrastructure BIM data are related to large-scale projects, such as roads, railroads, bridges, etc., which may involve several countries. The most important factors that should be considered in the georeferencing process in this type of project are the curvature of the Earth, aspects of the geodetic CRS, and the distortion implied by them. The curvature of the Earth, irregularities in gravity, and map projection play an essential role in defining the geometric context of the BIM models and calculating coordinates for surveyors of infrastructure projects [
47,
49]. Although the IFC can embed georeferencing information to model infrastructure projects, multiple sites should be used to control the effect of the curvature of the Earth, while the current IFC models can only support one instance of
IfcMapConversion [
7].
Infrastructure BIM data are commonly designed in a LCCS, assuming the Earth is flat. As a result, designers consider the constant scale of their projects. On the other hand, the georeferenced digital terrain models (DTMs) to a map projection will be used as a basis data for infrastructure design. The DTM is not a 1:1 representation due to scale variation, which causes a discrepancy between the designed infrastructure BIM and DTM [
14]. To address this, IFC 4 has been extended with IFC alignment to support alignment geometries such as roads and railroads, which are used for infrastructure design. Ref. [
14] investigated the geographic capabilities of IFC alignment extension. The IFC alignment project team proposed two steps to georeferencing infrastructure BIM models: rotating the engineering system to align the y-axis with cartographic north and translating the origin of the engineering system using the known Easting, Northing, and Height. As the IFC standard supports map projections identifiable by an EPSG code, the scale distortion depends on the geographic location of the project and the well-known map projections available for the area. Countries such as the United Kingdom, which use a single transverse Mercator projection zone, will be more affected by this problem [
14].
IFC version 4 supports the geodetic CRS (gCRS) by referring to an identifier of the EPSG database. However, referring to custom gCRSs is impossible, which can be problematic for large infrastructure projects. Jaud et al. (2019) proposed a novel approach to expand the IFC schema with the WKT notation to handle the custom gCRS in the Brenner Base Tunnel (BBT) project [
50]. Possibilities of parametric descriptions of any gCRS and acceptance by GIS made WKT the best option to store the custom gCRS information in the new entity
IfcWellKnownTextCRS. In addition, Ref. [
49] proposed an additional class deriving from
IfcCoordinateOperation with the name of
IfcBilinearConversion containing an array of tuples to link between the coordinates in the geodetic CRS defined with
IfcProjectedCRS and the corresponding coordinates used in the BIM model. The important note is to define a new class
IfcGeodeticPoint to separate it from the Cartesian point defined in the schema as
IfcCartesianPoint.
4.4. Collaboration of Industry and Academia
The Open Geospatial Consortium (OGC) and buildingSMART International published a paper as an output of their integrated digital built environment joint working group [
51]. This report focuses on a variety of challenges and addresses the need to develop better integration at a high level between BIM and GIS standards, IFC, CityGML, and LandInfra. The differences between their CRSs are considered one of the main challenges. CityGML’s use of gCRSs provides benefits such as easier indexing in GIS software, quicker spatial queries, and smoother integration of different datasets. However, a drawback is that changing an object’s global position requires updating every geometric feature. On the other hand, the IFC format use local cartesian CRSs, which must be transformed into a geodetic CRS for integration with other geolocated data, like CityGML models. IFC models often lack precise geolocation, making automated spatial integration challenging. Additionally, differences in how network topologies are represented and inconsistencies in object identification between standards highlight the importance of accurate real-world positioning to infer relationships, identify duplicates, and resolve conflicts between objects [
52].
BuildingSMART published several technical reports about user guides for georeferencing in IFC in January 2020 [
53]. Initial discussions with the industry identified the lack of knowledge with regard to georeferencing and the strong interest in this subject in the user base in Australia. Their objective was to work with a large site, but they also needed to be able to bring data in from smaller sites. The concept that defines the cadastre or terrain locates built assets and geographic features, etc., and it is represented in IFC2x3 and IFC4 by the
IfcSite entity. This is important because some users and members were not clear about whether the data were associated with the
IfcProject or
IfcSite. Their suggestion was that for every small site within a large project, a land surveyor should be used to establish the two sets of coordinates, which should not be too close together, and the 2D Helmert transformation parameters that will be captured in the map conversion settings should be calculated and its parameters stored in the entity
IfcMapConversion in IFC4 or in special property sets in IFC2x3. A strong recommendation was to allow for the storing of the 2D Helmert paired coordinate points, which would allow surveyors to carry out transformations to assess the accuracy of the process.
Table 6 shows the 2D Helmert transformation and CRS attributes, which will be stored in
IfcMapConversion and
IfcProjectedCRS, respectively [
54].
A detailed demonstration scenario has been generated by buildingSMART to show how to set up georeferencing in a building or linear infrastructure model.
Figure 11 illustrates the process with an explanation.
Dion Moult (architect/software developer) and John Mitchell (co-founder of buildingSMART Australia) proposed three scenarios to address the geolocation in IFC2x3 and IFC4. The main issue in IFC2x3 is the fact that there is no geolocation entity like
ProjectedCRS and
IfcMapConversion in IFC4. As a result, they proposed defining two new sets (the
IfcPropertySet is a container that holds properties within a property tree) called
EPset_ProjectedCRS and
EPset_MapConversion to store the same attributes. These two sets must be associated with the relevant top-level
IfcSite entity. The next issue was the confusion over optional fields in the
IfcProjectedCRS. They proposed EPSG:### number in the
IfcProjectedCRS. The name field must match a code in the Official EPSG Registry, specifically aligning with the XPath ProjectedCRS/identifier in the GML export. This would allow for retrieval of the corresponding WKT. Additionally, Moult and Mitchell suggest modifying the documentation for optional fields as follows [
56]:
MapProjection: Required if the Name identifier does not clearly define the map projection and the CRS is 3D.
MapZone: Required if the Name identifier does not clearly define the map zone and the CRS is 3D.
MapUnit: Required if the Name identifier does not clearly define the map unit and the CRS is 3D.
To resolve ambiguity with fields like
VerticalDatum and
GeodeticDatum, Moult proposed that their values should match the XPath of VerticalDatum/identifier and GeodeticDatum/identifier, respectively. This approach ensures a single, unambiguous value and aligns with the XPath convention used for ProjectedCRS/identifier. Using identifiers enhances data integrity by avoiding the issues associated with aliases [
56].
Dion Moult (21 May 2019) explained the IFC CRS similar to the level of georeferencing that [
10] proposed. Moult tried to investigate the mentioned coordinate systems in Revit software and figured out how they work. Revit provides an
IfcProject that includes an
IfcGeometricRepresentationContext, but it lacks an
IfcMapConversion, which is crucial for recording CRS, data, projections, and related information. The
IfcProject’s WorldCoordinateSystem is fixed at (0, 0, 0) and does not change regardless of Revit’s origin placements. The
RefLatitude and
RefLongitude are derived from the Revit project’s “Location” settings and are unrelated to the Survey Point or Project Base Point. Additionally, Revit does not distinguish between buildings, sites, or sub-sites, meaning all contents are placed within a single site and building. This limitation is important because, without a CRS conversion, users often input local CRS coordinates into the Project Base Point and Survey Point. Given that these values are typically large, the
IfcSite’s local placement can end up significantly offset in space [
57].
The collaboration between industry leaders like buildingSMART and OGC, along with academic contributions, has led to significant advancements in addressing georeferencing challenges within BIM and GIS integration. Through technical reports, standards development, and practical demonstrations, these efforts aim to streamline the use of geospatial data in BIM models and overcome the limitations of current technologies and standards, such as IFC. Continued collaboration will be crucial in developing more robust solutions for georeferencing, enhancing the accuracy of digital models, and fostering greater interoperability between BIM and GIS domains.