<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <title-group>
        <article-title>Interoperability between BIM and GIS through open data standards: An overview of current literature</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Eyosias Guyo</string-name>
          <email>eyosias.guyo@trimble.com</email>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Timo Hartmann</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Lucian Ungureanu</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Technische Universität Berlin</institution>
          ,
          <addr-line>Berlin</addr-line>
          ,
          <country country="DE">Germany</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Trimble Solutions Oy</institution>
          ,
          <addr-line>Espoo</addr-line>
          ,
          <country country="FI">Finland</country>
        </aff>
      </contrib-group>
      <fpage>115</fpage>
      <lpage>126</lpage>
      <abstract>
        <p>Building information modeling (BIM) allows representation of detailed information regarding building elements while geographic information system (GIS) allows representation of spatial information about buildings and their surroundings. Overlapping these domains will combine their individual features and provide support to important activities such as building emergency response, construction site safety, construction supply chain management, and sustainable urban design. Interoperability through open data standards is one method of connecting software tools from BIM and GIS domains. However, no single open data standard available today can support all information from the two domains. As a result, many researchers have been working to overlap or connect different open data standards to enhance interoperability. An overview of these studies will help identify the different approaches used and determine the approach with the most potential to enhance interoperability. This paper adopted a strong definition of interoperability using information technology (IT) based standard documents. Based on this definition, previous approaches towards improving interoperability between BIM and GIS applications through open data standards were studied. The result shows previous approaches have implemented data conversion, data integration, and linked data approaches. Between these methods, linked data emerged as having the most potential to connect open data standards and expand interoperability between BIM and GIS applications because it allows information exchange without editing the original data. The paper also identifies the main challenges in implementing linked data technologies for interoperability and provides directions for future research.</p>
      </abstract>
      <kwd-group>
        <kwd>BIM</kwd>
        <kwd>GIS</kwd>
        <kwd>Interoperability</kwd>
        <kwd>Open data standards</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>
        Building information modeling (BIM) and geographic information system (GIS) are
technology-driven domains with important interrelation. BIM allows representation of
data regarding all building elements [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ] and it can support the planning, construction
and operation of buildings. Meanwhile, GIS allows representation of spatial data
regarding a certain environment including buildings [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ]. This puts buildings at an
intersection between BIM and GIS domains. A cooperation between these two domains is
important to manage the built environment since the construction and operation of
buildings affect their environment [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ], and inversely, environmental aspects influence
the planning, construction, and operation of buildings [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]. Benefits of such cooperation
can include improved construction site safety, enhanced construction supply chain
management, improved building emergency management, and sustainable urban
design [
        <xref ref-type="bibr" rid="ref3 ref5 ref6 ref7 ref8 ref9">3, 5-9</xref>
        ].
      </p>
      <p>
        BIM and GIS tools, however, have some significant differences that make
collaboration a challenge. Originally, BIM tools were aimed at supporting the design of new
objects with various levels of detail, while GIS tools were used to represent spatial data
regarding objects that already exist in an environment [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ]. Hence, they evolved
differently [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]. They differ in data structure, in geometry representation, in level of
development, and in the coordinate system they use [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ]. As a result, even though the effort to
integrate the two domains has been increasing in the past years [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ], joining the domains
remains a challenge. The objective of this paper is to investigate previous integration
approaches and determine which of the approaches have the most potential to improve
cooperation between BIM and GIS tools. The paper will also identify challenges and
future research directions.
      </p>
      <p>
        Amirebrahimi et al. [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ] classified BIM and GIS integration levels into application
level, process level, and data level integration. This paper will focus on data level
integration through open data standards. The paper is structured as follows. In Section 2,
we adopt information technology (IT) based definition of interoperability from
international documents. In Section 3 we present some open data standards from BIM and GIS
that can play a key role in interoperability between the two domains. No single open
data standard, however, can fully support information exchange between BIM and GIS.
Therefore, the data standards should be overlapped or connected with one another. And
that will be the focus of Section 4 where previous approaches to connect open data
standards are discussed. The accomplishments and shortcomings of these approaches
will be presented in the same section. In Section 5 and 6 discussions and conclusions
are presented along with challenges and future research directions.
2
      </p>
    </sec>
    <sec id="sec-2">
      <title>Working definition of Interoperability</title>
      <p>
        Interoperability is defined in different ways in different domains [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ]. Therefore, we
decided to adopt a well-established definition for interoperability before discussing the
topic. Interoperability between software tools is an IT based concept. Hence, to
establish a strong definition for the term, we decided to explore IT based definitions. For this
purpose, we considered IEEE Standard Glossary of Software Engineering Terminology
published by Institute of Electrical and Electronics Engineers (IEEE) [
        <xref ref-type="bibr" rid="ref13">13</xref>
        ] and
Information Technology – Vocabulary jointly published by the International Organization
for Standardization (ISO) and the International Electrotechnical Commission
(IEC) [
        <xref ref-type="bibr" rid="ref14">14</xref>
        ]. ISO/IEC defines multiple types or features of interoperability such as
syntactic interoperability, semantic data interoperability, and behavioral
interoperability [
        <xref ref-type="bibr" rid="ref15">15</xref>
        ]. For this paper, we will use the general definition of the term given on
ISO/IEC 2382:2015 to simplify the discussion. We also identified the definition of
‘integration’ and ‘conversion’ as these concepts are sometimes mistakenly used in
interoperability discussions within the literature as being synonymous.
      </p>
      <p>“The ability of two or more The capability to communicate,
systems or components to ex- or exchange data between different
change information and to use functional units in a manner that
the information that has been demands the user to have little or
exchanged”. no knowledge regarding each unit</p>
      <p>“The process of combining “progressive assembling of
syssoftware components, hard- tem components into the whole
ware components, or both system”
into an overall system”.</p>
      <p>“Modification of existing Changing “the representation of
software to enable it to oper- data from one form to another,
ate with similar functional ca- without changing the information
pability in a different environ- conveyed”.</p>
      <p>ment”.</p>
      <p>The IT based definitions presented in Table 1 articulate what interoperability is and
what it is not. Interoperability is not conversion or modification of data representation.
It is also not combining or assembling data models into one. Rather, we define it as the
ability to communicate and exchange information between different software tools and
use the information exchanged. The software tools, in this paper’s context, are
applications from BIM and GIS domains. This definition will be used as a requirement to
evaluate interoperability approaches in this paper.
3</p>
    </sec>
    <sec id="sec-3">
      <title>Interoperability through open data standards</title>
      <p>
        There are different approaches to achieve interoperability between BIM and GIS tools.
These approaches involve either reconfiguring the tools or modifying work processes
or using open data standards [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ]. This paper focuses on interoperability through open
data standards. These open standards allow exchange of information between different
software tools without requiring users to have a vendor specific software package [
        <xref ref-type="bibr" rid="ref16">16</xref>
        ].
      </p>
      <p>The following subsections present some of the open data standards available for BIM
and GIS and their capacity to go beyond their original scope and contribute towards
BIM and GIS interoperability. The open data standards were selected by running a term
co-occurrence analysis using VOSviewer on the 41 literatures referenced in this paper.
The analysis identified CityGML (47 occurrences), IFC (31 occurrences), IndoorGML
(22 occurrences) and LandInfra (8 occurrences) as open data standards with multiple
occurrences.
3.1</p>
      <sec id="sec-3-1">
        <title>CityGML</title>
        <p>
          City Geography Markup Language (CityGML) is an XML-based data model widely
implemented for the representation and exchange of 3D city models [
          <xref ref-type="bibr" rid="ref17">17</xref>
          ]. It is an Open
Geospatial Consortium (OGC) standard that can represent built structures (buildings,
tunnels, bridges, and roads) and environmental aspects (elevation, vegetation, water
bodies and more) [
          <xref ref-type="bibr" rid="ref18">18</xref>
          ].
        </p>
        <p>
          CityGML provides two concepts to support the exchange of features that are not
explicitly represented in the schema [
          <xref ref-type="bibr" rid="ref18">18</xref>
          ]. One is the concept of generic objects and
attributes. This concept allows features that are not explicitly represented in CityGML
to be modelled using generic objects. The second concept is application domain
extension (ADE) which allows addition of new features and information to existing
CityGML classes without altering the semantic structure of CityGML [
          <xref ref-type="bibr" rid="ref18 ref19">18, 19</xref>
          ]. ADEs
have played an important role in some of BIM-GIS collaboration efforts such as de Laat
and van Berlo [
          <xref ref-type="bibr" rid="ref20">20</xref>
          ] and Deng et al. [
          <xref ref-type="bibr" rid="ref21">21</xref>
          ]. However, its use may not be supported by some
software packages [
          <xref ref-type="bibr" rid="ref20 ref21">20, 21</xref>
          ].
        </p>
        <p>
          Another important CityGML feature in BIM-GIS integration discussions is the
concept of level of details (LODs). CityGML supports 5 LODs. At the lowest level there
is LOD0 where buildings are represented by footprint or roof edge polygons. And at
the highest level we have LOD4 where buildings are modeled with detailed elements
including indoor space representations [
          <xref ref-type="bibr" rid="ref18">18</xref>
          ]. This concept supports integration efforts
since features represented in similar LODs can be integrated more smoothly than
features of different LoDs [
          <xref ref-type="bibr" rid="ref22">22</xref>
          ].
3.2
        </p>
      </sec>
      <sec id="sec-3-2">
        <title>Industry Foundation Classes (IFC)</title>
        <p>
          The Industry Foundation Classes (IFC) is an open source file format developed to
enable interoperability between BIM software tools [
          <xref ref-type="bibr" rid="ref16">16</xref>
          ]. It is developed by
buildingSMART International and it is the basis for ISO 16739-1:2018 [
          <xref ref-type="bibr" rid="ref23">23</xref>
          ]. Its data schema
is defined in EXPRESS data specification language (defined in ISO 10303-11) and in
XML Schema definition language (XSD) [
          <xref ref-type="bibr" rid="ref24">24</xref>
          ]. Currently, buildingSMART is working
on IFC extensions to represent infrastructure facilities (such as railways, roads and
bridges) which can enhance IFC’s role in cross-domain collaboration between BIM and
GIS tools [
          <xref ref-type="bibr" rid="ref17">17</xref>
          ].
3.3
        </p>
      </sec>
      <sec id="sec-3-3">
        <title>IndoorGML</title>
        <p>
          IndoorGML is another OGC open data standard and it is an XML-based schema for
indoor spatial information [
          <xref ref-type="bibr" rid="ref25">25</xref>
          ]. Unlike IFC, which focuses on building component
features, IndoorGML mainly focuses on representation of indoor space structures as well
as interoperability between indoor spatial information tools [
          <xref ref-type="bibr" rid="ref26">26</xref>
          ]. It also provides
extensive support for indoor navigation [
          <xref ref-type="bibr" rid="ref27">27</xref>
          ].
        </p>
        <p>
          IndoorGML includes only a minimum set of geometric and semantic components to
avoid overlapping with standards such as IFC and CityGML [
          <xref ref-type="bibr" rid="ref25">25</xref>
          ]. Therefore, it is
beneficial to align it with these other standards [
          <xref ref-type="bibr" rid="ref28">28</xref>
          ]. IndoorGML permits such alignment
by allowing referencing of objects in external datasets such as IFC and CityGML [
          <xref ref-type="bibr" rid="ref25">25</xref>
          ].
Through this referencing feature, IndoorGML has the potential to contribute to
crossdomain collaboration between BIM and GIS tools.
3.4
        </p>
      </sec>
      <sec id="sec-3-4">
        <title>LandInfra</title>
        <p>
          LandInfra is a relatively new OGC standard [
          <xref ref-type="bibr" rid="ref29">29</xref>
          ]. It is a conceptual model for land and
civil engineering infrastructure and it is published for predetermined use cases
(facilities, projects, alignment, road, railway, survey, land features and land division) [
          <xref ref-type="bibr" rid="ref30">30</xref>
          ].
LandInfra has some potential overlap with CityGML. However, unlike CityGML, it
does not have the concept of extension and LODs [
          <xref ref-type="bibr" rid="ref29">29</xref>
          ]. It does, however, support some
features that are not available in CityGML nor IFC. These include: supporting
subsurface data modeling, providing a framework to model legal information of buildings and
storing survey related information [
          <xref ref-type="bibr" rid="ref31">31</xref>
          ].
        </p>
        <p>
          © Ordnance Survey Limited 2021
Fig. 1. Real-world objects represented by IFC, CityGML and LandInfra (Dark shading indicates
strong coverage, light shading weaker coverage (or under development) and no shading implies
no known coverage.) [
          <xref ref-type="bibr" rid="ref32">32</xref>
          ]
In summary, the open data standards presented in this section are developed with a
specific scope in mind. IFC (currently) is for building information modeling, CityGML
is for 3D virtual city modeling, IndoorGML is for indoor space modeling and
navigation, and LandInfra is for land and civil engineering infrastructure. Figure 1 presents
three of these data standards (IFC, CityGML and LandInfra) and various objects from
BIM and GIS they support. As it can be seen in the figure, each standard supports only
a portion of all the objects available. Although some of the standards have features that
allow them to be extended beyond their original scope, no single standard can support
all data exchange requirements between BIM and GIS. While interoperability does not
necessitate complete data exchange, the lack of complete representation by the open
data standard implies there exists data that cannot be exchanged using these data
standards. As a result, researchers have been attempting to overlap or connect these open
data standards with one another to improve data exchange between BIM and GIS.
4
        </p>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>Connecting BIM and GIS data standards</title>
      <p>Previous studies that proposed different methods to connect open data standards from
BIM and GIS are summarized in this section. Their contribution towards improving
interoperability between BIM and GIS domains is discussed based on the definition of
interoperability articulated in Section 2. The methods identified are categorized into
data standard conversion, data standard integration, and linked data approach based
on the process they implemented. It should be noted that some methods involved more
than one of these processes.
4.1</p>
      <sec id="sec-4-1">
        <title>Data standard conversion</title>
        <p>
          Most of the previous BIM-GIS data standard integration methods focused on
conversion of IFC to CityGML [
          <xref ref-type="bibr" rid="ref3">3</xref>
          ]. de Laat and van Berlo [
          <xref ref-type="bibr" rid="ref20">20</xref>
          ] proposed a unidirectional
conversion where geometry of building objects and their properties (semantic information)
stored in IFC format can be transformed to CityGML LOD4. Deng et al. [
          <xref ref-type="bibr" rid="ref21">21</xref>
          ] proposed
a bidirectional exchange of geometrical information between IFC and CityGML as well
as a unidirectional transformation of semantic information from IFC to CityGML. Both
studies created new CityGML extensions (ADEs) to implement the conversion. These
methods will work only if GIS applications are able to work with the new extensions
which may not always be the case as revealed in the studies. A study by Donkers et
al. [
          <xref ref-type="bibr" rid="ref33">33</xref>
          ] presented a unidirectional conversion algorithm to convert geometrical and
semantic information from IFC model to CityGML LOD3 building model which does not
include building interiors like CityGML LOD4. There was also a proposal to extract
indoor building information from IFC into IndoorGML [
          <xref ref-type="bibr" rid="ref34">34</xref>
          ].
        </p>
        <p>
          Some commercial software tools provide data conversion services, mostly from IFC
to CityGML. Feature Manipulation Engine (FME) provides such service and it has been
used by studies such as Yu and Teo [
          <xref ref-type="bibr" rid="ref35">35</xref>
          ] and Jusuf et al. [
          <xref ref-type="bibr" rid="ref9">9</xref>
          ]. Similarly ArcGIS and its
data interoperability extension were used for conversion of BIM data into GIS data by
studies such as Amirebrahimi et al. [
          <xref ref-type="bibr" rid="ref6">6</xref>
          ] and Tashakkori et al. [
          <xref ref-type="bibr" rid="ref7">7</xref>
          ].
        </p>
        <p>
          Overall, the studies in this group proposed to exchange information between BIM
and GIS by converting one data standard into another. The conversions are mostly
unidirectional conversion from BIM to GIS (IFC to CityGML) which neglects the other
half of the information exchange requirement that is from GIS to BIM. Moreover, even
though some information can be transferred through conversion, the process alters and
modifies the original data model. This results in data loss and inconsistencies [
          <xref ref-type="bibr" rid="ref11 ref17">11, 17</xref>
          ].
And the outputs are not always supported by the target software tools. Because of these
drawbacks, the studies in this category fall short of meeting the requirements of
interoperability established in Section 2.
4.2
        </p>
      </sec>
      <sec id="sec-4-2">
        <title>Data standard integration</title>
        <p>
          In this category, there are studies that propose aggregating both BIM and GIS data into
a single unified model or database. A notable example is El-Mekawy et al. [
          <xref ref-type="bibr" rid="ref8">8</xref>
          ] who
presented a unified building model (UBM) where all classes and concepts from IFC
and CityGML would be aggregated. ArcGIS, a GIS software, was chosen to implement
this model. When compared with methods that convert IFC into CityGML, the UBM
method results in less information loss. However, the information exchange remains
one directional, that is from BIM tools to GIS tools.
        </p>
        <p>
          Wyszomirski and Gotlib [
          <xref ref-type="bibr" rid="ref2">2</xref>
          ] proposed to combine data from IFC and CityGML
models and store it in a single database. The aim is to allow BIM and GIS tools to share
information by sending and retrieving data to and from a database. However, BIM
applications that are currently available on the market do not have mechanisms to work
with data stored in a database.
        </p>
        <p>
          The methods grouped in this section were able to reduce data loss by integrating IFC
and CityGML data standards together instead of converting one into the other.
However, whether fully integrating different models is favorable or not is questioned by
some authors as it can create data ownership and intellectual property rights issues [
          <xref ref-type="bibr" rid="ref11 ref36">11,
36</xref>
          ]. Furthermore, the proposed methods favor GIS tools since those tools are the ones
that get access to the integrated data. Therefore, methods in this group do not
sufficiently satisfy the requirements of interoperability defined in Section 2.
4.3
        </p>
      </sec>
      <sec id="sec-4-3">
        <title>Linked data for interoperability</title>
        <p>
          Studies grouped in this category used linked data approaches to link BIM and GIS data
standards. Hor et al. [
          <xref ref-type="bibr" rid="ref37">37</xref>
          ] proposed to link BIM and GIS through semantic web
technologies by developing a semantic graph database framework using IFC and CityGML
source datasets. They provided a web-based application to simulate the integrated
model. However, practical use cases of the integration were not discussed in detail.
        </p>
        <p>
          Vilgertshofer et al. [
          <xref ref-type="bibr" rid="ref17">17</xref>
          ] used a linked data approach to connect a BIM-based tunnel
model with its corresponding GIS model by converting IFC and CityGML into web
ontology language (OWL) representation and establishing a link between them. OWL
is a language in semantic web technologies that is used to represent rich and complex
knowledge [
          <xref ref-type="bibr" rid="ref38">38</xref>
          ]. Using OWL representation to establish the link allowed the authors to
use semantic web querying language SPARQL to query data from IFC and CityGML.
        </p>
        <p>
          Similarly, Karan et al. [
          <xref ref-type="bibr" rid="ref10">10</xref>
          ] proposed to create semantic web representation of BIM
and GIS data , so that it can be processed by semantic web applications. They developed
an ontological representation of IFC and linked that to selected existing GIS ontologies.
The result was an extended ontology with concepts from BIM and GIS that were
relevant to a specific use case (monitoring construction supply chain management). Then,
using SPARQL, information could be retrieved from the combined dataset. The authors
were able to represent the query results in ifcXML building model which can be loaded
into BIM tools. They also used CSV format to represent the query result in GIS tools.
        </p>
        <p>
          The studies categorized in this group developed a semantic web representation of
BIM and GIS data standards and created a link between the web representation (rather
than converting one data standard into another). Hence the original data remained
unchanged. Only selected data was transferred instead of all the data. And the results could
be created in formats that can be used by both BIM and GIS tools. These characteristics
make the linked data approaches exceedingly favorable for interoperability use between
BIM and GIS tools.
Semantic web approaches are gaining popularity in BIM-GIS collaboration
researches [
          <xref ref-type="bibr" rid="ref3">3</xref>
          ]. Availability of BIM and GIS web standards can contribute to such studies.
IFC schema is available in OWL ontology (ifcOWL) which provides the opportunity
to represent building data in Resource Description Framework (RDF) graphs [
          <xref ref-type="bibr" rid="ref1">1</xref>
          ]. RDF
is a framework used to publish and interlink data on the web [
          <xref ref-type="bibr" rid="ref39">39</xref>
          ]. Geospatial data can
also be represented in the semantic web using standards such as GeoSPARQL and
stRDF. GeoSPARQL provides a vocabulary for representation of geospatial data in
RDF and it also defines a SPARQL extension to process geospatial data [
          <xref ref-type="bibr" rid="ref40">40</xref>
          ]. stRDF
extends RDF with the ability to represent spatial and temporal data and it can be queried
using stSPARQL which is an extension of SPARQL [
          <xref ref-type="bibr" rid="ref41">41</xref>
          ].
        </p>
        <p>
          However, semantic web approaches have some critical issues. Ontologies developed
by multidisciplinary professionals (BIM and GIS in the current context) may lead to
inconsistency [
          <xref ref-type="bibr" rid="ref10">10</xref>
          ]. Establishing agreement between the different ontologies is a
challenge [
          <xref ref-type="bibr" rid="ref24">24</xref>
          ]. Additionally, the technologies require some understanding of graph
mathematics, graph databases structure and related tools in addition to understanding BIM
and GIS knowledge data structure and schema characteristics [
          <xref ref-type="bibr" rid="ref37">37</xref>
          ]. And finally, the
methods were implemented on limited use cases. Therefore, further studies that
implement semantic web approaches to other use cases is necessary to better understand and
evaluate these methods.
5
        </p>
      </sec>
    </sec>
    <sec id="sec-5">
      <title>Discussion</title>
      <p>This paper embraces an IT-based definition of interoperability extracted from IEEE and
ISO/IEC standards. We defined interoperability as the ability to communicate and
exchange information between different software tools and be able to use the exchanged
information. Among the different methods that can be implemented to provide
interoperability between BIM and GIS tools, the use of open data standards was the focus of
this paper.</p>
      <p>We presented some of the open data standards available in BIM and GIS (IFC,
CityGML, IndoorGML and LandInfra) in Section 3. The interoperability role these
standards play in their respective domain (For example CityGML in 3D virtual city
modeling) and their capacity to extend beyond their original scope and support
crossdomain collaboration between BIM and GIS tools (for example ADEs in CityGML)
were discussed. However, currently, none of these standards can support all data
exchange requirements between BIM and GIS. Even though interoperability does not
necessitate complete data exchange, the lack of complete representation by the open data
standard indicates that there exists data that cannot be exchanged while using these data
standards. Therefore, to enhance interoperability, the data standards could be
overlapped or connected with one another.</p>
      <p>Several studies have proposed several approaches to connect BIM and GIS data
standards. These proposals were grouped into three in this paper. The first group
proposed to convert one data standard into another. Some information could be transferred
between BIM and GIS tools through these conversion methods. However, the
conversion process alters and modifies data representation resulting in data inconsistency and
data loss. Moreover, most of the conversion methods are unidirectional transformations
(from BIM to GIS) that cover only one side of the information exchange requirement.
And at times, the outputs were not supported by the target applications. Hence, these
approaches fail to correspond with the definition of interoperability established in
Section 2 of this paper.</p>
      <p>The second group of approaches proposed to combine data standards from BIM and
GIS domains (in IFC and CityGML format) and store it in a unified model or database.
These methods allow information from BIM and GIS domains to be aggregated and
stored together. However, it was the GIS tools that had access to the aggregated data.
That means data is transferred from BIM to GIS but not vice versa. Therefore, these
methods fell to meet the requirements of interoperability established in this paper.</p>
      <p>
        The third group of BIM-GIS interoperability studies identified were studies that
created links between different data standards through linked data and semantic web
technologies. This approach allows different models to remain separate and stored in their
original form while selected information is shared between them without loss of
meaning [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ]. The outputs could be given in formats that are supported by both BIM and GIS
tools. These important characteristics of linked data approaches complies with the
definition of interoperability adopted in Section 2 of this paper.
      </p>
      <p>
        Although semantic web technologies are identified as promising methods to link data
models, they still have certain issues. Establishing agreement between different
ontologies from different disciplines is a crucial challenge [
        <xref ref-type="bibr" rid="ref24">24</xref>
        ]. One way to address this
issue could be through formalization of AEC ontologies [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ]. Currently, there are
discussions as to whether to create a central ontology and build everything else around it
or manage data in a completely decentralized manner [
        <xref ref-type="bibr" rid="ref24">24</xref>
        ]. Another challenge is that
these technologies require some understanding of graph mathematics, graph database
structure and related concepts [
        <xref ref-type="bibr" rid="ref37">37</xref>
        ].
6
      </p>
    </sec>
    <sec id="sec-6">
      <title>Conclusion</title>
      <p>The relationship between buildings and their surrounding environment calls for a
collaboration between BIM and GIS domains. BIM supports the design, construction, and
operation of the buildings while GIS supports spatial data regarding the surrounding of
those buildings as well as their inside space. Interoperability between software tools
from the two domains will allow us to combine their functionality and leverage it for
better management of the built environment.</p>
      <p>To discuss interoperability between BIM and GIS tools, it is necessary to have a
well-developed definition of interoperability. Hence, this paper began by adopting a
definition of interoperability from IEEE and ISO/ IEC standards. Then, between the
different approaches towards interoperability, this paper focused on the use of open
data standards. Some open data standards from BIM and GIS were presented and their
potential to support cross-domain interoperability between BIM and GIS was
discussed. However, since none of the open data standards support all necessary data
exchange requirements, they need to be overlapped or connected with one another to
improve interoperability.
There were many approaches in the past to connect open data standards from BIM
and GIS. These approaches were summarized in this paper and were classified into data
standard conversion, data standard integration and linked data approach. Among these,
the use of linked data methods to create a link between BIM and GIS data standards
was identified as a promising approach to enhance interoperability for the fundamental
reason that it allows information exchange without editing the original data. However,
harmonization between knowledge bases created by different domains remains a
challenge to the linked data methods. Furthermore, additional use case-based studies that
implement linked data methods to exchange information between BIM and GIS tools
are necessary to further understand the role linked data methods can play in the
interoperability discussion.</p>
    </sec>
    <sec id="sec-7">
      <title>Acknowledgment</title>
      <p>This project is receiving funding from the European Union’s Horizon 2020 research
and innovation programme under the Marie Skłodowska-Curie grant agreement No
860555.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Pauwels</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          and
          <string-name>
            <surname>Terkaj</surname>
            ,
            <given-names>W.</given-names>
          </string-name>
          ,
          <article-title>EXPRESS to OWL for construction industry: Towards a recommendable and usable ifcOWL ontology</article-title>
          , Autom. Constr., vol.
          <volume>63</volume>
          , pp.
          <fpage>100</fpage>
          -
          <lpage>133</lpage>
          , (
          <year>2016</year>
          ), doi: 10.1016/j.autcon.
          <year>2015</year>
          .
          <volume>12</volume>
          .003.
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Wyszomirski</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          and
          <string-name>
            <surname>Gotlib</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <given-names>A Unified</given-names>
            <surname>Database</surname>
          </string-name>
          <article-title>Solution to Process BIM and GIS Data, Appl</article-title>
          . Sci., vol.
          <volume>10</volume>
          , no.
          <issue>23</issue>
          , (
          <year>2020</year>
          ), doi: 10.3390/app10238518.
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Wang</surname>
            ,
            <given-names>H.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Pan</surname>
            ,
            <given-names>Y.</given-names>
          </string-name>
          , and
          <string-name>
            <surname>Luo</surname>
            ,
            <given-names>X.</given-names>
          </string-name>
          ,
          <article-title>Integration of BIM and GIS in sustainable built environment: A review and bibliometric analysis</article-title>
          ,
          <source>Automation in Construction</source>
          , vol.
          <volume>103</volume>
          .
          <string-name>
            <surname>Elsevier</surname>
            <given-names>B.V.</given-names>
          </string-name>
          , pp.
          <fpage>41</fpage>
          -
          <lpage>52</lpage>
          , (Jul. 01,
          <year>2019</year>
          ), doi: 10.1016/j.autcon.
          <year>2019</year>
          .
          <volume>03</volume>
          .005.
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Zhu</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Wright</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Wang</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          , and
          <string-name>
            <surname>Wang</surname>
            ,
            <given-names>X.</given-names>
          </string-name>
          ,
          <article-title>A Critical Review of the Integration of Geographic Information System and Building Information Modelling at the Data Level, ISPRS Int</article-title>
          .
          <source>J. Geo-Information</source>
          , vol.
          <volume>7</volume>
          , no.
          <volume>2</volume>
          :
          <fpage>66</fpage>
          , (
          <year>2018</year>
          ), doi: 10.3390/ijgi7020066.
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Irizarry</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Karan</surname>
            ,
            <given-names>E. P.</given-names>
          </string-name>
          , and
          <string-name>
            <surname>Jalaei</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Integrating</surname>
            <given-names>BIM</given-names>
          </string-name>
          and
          <article-title>GIS to improve the visual monitoring of construction supply chain management, Autom</article-title>
          . Constr., vol.
          <volume>31</volume>
          , pp.
          <fpage>241</fpage>
          -
          <lpage>254</lpage>
          , (
          <year>2013</year>
          ), doi: 10.1016/j.autcon.
          <year>2012</year>
          .
          <volume>12</volume>
          .005.
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Amirebrahimi</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Rajabifard</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Mendis</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          , and
          <string-name>
            <surname>Ngo</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          ,
          <article-title>A data model for integrating GIS and BIM for assessment and 3D visualisation of flood damage to building</article-title>
          ,
          <source>in CEUR Workshop Proceedings</source>
          , (
          <year>2015</year>
          ), vol.
          <volume>1323</volume>
          , pp.
          <fpage>78</fpage>
          -
          <lpage>89</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <surname>Tashakkori</surname>
            ,
            <given-names>H.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Rajabifard</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          , and
          <string-name>
            <surname>Kalantari</surname>
            ,
            <given-names>M.,</given-names>
          </string-name>
          <article-title>A new 3D indoor/outdoor spatial model for indoor emergency response facilitation, Build</article-title>
          . Environ., vol.
          <volume>89</volume>
          , pp.
          <fpage>170</fpage>
          -
          <lpage>182</lpage>
          , (
          <year>2015</year>
          ), doi: 10.1016/j.buildenv.
          <year>2015</year>
          .
          <volume>02</volume>
          .036.
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <surname>El-Mekawy</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Östman</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          , and
          <string-name>
            <surname>Hijazi</surname>
            ,
            <given-names>I.</given-names>
          </string-name>
          ,
          <article-title>A unified building model for 3D urban GIS, ISPRS Int</article-title>
          .
          <source>J. Geo-Information</source>
          , vol.
          <volume>1</volume>
          , no.
          <issue>2</issue>
          , pp.
          <fpage>120</fpage>
          -
          <lpage>145</lpage>
          , (
          <year>2012</year>
          ), doi: 10.3390/ijgi1020120.
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <surname>Jusuf</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Mousseau</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Godfroid</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          , and
          <string-name>
            <surname>Soh</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <article-title>Path to an Integrated Modelling between IFC and CityGML for Neighborhood Scale Modelling, Urban Sci</article-title>
          ., vol.
          <volume>1</volume>
          , no.
          <volume>3</volume>
          :
          <fpage>25</fpage>
          , (
          <year>2017</year>
          ), doi: 10.3390/urbansci1030025.
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <surname>Karan</surname>
            ,
            <given-names>E. P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Irizarry</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          , and
          <string-name>
            <surname>Haymaker</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <source>BIM and GIS Integration and Interoperability Based on Semantic Web Technology, J. Comput. Civ. Eng.</source>
          , vol.
          <volume>30</volume>
          , no.
          <issue>3</issue>
          , (
          <year>2016</year>
          ), doi: 10.1061/(asce)cp.
          <fpage>1943</fpage>
          -
          <volume>5487</volume>
          .
          <fpage>0000519</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11.
          <string-name>
            <surname>Herle</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Becker</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Wollenberg</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          , and
          <string-name>
            <surname>Blankenbach</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <article-title>GIM and BIM: How to Obtain Interoperability Between Geospatial and Building Information Modelling?</article-title>
          ,
          <string-name>
            <surname>PFG - J. Photogramm</surname>
          </string-name>
          . Remote Sens.
          <source>Geoinf. Sci.</source>
          , vol.
          <volume>88</volume>
          , no.
          <issue>1</issue>
          , pp.
          <fpage>33</fpage>
          -
          <lpage>42</lpage>
          , (
          <year>2020</year>
          ), doi: 10.1007/s41064-020-00090-4.
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          12. International Organization for Standardization,
          <article-title>Advanced automation technologies and their applications - Requirements for establishing manufacturing enterprise process interoperability - Part 1: Framework for enterprise interoperability (ISO 11354-1:</article-title>
          <year>2011</year>
          ).
          <article-title>(</article-title>
          <year>2011</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          13.
          <article-title>The Institute of Electrical and Electronics Engineers (IEEE), IEEE Standard Glossary of Software Engineering Terminology</article-title>
          . (
          <year>1990</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          14.
          <string-name>
            <surname>International</surname>
          </string-name>
          <article-title>Organization for Standardization (ISO)</article-title>
          ,
          <source>ISO/IEC 2382:2015 Information technology - Vocabulary</source>
          , 1st ed. (
          <year>2015</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          15.
          <string-name>
            <surname>International</surname>
          </string-name>
          <article-title>Organization for Standardization (ISO)</article-title>
          ,
          <source>ISO/IEC 19941:2017 Information technology - Cloud computing - Interoperability and portability</source>
          . (
          <year>2017</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          16.
          <string-name>
            <surname>Laakso</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          and
          <string-name>
            <surname>Kiviniemi</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <article-title>The IFC standard - A review of history, development, and standardization</article-title>
          ,
          <source>J. Inf. Technol. Constr.</source>
          , vol.
          <volume>17</volume>
          , pp.
          <fpage>134</fpage>
          -
          <lpage>161</lpage>
          , (
          <year>2012</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          17.
          <string-name>
            <surname>Vilgertshofer</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Amann</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Willenborg</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Borrmann</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          , and
          <string-name>
            <surname>Kolbe</surname>
            ,
            <given-names>T. H.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Linking</surname>
            <given-names>BIM</given-names>
          </string-name>
          and
          <article-title>GIS models in infrastructure by example of IFC and CityGML</article-title>
          , in ASCE International Workshop on Computing in
          <source>Civil Engineering</source>
          <year>2017</year>
          , (
          <year>2017</year>
          ), pp.
          <fpage>133</fpage>
          -
          <lpage>140</lpage>
          , doi: 10.1061/9780784480823.017.
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>
          18. Open Geospatial Consortium,
          <string-name>
            <surname>OpenGIS City Geography Markup Language (CityGML) Encoding</surname>
            <given-names>Standard</given-names>
          </string-name>
          ,
          <source>Version 2.0.0</source>
          . (
          <year>2012</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref19">
        <mixed-citation>
          19.
          <string-name>
            <surname>Biljecki</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kumar</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          , and
          <string-name>
            <surname>Nagel</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>CityGML Application Domain</surname>
          </string-name>
          <article-title>Extension (ADE): overview of developments, Open Geospatial Data, Softw</article-title>
          . Stand., vol.
          <volume>3</volume>
          , no.
          <volume>1</volume>
          :
          <fpage>13</fpage>
          , (
          <year>2018</year>
          ), doi: 10.1186/s40965-018-0055-6.
        </mixed-citation>
      </ref>
      <ref id="ref20">
        <mixed-citation>
          20. de Laat, R. and van
          <string-name>
            <surname>Berlo</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          ,
          <article-title>Integration of BIM and GIS: The Development of the CityGML GeoBIM Extension</article-title>
          , (
          <year>2011</year>
          ), pp.
          <fpage>211</fpage>
          -
          <lpage>225</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref21">
        <mixed-citation>
          21.
          <string-name>
            <surname>Deng</surname>
            , Y., Cheng,
            <given-names>J. C. P.</given-names>
          </string-name>
          , and
          <string-name>
            <surname>Anumba</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <article-title>Mapping between BIM and 3D GIS in different levels of detail using schema mediation and instance comparison, Autom</article-title>
          . Constr., vol.
          <volume>67</volume>
          , pp.
          <fpage>1</fpage>
          -
          <lpage>21</lpage>
          , (
          <year>2016</year>
          ), doi: 10.1016/j.autcon.
          <year>2016</year>
          .
          <volume>03</volume>
          .006.
        </mixed-citation>
      </ref>
      <ref id="ref22">
        <mixed-citation>
          22.
          <string-name>
            <surname>Gröger</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          and
          <string-name>
            <surname>Plümer</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          ,
          <article-title>CityGML - Interoperable semantic 3D city models</article-title>
          ,
          <source>ISPRS Journal of Photogrammetry and Remote Sensing</source>
          , vol.
          <volume>71</volume>
          . pp.
          <fpage>12</fpage>
          -
          <lpage>33</lpage>
          , (Jul.
          <year>2012</year>
          ), doi: 10.1016/j.isprsjprs.
          <year>2012</year>
          .
          <volume>04</volume>
          .004.
        </mixed-citation>
      </ref>
      <ref id="ref23">
        <mixed-citation>
          23.
          <string-name>
            <surname>International</surname>
          </string-name>
          <article-title>Organization for Standardization (ISO)</article-title>
          ,
          <source>ISO 16739-1</source>
          :2018
          <string-name>
            <given-names>Industry</given-names>
            <surname>Foundation</surname>
          </string-name>
          <article-title>Classes (IFC) for data sharing in the construction and facility management industries - Part 1: Data schema</article-title>
          . (
          <year>2018</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref24">
        <mixed-citation>
          24.
          <string-name>
            <surname>Pauwels</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          , Zhang,
          <string-name>
            <given-names>S.</given-names>
            , and
            <surname>Lee</surname>
          </string-name>
          ,
          <string-name>
            <surname>Y.-C.</surname>
          </string-name>
          ,
          <article-title>Semantic web technologies in AEC industry: A literature overview</article-title>
          , Autom. Constr., vol.
          <volume>73</volume>
          , pp.
          <fpage>145</fpage>
          -
          <lpage>165</lpage>
          , (
          <year>2017</year>
          ), doi: 10.1016/j.autcon.
          <year>2016</year>
          .
          <volume>10</volume>
          .003.
        </mixed-citation>
      </ref>
      <ref id="ref25">
        <mixed-citation>
          25. Open Geospatial Consortium,
          <source>OGC ® IndoorGML 1</source>
          .1. (
          <year>2020</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref26">
        <mixed-citation>
          26.
          <string-name>
            <surname>Kim</surname>
            ,
            <given-names>J. S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Yoo</surname>
            ,
            <given-names>S. J.</given-names>
          </string-name>
          , and
          <string-name>
            <surname>Li</surname>
            ,
            <given-names>K. J.</given-names>
          </string-name>
          ,
          <article-title>Integrating IndoorGML and CityGML for indoor space</article-title>
          , vol.
          <volume>8470</volume>
          . Springer Verlag, (
          <year>2014</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref27">
        <mixed-citation>
          27.
          <string-name>
            <surname>Srivastava</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Maheshwari</surname>
            ,
            <given-names>N.</given-names>
          </string-name>
          , and
          <string-name>
            <surname>Rajan</surname>
            ,
            <given-names>K. S.</given-names>
          </string-name>
          ,
          <article-title>Towards generating semantically-rich indoorgml data from architectural plans</article-title>
          ,
          <source>in International Archives of the Photogrammetry, Remote Sensing and Spatial Information Sciences - ISPRS Archives</source>
          , (
          <year>2018</year>
          ), vol.
          <volume>42</volume>
          , no.
          <issue>4</issue>
          , pp.
          <fpage>591</fpage>
          -
          <lpage>595</lpage>
          , doi: 10.5194/isprs-archives-XLII-4
          <string-name>
            <surname>-</surname>
          </string-name>
          591-
          <year>2018</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref28">
        <mixed-citation>
          28.
          <string-name>
            <surname>Kang</surname>
            ,
            <given-names>H. K.</given-names>
          </string-name>
          and
          <string-name>
            <surname>Li</surname>
            ,
            <given-names>K. J.,</given-names>
          </string-name>
          <article-title>A standard indoor spatial data model - OGC IndoorGML and implementation approaches</article-title>
          ,
          <source>ISPRS Int. J. Geo-Information</source>
          , vol.
          <volume>6</volume>
          , no.
          <issue>4</issue>
          , (
          <year>2017</year>
          ), doi: 10.3390/ijgi6040116.
        </mixed-citation>
      </ref>
      <ref id="ref29">
        <mixed-citation>
          29.
          <string-name>
            <surname>Kumar</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Labetski</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ohori</surname>
            ,
            <given-names>K. A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ledoux</surname>
            ,
            <given-names>H.</given-names>
          </string-name>
          , and
          <string-name>
            <surname>Stoter</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <article-title>Harmonising the OGC standards for the built environment: A CityGML extension for Landinfra, ISPRS Int</article-title>
          .
          <source>J. GeoInformation</source>
          , vol.
          <volume>8</volume>
          , no.
          <issue>6</issue>
          , (
          <year>2019</year>
          ), doi: 10.3390/ijgi8060246.
        </mixed-citation>
      </ref>
      <ref id="ref30">
        <mixed-citation>
          30. OGC,
          <article-title>OGC ® Land and Infrastructure Conceptual Model Standard (LandInfra)</article-title>
          .
          <source>Paul Scarponcini</source>
          , (
          <year>2016</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref31">
        <mixed-citation>
          31.
          <string-name>
            <surname>Kumar</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Labetski</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ohori</surname>
            ,
            <given-names>K. A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ledoux</surname>
            ,
            <given-names>H.</given-names>
          </string-name>
          , and
          <string-name>
            <surname>Stoter</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <article-title>The LandInfra standard and its role in solving the BIM-GIS quagmire, Open Geospatial Data, Softw</article-title>
          . Stand., vol.
          <volume>4</volume>
          , no.
          <issue>1</issue>
          , (
          <year>2019</year>
          ), doi: 10.1186/s40965-019-0065-z.
        </mixed-citation>
      </ref>
      <ref id="ref32">
        <mixed-citation>
          32.
          <string-name>
            <surname>Gilbert</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          et al.,
          <article-title>Built environment data standards and their integration: an analysis of IFC, CityGML</article-title>
          and LandInfra, (
          <year>2020</year>
          ). doi: https://www.buildingsmart.
          <article-title>org/buildingsmartinternational-bsi-and-open-geospatial-consortium-ogc-release-bim-and-gis-integrationpaper/.</article-title>
        </mixed-citation>
      </ref>
      <ref id="ref33">
        <mixed-citation>
          33.
          <string-name>
            <surname>Donkers</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ledoux</surname>
            ,
            <given-names>H.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Zhao</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          , and
          <string-name>
            <surname>Stoter</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <article-title>Automatic conversion of IFC datasets to geometrically and semantically correct CityGML LOD3 buildings</article-title>
          ,
          <source>Trans. GIS</source>
          , vol.
          <volume>20</volume>
          , no.
          <issue>4</issue>
          , pp.
          <fpage>547</fpage>
          -
          <lpage>569</lpage>
          , (
          <year>2016</year>
          ), doi: 10.1111/tgis.12162.
        </mixed-citation>
      </ref>
      <ref id="ref34">
        <mixed-citation>
          34.
          <string-name>
            <surname>Teo</surname>
            ,
            <given-names>T. A.</given-names>
          </string-name>
          and
          <string-name>
            <surname>Yu</surname>
            ,
            <given-names>S. C.</given-names>
          </string-name>
          ,
          <article-title>The extraction of indoor building information from bim to OGC indoorgml</article-title>
          , in
          <source>International Archives of the Photogrammetry, Remote Sensing and Spatial Information Sciences - ISPRS Archives</source>
          , (
          <year>2017</year>
          ), vol.
          <volume>42</volume>
          , no.
          <issue>4</issue>
          /
          <issue>W2</issue>
          , pp.
          <fpage>167</fpage>
          -
          <lpage>170</lpage>
          , doi: 10.5194/isprs-archives-XLII-4
          <string-name>
            <surname>-W2-</surname>
          </string-name>
          167-
          <year>2017</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref35">
        <mixed-citation>
          35.
          <string-name>
            <surname>Yu</surname>
          </string-name>
          , S.-C. and
          <string-name>
            <surname>Teo</surname>
          </string-name>
          , T.-A.,
          <article-title>The Generalization of Bim/Ifc Model for Multi-Scale 3D Gis/Citygml Models</article-title>
          ,
          <source>in Proceedings of the 35th Asian Conference on Remote Sensing</source>
          , Nay Pyi Taw, Myanmar, (
          <year>2014</year>
          ), pp.
          <fpage>27</fpage>
          -
          <lpage>31</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref36">
        <mixed-citation>
          36.
          <string-name>
            <surname>Granholm</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          and
          <string-name>
            <surname>Törmä</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <article-title>Using Linked Data to facilitate smooth and effective workflow in a federated model environment</article-title>
          ,
          <source>in Proceedings of the 2019 Workshop on Linked Building Data and Semantic Web Technologies (WLS2019)</source>
          , (
          <year>2019</year>
          ), pp.
          <fpage>45</fpage>
          -
          <lpage>52</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref37">
        <mixed-citation>
          37.
          <string-name>
            <surname>Hor</surname>
            ,
            <given-names>A. E. H.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Sohn</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Claudio</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Jadidi</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          , and
          <string-name>
            <surname>Afnan</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <article-title>A semantic graph database for BIM-GIS integrated information model for an intelligent urban mobility web application</article-title>
          ,
          <source>in ISPRS Annals of the Photogrammetry, Remote Sensing and Spatial Information Sciences,</source>
          (
          <year>2018</year>
          ), vol.
          <volume>4</volume>
          , no.
          <issue>4</issue>
          , pp.
          <fpage>89</fpage>
          -
          <lpage>96</lpage>
          , doi: 10.5194/isprs-annals
          <string-name>
            <surname>-IV-</surname>
          </string-name>
          4
          <string-name>
            <surname>-</surname>
          </string-name>
          89-
          <year>2018</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref38">
        <mixed-citation>
          38.
          <string-name>
            <surname>Hitzler</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Parsia</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          , Patel-schneider,
          <string-name>
            <given-names>P. F.</given-names>
            , and
            <surname>Rudolph</surname>
          </string-name>
          ,
          <string-name>
            <surname>S.</surname>
          </string-name>
          , OWL 2
          <string-name>
            <given-names>Web</given-names>
            <surname>Ontology Language Primer</surname>
          </string-name>
          , W3C Recommendation, (
          <year>2012</year>
          ). https://www.w3.org/TR/owl2-primer/.
        </mixed-citation>
      </ref>
      <ref id="ref39">
        <mixed-citation>
          39.
          <string-name>
            <surname>Schreiber</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          and
          <string-name>
            <surname>Raimond</surname>
            ,
            <given-names>Y.</given-names>
          </string-name>
          ,
          <source>RDF 1.1 Primer, W3C Working Group Note 24 June</source>
          <year>2014</year>
          , (
          <year>2014</year>
          ). https://www.w3.org/TR/rdf11-primer/ (accessed Jul.
          <volume>22</volume>
          ,
          <year>2021</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref40">
        <mixed-citation>
          40. Open Geospatial Consortium,
          <article-title>OGC GeoSPARQL-A geographic query language for RDF data</article-title>
          . (
          <year>2012</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref41">
        <mixed-citation>
          41.
          <string-name>
            <surname>Koubarakis</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          and
          <string-name>
            <surname>Kyzirakos</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <article-title>Modeling and Querying Metadata in the Semantic Sensor Web: The Model stRDF and the Query Language stSPARQL</article-title>
          ,
          <source>in The Semantic Web: Research and Applications</source>
          , (
          <year>2010</year>
          ), pp.
          <fpage>425</fpage>
          -
          <lpage>439</lpage>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>