WO2016081628A1

WO2016081628A1 - System and method for aggregating and analyzing data and creating a spatial and/or non-spatial graphical display based on the aggregated data

Info

Publication number: WO2016081628A1
Application number: PCT/US2015/061386
Authority: WO
Inventors: Michael Carl JANSEN; Robert Samuel LEGA; Remi Simon Vincent ARNAUD
Original assignee: Cityzenith, Llc
Priority date: 2014-11-18
Filing date: 2015-11-18
Publication date: 2016-05-26

Abstract

A system for aggregating, analyzing and graphically displaying data collected from one or more data sources includes one or more data sources, a database for receiving data from the one or more data sources, and having a converting unit configured to convert all received data into a uniform encoding language. The data includes data associated with a 3D model of a real asset and additional data related to the real asset. The system also includes a visualization engine configured to receive the converted data, generate a graphical 3D representation of the real asset and the additional information, and output the generated graphical 3D representation to a display. The data associated with the 3D model and the additional data are received from the database. A client device is connected to the display and configured to display the graphical 3D representation generated at the visualization engine. The client device also displays a graphical user interface together with the graphical 3D representation. A server is communicably connected between the database and a client.

Description

TITLE

SYSTEM AND METHOD FOR AGGREGATING AND ANALYZING DATA AND CREATING A SPATIAL AND/OR NON-SPATIAL GRAPHICAL DISPLAY BASED ON

THE AGGREGATED DATA

BACKGROUND

[0001] The following description relates to methods and systems for aggregating, analyzing and/or graphically displaying data collected from one or more data sources to create a geospatial data environment, and in some embodiments, a communication system for performing the same.

[0002] Population centers produce vast amounts of data. The data may relate to, for example, supply and demand of utilities including water, electric and gas. Other data may relate to waste, vehicle and pedestrian traffic and public transit. Additional data may be created, for example, with the deployment of municipal resources, including, waste collection, utility repair and maintenance, transportation infrastructure repair and maintenance and other municipal services. Similar data may be generated by private entities as well. Further still, data may be produced and collected at individual public and/or privately owned real assets, such as municipal, commercial, industrial and residential buildings. Even further, data may be collected that relates to atmospheric conditions, such as temperature, wind, sunlight and the like.

[0003] However, much of the generated data is unstructured and goes un-used or under-used. As a result, the potential for efficiency gains may go un-utilized or under-utilized. For example, resources may be inefficiently allocated to certain projects, while other resources may be under-allocated to other projects. In another example, utility usage may not be optimized, which may result in, for example, excess waste including release of greenhouse gases into the atmosphere.

[0004] Current systems may be geared toward data collection from a single source, or one or more closely related sources. However, the current systems are not designed to collect data from numerous, disparate sources in different data formats, and convert the data to a common format. Thus, not all received data may be easily read or utilized by the systems. In addition, in different systems, the data may be used on a limited basis to relay information to users. However, the current systems do not pull data from a multitude of sources and combine that data with real assets to be graphically displayed at a client device. [0005] Accordingly, it is desirable to provide a system for collecting data from one or more input sources, storing the data, organizing the data and outputting and displaying the data in a graphic format to interested parties. In a population center, the data may be analyzed and used to create a 3-dimensional (3D) visual representation of, for example, physical buildings, and above and below ground infrastructure. In addition, it is desirable to provide a system that provides asset and coordination tools to support planning workflow collaboration between departments for scheduling and permitting. Further, it is desirable to provide a system that allows for viewing of external data including reference materials, documents and images for selected targets.

SUMMARY

[0006] According to one embodiment there is provided a system for aggregating, analyzing and graphically displaying data collected from one or more data sources. The system includes one or more data sources, a database configured to receive data from the one or more data sources, the database comprising a converting unit configured to convert all received data into a uniform encoding language, the data including data associated with a 3D model of a real asset and additional data related to the real asset, a 3D visualization engine configured to receive the data associated with a 3D model of a real asset and the additional data related to the real asset with respect to time, generate a graphical 3D representation of the real asset and the additional information, and output the generated graphical 3D representation to a display. The data associated with the 3D model and the additional data are received from the database. The system further includes a client device connected to the display and configured to display the graphical 3D representation generated at the visualization engine, the client device further configured to display a graphical user interface together with the graphical 3D representation, and a server communicably connected between the database and a client.

[0007] According to another embodiment there is provided a method of generating and displaying a geospatial data environment. The method includes receiving, at a database, data from one or more sources, the data including data associated with a 3D model of a real asset and additional data related to the real asset, converting the received data to a uniform encoding language and storing the converted data at the database, receiving a request to generate a graphical 3D representation, transmitting the converted data to a 3D visualization engine, generating a graphical 3D representation based on the data associated with a 3D model of the a real asset and the additional data, outputting the graphical 3D representation to a display, and displaying the graphical 3D representation of a real asset and additional data associated with the real asset.

[0008] According to another embodiment, there is provided an electronic client device. The device includes a display, an input/output module, a communication module, a memory module, and one or more microprocessors. The memory module stores a program instruction configured to be executed by the one or more microprocessors for displaying a first graphical 3D representation of a first real asset generated based on data associated with a 3D model of the first real asset and first additional data related to the first real asset. The data associated with a 3D model of the first real asset is displayed as a rendering of the first real asset in the graphical 3D representation, and the first additional data is displayed as a color or text on at least a portion of the rendering of the first real asset in the graphical 3D representation.

Different colors or text are displayed to represent different values of the first additional data. The first additional data includes a geospatial position tag combined with a data value, wherein the geospatial position tag corresponds to a geospatial position on the first real asset where the data value was measured. The graphical 3D representation displays the first additional data at a position on the rendering of the first real asset based on the geospatial position tag.

[0009] Other objects, features, and advantages of the disclosure will be apparent from the following description, taken in conjunction with the accompanying sheets of drawings, wherein like numerals refer to like parts, elements, components, steps, and processes.

BRIEF DESCRIPTION OF THE DRAWINGS

[0010] FIG. 1 is a diagram of a system according to an embodiment described herein;

[0011] FIG. 2 is another diagram of a system according to an embodiment described herein;

[0012] FIG. 3 is a diagram showing a client device according to an embodiment described herein;

[0013] FIG. 4 is a diagram showing a database according to an embodiment described herein; [0014] FIGS. 5-9 are diagrams showing examples of architectures for use in the system described herein;

[0015] FIGS. 10-13 are tables showing examples of situations of where and how the system of FIG. 1 may be employed, subsystem integration, functionality, and data types utilized;

[0016] FIGS. 14-28 depict various views of the user interface (UI) according to an embodiment described herein; and

[0015] FIG. 29 is a diagram showing a method of generating and displaying a geospatial data environment according to an embodiment described herein.

DETAILED DESCRIPTION

[0017] While the present disclosure is susceptible of embodiment in various forms, there is shown in the drawings and will hereinafter be described one or more

embodiments with the understanding that the present disclosure is to be considered illustrative only and is not intended to limit the disclosure to any specific embodiment described or illustrated.

[0018] FIGS. 1 and 2 are diagrams showing a system 10 for aggregating, analyzing and graphically outputting and displaying geospatial and non-spatial images representing real assets together with additional data with relation to time based on the aggregated data. Referring to FIGS. 1 and 2, the system 10 generally includes one or more first database 12, one or more second database 14, a visualization engine, such as a 3D visualization engine 16, one or more server 18 and one or more client device 20. The one or more client device 20 described herein may be an electronic device typically having a display or an interface for connecting to a display, wired or wirelessly. In one embodiment, the client device 20 may be a portable electronic device, including but not limited to, a mobile communication device such as mobile telephone or smartphone, a PDA, and/or a tablet computer. The portable electronic device may include a touch sensitive screen or control surface to be manipulated by a user to control operation of the device. Other electronic devices may be personal or desktop computers, laptop computers or other portable computers, such as vehicle mounted or installed computers. Other suitable electronic devices include set top boxes and the like that may be connected to a display, such as a monitor or television. The electronic devices described herein may include an internal power supply, such as a battery, including, rechargeable and/or replaceable batteries, and/or an interface for connecting to an external power supply, such as an auxiliary battery or a known electrical wall socket.

[0019] In addition to the applications described herein, the electronic device may support a plurality of other applications, including, for example, a camera application, a phone application, a video application, a Short Message Service (SMS) application, a web browsing application and/or an email application.

[0020] The client device 20 is configured to communicate with other client devices and components of the system 10 described herein, or other, external, components or systems. The client device 20 is connected to and communicates over a communication network. For example, the client device 20 may communicate by sending and receiving radio frequency (RF) signals. The client device 20 may transmit or receive RF signals via an antenna, a transceiver, a SIM card and the like. The client device 20 is also configured to communicate over a cellular telephone network, Local Area Network (LAN) including a Wireless Local Area Network (WLAN) and other wired and/or wireless communication networks. Wireless communications may use suitable technologies or protocols such as GSM, CDMA, Bluetooth, Near Field Communications, Wi-Fi (including IEEE 802.xx standards), VoIP and other similar protocols or standards facilitating wireless communication. The client device 20 may be connected to other devices or components of the system 10 or other systems either wirelessly, as described above, or through wired systems including, cable, fiber optic and/or standard telephone lines or known connection cables with, for example, pin or USB interfaces.

[0021] FIG. 3 is a diagram showing the client device 20 in further detail, according to an embodiment described herein. Referring to FIG. 3, the client device 20 includes a memory module 202, and input/output (I/O) module 204, a communication module 206, a controller 208 and a display 210. The memory module 202 is computer-readable storage media. Computer-readable storage media include non-transitory media, for example, magnetic media, including hard disks and floppy disks; optical media including CD ROM disks and DVDs, and/or optical disks. Computer-readable storage media may also include hardware devices configured to store and/or perform program instructions, including read-only memory (ROM), random access memory (RAM), flash memory and the like. Further, computer-readable media may include Solid State Drives (SSDs) and remote or distributed memory devices or services. It is understood that non-transitory media does not include signals or waves.

[0022] The I/O module 204 is configured to connect to peripheral devices, for example, an external memory 212, an external display 214, or an external input device 216, such as a keyboard or pointer, for example. The communication module 206 may be an RF module 206 and include components as described above to enable RF communication of the client device 20. The controller 208 is implemented as a central processing unit (CPU) having one or more microprocessor configured execute program instructions and steps stored in the memory module 202. The controller 208 is communicably connected to various components of the client device 20 and is configured to control operation of the components. The client device 20 may have the display 210 integrally connected or formed therewith, the external display 214 connected thereto through the I/O module 204, or both.

[0023] Referring to FIG. 2, the system 10 may optionally include one or more sensors 22 configured to measure data and/or detect a change in data. The one more sensors 22 may include, for example, a strain gauge, a flow meter, a photo sensor, a position sensor, a motion sensor, a speedometer, a load cell, a temperature sensor, a current sensor, a voltmeter, an air quality sensor and a wind gauge, for example. Other sensors are envisioned as well. The sensors 22 may measure the data with respect to time at predetermined intervals or upon detecting a change in the data. The one or more sensors 22 are configured to measure a data value and transmit the data value to the database 12. In one embodiment, the sensors 22 may also detect and transmit a geospatial position tag together with the data value indicating a geospatial position where the data value was measured. In other embodiments, the geospatial position of the one or more sensors 22 is known, and the geospatial position tag may be later associated or linked to the measured data value. For example, a sensor 22 may detect a flow rate of a fluid and transmit a data value of the flow rate together with a geospatial location tag where the flow rate measurement was taken. In another example, a sensor 22 may measure air temperature in a room, and transmit that data value. If the geospatial position of the sensor 22 is known and previously recorded in the system, or may be determined by the system, the geospatial position may be associated with or linked to the measured temperature data value.

[0024] The database 12 is configured to store data. The data may be received from multiple inputs as described further below. The database 12 may receive and store data associated with a 3D model of a real asset. In one embodiment, a real asset may be, for example, a building or infrastructure, including, but not limited to, utility, transit and/or transportation infrastructure. In one embodiment, the data associated with the 3D model of a real asset may be stored as a first image representing a 3D depiction or model of the real asset. The database 12 may also retrieve or be connected to other databases having one or more real asset models stored therein. Alternatively, or in addition, the database 12 may store data or code associated with a real asset that allows another component, such as the visualization engine 16, to render a 2- dimensional (2D) or 3D model of the real asset based on the code or data.

[0025] The database 12 may also receive and store additional data from different data sources. For example, the database 12 may receive the additional data from other existing databases 14, the one or more sensors 22, or user input. Existing databases 14 may be, for example, publically accessible databases or private databases to which access is granted. In one embodiment, the existing databases may store publically accessible municipal data, privately accessible data, and/or user input or collected data, for example, infrastructure data, energy or utility data, transit or transportation data, communication data, planning and/or sustainability data and safety and/or security data.

[0026] The additional data may be related to fixed data sets, such as construction date, building material, location, address, building or construction type, building structural specifics such as footprint and height, construction specifics such as the number of windows or doors, and building equipment, such as HVAC or security equipment. Other types of additional data may include historical or archived data, or schedule data such as maintenance requests, repairs and records, status, property taxes, occupancy and other safety records, tenants, ownership and utilization of available resources. Still other types of additional data include those collected in real time or at predetermined intervals. This type of additional data may be collected, for example, by the sensors 22 described above, utility meter readings, user input and/or crowd sourced data. This additional data may include, for example, flow rates of fluids in a water or waste stream, utility supply and demand including electric, gas and water, traffic patterns and rates (measured in vehicle or persons per unit time at a particular location) including public transit, private transportation, pedestrian, cycling and the like, traffic control signal operation and cycles, temperature at particular locations, for example, within or near specific assets, luminous flux, wind, humidity, pressure, position of particular features of assets, including valves, doors, windows, switches and the like, and other similar, collectible data. This additional data may be collected and stored with respect to time so that changes in the additional data may be observed over time, as well as at a particular instant in time. The additional data may further relate to public safety notices, crime and safety data, emergency vehicle data, social media postings and the like. Additional data may also relate to telecommunication usage, including data usage, for example of high speed internet networks or cellular data networks. It is understood that the additional data described above is not exhaustive, and other measurable and fixed data is envisioned as well, including data derived from video or still images or computer models. The additional data may be stored in various documents received from the data sources. Thus the additional data is related to one or more real assets.

[0027] The system 10 may be used to render graphical 3D representations of real assets, for example, buildings, structures and infrastructure in a population center, with respect to time. The system 10 may also render the graphical 3D representations to include graphical or textual representations (or both) of the additional data related to the real assets displayed together with the models of the real assets. Thus, the database 12 may be provided where space (i.e., 3D modeling of real assets), time and the additional data are all connected to one another.

[0028] In general, raw data (e.g., data associated with a 3D model of a real asset and the additional data) stored in the database 12 may be accessed by a client device 20 through an Application Program Interface (API) 24. The raw data retrieved from the database 12 may be input into the 3D visualization engine 16 and output as a graphical 3D representation of a real asset, such as a building, with the additional data, such as one or more of the data values described above represented thereon in a graphical and/or textual format. The additional data may also be represented with respect to time. In one embodiment, the additional data may be represented in the graphical 3D representation as a color or shading on 3D model of the real asset. The additional data may also, or alternatively, be represented in the graphical 3D representation as text, as a graphic, or some combination thereof.

[0029] Preferably, the data in the database 12 is represented in a homogenous format, and thus provides a representation that enables the same processing (e.g.,

interconnection, search, navigation, and the like) in all dimensions (i.e., in the 3D models, time and documents). To this end, in one embodiment, the system 10 may use a common descriptive language to store all data or information. In one embodiment, the system uses XML as the universal encoding language. However, the present disclosure is not limited to this configuration and homogenous data formats are envisioned.

[0030] FIG. 4 is a diagram showing an embodiment of the database 12. The database 12 may refer to collection of databases. The database 12 may collect and store data received from the disparate sources (e.g., other databases 14, sensors 22 and user input) in different formats. The database 12 includes a database controller 220 having a data converter module 222 and a memory module 224. The database may also include an I/O module 226. The database controller 220, memory module 224 and I/O module 226 may be implemented in a manner similar to the controller 208, memory module 202 and I/O module 204 in the client device 20 above. Initially, an Application Program Interface (API) coordinates in which database 12 received data should be stored. The database controller 220 controls the data converter module 222 to analyze the file format of data of received from a data source, identify the file format, and convert or translate to file format to common file format for data to be stored in the database 12. Accordingly, the data may be unified in a common format before being visualized at the 3D visualization engine 16. In one embodiment, the common file format may be, for example XML. That is, a first file in a first format may be input into the data converter module 222, and a second file, in a second format may be output from the data converter module 222. For example, 3D models of real assets may be encoded in COLLADA XML, the additional data may be stored and indexed in XML documents, and time and other project information or data may be stored in separate XML documents.

[0031] That is, the data or information stored in the system 10, and in particular, in the database 12, may be stored in the same descriptive language, rather than a specific encryption type for each type of document or data. Accordingly, the information contained across various documents is available for searching, indexing, navigation and processing. For example, a search for a string in a document may return all the documents that contain reference to that search, which then may be used to visualize where in a 3D space the documents apply, and when in time this information was relevant.

[0032] The database 12 may be used by any client that can interface with it via an

API. For example, the database 12 may be implemented with the server 18, where the server 18 is a HTTP server providing a RESTful API and communicating with the client 20 through html, JSON and/or XML. In one embodiment, the server 18 may be implemented as a Web 2.0 engine, for example. Alternatively, or in addition, the server 18 may be a cloud server. The server 18 may include, for example, a memory module, and I/O module and controller, implemented similarly to the memory module, I/O module and controller described above with respect to the client device 20. Accordingly, the database 12 may be accessible through client devices 20, such as a desktop computer, laptop computer, mobile phone and/or tablets having existing web browsers. The database 12 may also be interfaced with other clients, web based applications or mobile applications. In one example, the database 12 or system 10 may be queried to return geolocations of specific assets, and return the information in a KML document, which may then be used in an existing web based geographical mapping application. The communication is triggered by the client 20, but is carried directly between an application and the database 12 without further involvement from the client application at the client 20. However, the present disclosure is not limited to web-based applications.

[0033] In some embodiments, the database 12 may be installed at the same computer or device as the client 20 for private use. In other embodiments, the database 12 may be a cloud application, remote from the client 20. In either application, the same interface is provided to various client applications.

[0034] The database 12 may be implemented with XML Native Database (XND) and xQuery language and other W3C standards. This implementation may provide increased flexibility and may handle new types of documents, searches, and links. For example, a user may use a MICROSOFT OFFICE application, such as MICROSOFT EXCEL, to create a spreadsheet of additional data, attach it to real assets, or a 3D model of a real asset stored in the database 12, and a specific timeline. The data is then available through client software. Accordingly, a user may enter new data without a database administrator or vendor creating a new type of schema or form to enter such data.

[0035] The asset models or data associated with 3D models of real assets, additional data and documents stored in the database 12 may be received from multiple and diverse sources as described above. Further, the asset models, additional data and documents may be directed or relate to variety of different metrics, data points, subjects or topics, as also detailed above. In addition to the data sources described above, the database 12 may also be connected to and receive data from the Internet of Things (IoT), public or open data, and commercial (M2M) sources. The additional data may be associated directly with the assets, such as the 3D models of real assets already stored in the database 12 and associated with a specific time or time frame. It is understood that additional data sources, types of data, and subject are envisioned in the embodiments described herein, and the examples of such provided herein are neither exhaustive nor limiting.

[0036] A graphic or 3D visualization engine 16 may be used to generate 3D models of real assets based on data associated with 3D models of real assets (i.e., data necessary to build the 3D models). The visualization engine may also generate graphical 3D

representations of the data associated with 3D models of the reals assets together with representations of the additional data associated with the real assets. In one embodiment, the 3D visualization engine may be implemented using CESIUM, which is a JavaScript library for creating 3D globes and 2D maps in a web browser without a plugin. CESIUM uses WebGL for hardware-accelerated graphics and is cross-platform, cross-browser and tuned for dynamic-data visualization. It is understood however, that other visualization engines are envisioned and may be suitable as well. The visualization engine 16 may alternatively be implemented as a game engine.

[0037] In one embodiment the 3D models of the real assets reflect a physical appearance of the real assets. That is, the digital 3D models form a virtual representation of the real assets. In addition, the graphic or 3D visualization engine 16 may graphically represent the time or additional data also stored in the database 12, as they relate to a specific real asset or group of real assets. For example, the 3D visualization engine 16 may compile the real assets as 3D models, and include further graphical features directed to a change in time or change in data over time. In one embodiment, the 3D visualization engine 16 may create a hierarchical display, where, for example, 3D models of different real assets, are displayed in different colors based on a threshold value or measured value of a particular data set of the additional date. The data set used for representing a threshold value or range may be retrieved from the additional data or documents stored at the database 12. Further, the 3D visualization engine 16 may include lighting or shading corresponding to a time of day, and shadows corresponding to 3D models of the real assets.

[0038] The 3D visualization engine 16 may also present the 3D models in a layered format, to include, for example, street level or aerial representations of the real assets, and representation of below ground assets, for example, real infrastructure assets, including, but not limited to utilities. That is, visual pealing back or sliding away of geospatial layers may be provided. Further, fly-through or drive -through functionality, representing aerial or ground level movement through or between a plurality of 3D models of real assets may be provided. The 3D visualization engine 16 provides this functionality to a user interface (UI) at the client 20 described further below. Further visual functionality provided to the user may include, but is not limited to: attribute based display of objects (coloring objects (e.g. models of real assets) based on attributes of that object (e.g., additional data related to the real asset)), filter based display of objects (provide capability to colorize an object based filtering on the attributes of that object (use type, number of doors, etc.)), ticker display of streaming text, and/or observer vs. scene toggle.

[0039] In one embodiment, the 3D visualization engine 16 may receive or retrieve one or more first images from the database 12 or other pre-existing database, for example, through an API. The one or more first images may be, for example, the 3D model of the real asset, such as a building or infrastructure, including utility, transit and/or transportation infrastructure, for example. Alternatively, the visualization engine may generate the 3D model of the real asset based on data associated with a 3D model of a real asset and store the generated model as the first image. The 3D visualization engine 16 may also receive the additional data or documents and related time information from the database 12. For example, the 3D visualization engine may receive data related to infrastructure data, energy or utility data, transportation or transit data communication data, planning and/or sustainability data and safety and/or security data, or similar types of other data, including those described herein.

[0040] In one embodiment, the 3D visualization engine 16 modifies the one or more first images based on the additional data and/or associated time information. For example, the 3D visualization engine 16 may add color or shading to the first image to create a second image, that is modified version of the first image. The color or shading corresponds to the additional data may be applied to the first image as whole, or a portion of the first image. For example, where the first image is a 3D model of a real asset such as a multi-floor building, a particular floor, or section of a floor may be shown in a different color indicating a value or threshold of a particular characteristic represented by the additional data. For example, where additional data indicates that a particular floor or section of a floor exceeds a maximum desired temperature, that floor or section of the floor may be shown with red shading added to it. That is, the first image may be modified to include shading, such as red shading, based on the additional data, and output as a second image including the model of the 3D asset and a graphical representation of the additional data. The additional data may also be added to the model of the 3D asset in a text or graphic format so that more precise values and data may be displayed to the user. In another embodiment, the 3D visualization engine 16 generates the graphical 3D representation as a new image based on the data associated with a #d model of a real asset and the additional data. In still another embodiment, the 3D visualization engine may generate graphical 3D representation of cityscape, i.e., a representation of multiple real assets in spatial relationship with one another. The additional data related to one or more of the real assets may be represented by, for example, coloring, text and/or graphics overlaying a portion of the cityscape representation. Some of the graphical representations may be transparent or translucent so as to show additional layers or detail.

[0041] In one embodiment, the visualization engine 16 represents the additional data in the generated graphical 3D representation of the real asset and additional data based on a rules engine or rules table stored a memory module, for example, the memory module 224 of the database 12 or the memory module 202 of the client device 20. The rules engine or table may include different colors associated with different types of additional data. In addition, the rules engine or table may associate different colors with different data values and establish

relationships between threshold values and colors used to represent the data value from the additional data. The rules engine or table may also dictate whether certain types of additional data are to be represented using text or graphics other than colors. For example, in one embodiment the rules engine may dictate additional data is represented using a red color when the data value of that additional data exceeds a threshold value. Conversely, the rules engine may dictate that additional data is represented using a green color when the data value falls within an acceptable range. Alternatively, the rules engine may dictate that the additional data is represented as a textual word or graphic (including, but not limited to, graphs or charts) based on a data value or type of data.

[0042] Accordingly, in the embodiments above, a user may manipulate a display of the client device 20 to virtually move through a graphical 3D representation of real assets. The representations of the assets may be identified and labeled within the system. Additional data associated with the assets may be accessed and viewed through selection of the asset or other menu options on the UI. That is, a geospatial data environment may be created, having 3D models of real assets, time data and additional data. All data may be represented graphically, textually or in graphic or text inserts or overlays displayed on the client 20. More than one graphical 3D representation and more than one representation of additional data may be simultaneously displayed to simulate a real world view of a combination of real assets. A user may operate the UI to switch between different graphical representations of real assets, such as a first asset and a second asset, and between representations of different sets of additional data, such as first additional data and second additional data. For example, a user may operate the UI to switch between a graphical representation of the first building (first real asset) and a second building (second real asset), or switch between a graphical representation of energy usage (first additional data) and room temperature (second addition data). It is understood that the present disclosure is not limited to these particular configurations, and different representations of real assets and types additional data may be viewed through use of the UI.

[0043] In one embodiment, the client 20 includes the 3D visualization engine 16 detailed above, combined with a HTML5 web browser engine. The client software

communicates with the database 12 via the API, which provides the 3D asset, time and additional data to the client application 20. The client 20 may also, or alternatively, be used with a known web browser. Preferably, the web browser includes some 3D rendering capabilities, for example, plug-ins including flash or WebGL, or integrating web browsing surfaces inside a 3D application, such as Vivaty or Second Life. In another embodiment, the 3D visualization may be cloud-based rather than located at the client 20. Accordingly, a cloud server 18 may

communicate with database 12 to retrieve the 3D, time and data content and the 3D visualization engine may visualize the content at the cloud server. The visualized content may then be provided to the client device 20.

[0044] In one embodiment, the client 20 includes the 3D visualization engine 16 together with a web browser operating side -by-side, as opposed to architectures where one is fit into another. In use, in one embodiment, the 3D visualization engine 16 and the web browser have access to the entire viewable screen on the display. A compositing stage is then applied to the two outputs, where the 3D visualization engine 16 rendering is used as the background to the web browser screen. The architecture may enable the reverse order, or in fact any number of those layers in any order. The background of the web page is replaced with transparent pixels, which are transparent to both the color, and the events. In other words, where there is no html object (or User Interface), the rendering of the 3D model appears. The transparency to events works the other way around as well, when there are no web page elements, the user events (mouse/keyboard events) are sent directly to the 3D model. Such a sharing of the screen resource is invisible to the user, which can indifferently interact with the 3D view or the 2D interface, on a per pixel basis.

[0045] Both the 3D engine and the web browser may be multithreaded applications, and may spread to multiple CPU cores automatically. The two systems may be interconnected and threads of both subsystems can be managed, for example, by one or more processors or CPUs, so that the priority is given to non-starving threads to maintain a smooth operation. That is, in one embodiment, the system 10 may include a distributed processing configuration across multiple client devices 20 and/or processors, or a parallel processing configuration where a single client device 20 uses multiple processors or CPUs to increase efficiency and performance by reducing or avoiding bottle necks. The systems may be interconnected, for example, by an API or core service application that intermediates between the client and database layers and provides the uniform encoding language. The one or more processors may be, for example, at the client device 20, the server 18 and another system component, or combination of components.

[0046] The interconnected subsystems also provide a programmatic interface between the 3D visualization engine 16 and the web browser engine, namely a Javascript conduit interface. The html page (served by the database 12 system or other http server 18) displayed by the web browser component may have a Javascript program that can make calls into the conduit API, which will trigger an action executed within the 3D visualization engine (e.g. "load 3D model", "move camera", "show object X as selected). The 3D application may also callback into the web browser component, provided the html page contains the entry point (e.g., the use click on a 3D model, which will trigger the 3D engine to do a Javascript callback to signal the web browser that an object has been selected in the 3D view, mimicking the standard event system used by web pages).

[0047] The web browser has built in capability for scripting, caching, and streaming. The client device 20 utilizes these capabilities, as opposed to a design where the 3D visualization engine would have to implement its own scripting, caching and content streaming. The system 10 may use the conduit API for the 3D visualization engine to callback into the web browser which will then use standard http mechanism to query for resources, as well as providing local caching for performance.

[0048] Although the description above relates to web-specific embodiments operable via web browser, it is understood that the present disclosure is not limited to this configuration. For example, the web browser functionality may be replaced with native client installed at a client device 20, for example, at a desktop computer or a mobile application.

[0049] FIGS. 5-9 are diagrams showing architectures for use in or with the system 10 described above. For example, referring to FIGS. 5-9, and particularly to FIG. 5, the architecture may be cloud-based and include three tiers. One tier, for example a

client/application tier, may include one or more databases, including the database 12 and external databases 14, which may include private and cloud databases. An application module, having applications for different uses may also be at the client/application tier. The different applications may include, for example, energy, infrastructure, transportation, environment, civic and/or planning. The application module is in communication with the databases 12, 14 and may transmit or receive information to or from the databases.

[0050] The middle tier may be, for example, an enterprise tier, and include an IoT

Module 26, M2M Module 28 and a Model Rendering Module 30. These modules may operate across multiple platforms and devices. The remaining tier may include an API to be used by application developers to develop applications using the data from the databases 12, 14. The security layer and communications layer may extend across all tiers, while the API may extend across the client/application tier and the enterprise tier.

[0051] The system 10 may support standards and allow for more flexible integration with various subsystems both internal and external to city systems and service. The system may be built on modern Web 2.0 technologies, and may be readily deployed as a cloud platform or behind a firewall. A Web Standards approach may allow for convenient user access. The browser-based client 20 may present a visually engaging 3D experience and the ability to quickly adapt the user interface through HTML5 for various applications and roles. The platform is compatible with most 2D and 3D modeling environments and it utilizes an open standard file format supported by the Khronos Group, which develops and supports most web 3D graphics standards (e.g. OpenGL ES, WebGL). The information repository that provides much of the flexibility, extensibility and data aggregation is also based on open standard formats, namely XML. The use of a native XML (NXD) database for data aggregation may ensure the flexibility and scalability required for large scale nature of the data. Connecting to these subsystems is accomplished through a set of Javascript, REST, and AJAX APIs that insulate the application developers from the complexity of managing the information and relationships, which allows them to focus on the overall user experience and accessibility to the underlying information network.

[0052] FIGS. 10-13 are tables showing examples of situations of where and how the system 10 may be employed, subsystem integration, functionality, and data types utilized. For example, one potential application of the system 10 described herein may be for a water inspector. The water inspector may wish to access 3D visuals of water pipes, sewers and mains (i.e., real assets). Using the system 10 described herein, according to the embodiments above, the water inspector may view a 3D model of the current infrastructure while in a field from an upcoming event. That is, the database 12 may include a 3D model of real assets, such as water pipes, sewers and mains. The database 12 may also include additional information such as upcoming inspection and/or maintenance events. The 3D visualization engine 16 may receive the 3D model and the additional information and combine them into a single image that the inspector may view from the client device 10.

[0053] In another example, a city planner may wish to generate estimates for permits and coordination with other civic works, such as power services. The system 10, having additional data received from multiple sources, including municipal and private utilities, and real assets, such as infrastructure, may view a schedule of operations, maintenance and downtime on the real asset so coordinate these operations to minimize downtime or interference with normal use. That is, scheduled uses, including repairs, maintenance, down time and the like by different agencies may be centralized into a single display by the system 10 described herein.

Accordingly, the different uses or operations may be coordinated to increase efficiency.

[0054] FIG. 14-28 are examples of the UI 300 displayed on a screen at the client device 20, according to an embodiment described herein. Referring to the examples in FIGS. 14- 28, the system may first require user authentication 302. Upon verification of proper

authentication, the UI 300 may then display the 3D models of the real assets. In one example, the UI 300 displays a 3D rendering of a desired cityscape, including buildings, roads, and other structures and infrastructure. The UI 300 may also include a menu bar 304 having one or more menu options and a plurality of submenu options. For example, referring to FIG. 15, the menu bar 304 may include options such as MENU 306, SELECT 308, BUIDLINGS 310, ENERGY 312, TRANSPORT 314, ROAD 316, ENVIRONMENT 318, CUSTOM 320, POWER 322, ROUTING 324, HEAT MAPS 326, RISK PROFILES 328, MEASURE 330 and LINE OF SIGHT 332.

[0055] A user may manipulate the client device 20 to select a desired item from the menu bar 304. For example, the user may control a pointer device (not shown) connected to the client device 20, to move to a desired menu bar option, and select the desired option through operation of, for example, a click or hover of the pointer device. Alternatively, the display at the client device 20 may be touch screen display that recognizes contact from user or stylus at desired location to select a desired menu option. In one embodiment, the locations of the menu options are mapped to different functions and stored in the database 12 or in the memory module at the client device 20. Upon receiving a click from a pointer device or a touch on a touch screen, the location of the pointer or the touch is compared to the mapped locations corresponding to the different menu options. Where the click or touch corresponds to a location of a menu option, the processer operates the client device 20 to change the displayed UI 300 to a new UI 300 corresponding to the desired menu option. In another embodiment, the client device 20 may include a voice or word recognition module (not shown) and a microphone module (not shown), and menu selections may be made via voice commands from the user. These steps may be carried out by the controller 208 at the client device 20.

[0056] In one example, the selection of, or hovering over the MENU 306 option presents a sub-menu, including, for example, NEW WORKSPACE 334, PROJECT 336, BOOKMARKS 338, ANALYSIS 340, LAYERS 342, SETTING 344, HELP 346 and QUIT 348. Selection of or hovering over a sub-menu may bring about a display of another sub-menu. For example, selection of or hovering over ANALYSIS 340, may present another sub-menu with additional options as shown in FIG. 16. Selecting or hovering over PROJECT 336 may present another sub-menu with options include, for example, NEW 350, OPEN 352, OPEN RECENT 354, SAVE 356, SAVE AS 358, CREATE REPORT 360, SENT TO 362, PRINT SETUP 364 and PRINT 366, as shown in FIG. 17. [0057] Referring to the example FIG. 18, selecting or hovering over BUILDINGS

310 may present a drop down menu or sub-menu with options including FACADE 368,

STRUCTURAL 370, INFRASTRUCTURE 372 and SUBSTRUCTURE 374. Referring to the example in FIG. 19, selecting or hovering over ENERGY 312 may present a drop down menu having options WATER 376, SEWER 378 and SOLAR 380. Referring to FIG. 20, the selecting or hovering over TRANSPORT 314 may present a drop down menu having options METRO 382, SUBWAY 384, BUS 386, TAXI 388 and FAA 390. Referring to FIG. 21, selecting or hovering over ROAD 316 may present drop down menu options ROADS 392, TRAFFIC LIGHTS 394, PARKING 396, and TRAFFIC 398. Referring to FIG. 22, selecting or hovering over ENVIRONMENT 318 may present drop down menu options TREES 400, PARKS 402, GREEN BELTS 404, AIR QUALITY 406, CIVIC APPl 408 and CIVIC APP2 410. Referring to FIG. 23, selecting CUSTOM 320 may present drop down menu options LAYERl 412, LAYER2 414, LAYER3 416, LAYER4 418, ADD LAYER 420 and BUILD QUERY 422. Referring to FIG. 24, selecting or hovering HEAT MAPS 326 may present drop down menu options BUA 424, TRAFFIC 426 and CRIME 428. Referring to FIG. 25, selecting or hovering on a magnifying glass 430 may present a text search box 432. Referring to FIG. 26, selecting or hovering the time 434 may present an enlarged clock graphic 436. Referring to FIG. 27, selecting or hovering on the date 438 may present calendar 440 for example, displaying a one month view. It is understood the above menu options are described for the purpose of example only, and are not exhaustive, nor required. Rather, the menu options described herein may be included or excluded depending on customer needs and applicability.

[0058] The menu and sub-menu options may be linked to data or information stored in the database 12 or external database 14. Selection of one of these options may cause the data or information to be retrieved, processed in the 3D visualization engine 16 and displayed graphically or textually at the client 20 on the UI 300. In one embodiment, these actions may be initiated or controlled by the controller 208 at the client device 20.

[0059] Information may also be processed behind the API and delivered to the client for visualization. For example, in one embodiment, a real asset, such as a sewer may be modeled at the cloud server 18, cached, and then delivered to the client 20 with minimal data alongside for interaction or annotation as compressed, high-performance model. It is understood the server 18 described above may be a cloud server, or alternatively, a cloud server may be implemented in the system 10 as a separate component.

[0060] Other menu and sub-menu options may be selected to operate and navigate the UI 300. In some embodiments, for example, as shown in FIG. 28, the UI may be utilized to displaced information or data regarding a specific selected building. The building may be selected via the UI 300, for example, the selecting a 3D model of the desired building, or selecting from a list. Selection of particular 3D model of a real asset initiate retrieval of the additional data associated with the selection 3D of a real asset. The 3D visualization engine 16 may then modify the 3D model of the real asset to include additional representation, either graphically or textually, based on the additional data. The updated graphical representation of the real asset, including representations of selected additional data, may then be generated at or transmitted to the client device 20, where the updated representation may be displayed. It is understood that these items are non-exhaustive, and additional information or data may be retrieved and displayed, for example, utility and waste information.

[0061] Further still, it is understood that the examples shown in the UI 300 frames of FIGS. 14-28 are non-exhaustive, and the UI 300 may display other or additional information or views. For example, the UI 300 may be navigated to retrieve infrastructure information. In one example, the infrastructure may be below ground. The UI 300 may be navigated to show a below ground display of a 3D model of such infrastructure. Additional information may also be displayed. For example, maintenance records, operating status and historical operating status and performance metrics may be displayed. Such information may be stored in the database, and entered and/or updated, for example, through sensors 22 monitoring the infrastructure, or by a user. Information stored in the database 12 is preferably time stamped so that the information may be associated with a particular time, and may be displayed as a function of time. Further, in the embodiments above, the menu, sub-menu and drop down menu options may include a graphic or image next to the option, where the graphic is a graphical representation of the menu option.

[0062] Referring to FIG. 28, in some embodiments, a user can select a graphical

3D representation of a real asset 450 from the display 210. In response to selection of the graphical 3D representation, related additional data 452 may be displayed. In one embodiment, the related additional data 452 may include a building address, structural information of the building including, but not limited to, building height, area and opening date. Other additional data 452 may include owner information, building materials, and occupancy levels. Other additional data 452 may also be selected, for example projects, energy, water, community and schedule information. In this embodiment, the additional data may be represented in a textual and graphical manner on the display 210.

[0063] FIG. 29 is a diagram showing a method of generating and displaying a geospatial data environment, according to the embodiment described herein. Referring to 1, 2, 28 and 29, for example, the method includes, at 510, receiving, at the database 12, data from one or more sources, the data comprising data associated with a 3D model of a real asset 450 and additional data 452 related to the real asset, at 512, converting the received data to a uniform encoding language, such as XML, and storing the converted data at the database and at 514, receiving a request to generate a graphical 3D representation. The method further includes, at 516, transmitting the converted data to a 3D visualization engine 16, at 518, generating a graphical 3D representation 454 based on the data associated with a 3D model of the a real asset 450 and the additional data 452, at 520, outputting the graphical 3D representation 454 to a display 210, and at 522, displaying the graphical 3D representation 454 of a real asset 450 and additional data 452 associated with the real asset. The additional data 452 may be graphically represented through different colors, for example, and may be selectively filtered by a user. The additional data may also be displayed as text in a text box or a combination of text and graphics in an information box 456 inserted into the 3D model or on the UI 300. The client 20 may then display the graphical data created by the visualization engine 16. A UI 300 at the client 20 allows a user to navigate the displayed data, search for and request additional or alternative data.

[0064] In one embodiment, the client requests to the database 12 (or 14) go through an API 24 relevant to the database. In one embodiment, the 3D models may be created at a cloud server 18 and made into models by the 3D visualization engine when combined with the additional data. The 3D models may be, for example, static building models that may be provided to the 3D visualization engine 16 by a Content Delivery Network (CDN). Other 3D models of real assets, for example, infrastructure models such as sewer data, may be modeled in other software, such as geoJSON in the database 12. Thus, some models of real assets may be previously generated and stored, while other models may be created based on city data sources shortly before or during data collection at the database 12. [0065] Further, as described above, an electronic client device 20 may include the display 210, the I/O module 204, the communication module 206 configured for connection to a communication network, the memory module 202 and the controller 208 having one or more microprocessors. The memory module 202 stores a program instruction or instructions configured to be executed by the one or more microprocessors for displaying a first graphical 3D representation of a first real asset generated based on data associated with a 3D model of the first real asset and first additional data related to the first real asset, wherein the data associated with a 3D model of the first real asset is displayed as a rendering of the first real asset in the graphical 3D representation 454, and the first additional data is displayed as a color or text on at least a portion of the rendering of the first real asset in the graphical 3D representation 454. Different colors or text are displayed to represent different values of the first additional data. In some embodiments, the first additional data includes a geospatial position tag associated or combined with a data value, wherein the geospatial position tag corresponds to a geospatial position on the first real asset where the data value was measured. The graphical 3D representation 454 also includes the first additional data at a position on the rendering of the first real asset based on the geospatial position tag. In some embodiments the visualization engine 16 may be located at the client device 20, while in other embodiments, the communication module 206 may receive the graphical 3D representation 454 via a data stream, and the display 210 displays the received graphical 3D representation 454.

[0066] In one embodiment, the instructions may further include instructions for displaying a UI 300 on the display, the UI 300 having one or more menu options. In one embodiment, the instructions may further include receiving an instruction indicating a selection of a menu option, and in response to receiving the instruction, displaying a second graphical 3D representation different from the first graphical 3D representation.

[0067] In one embodiment, the second graphical 3D representation is generated based on the data associated with the 3D model of the first real asset and second additional data related to the first real asset. Further, in one embodiment, the second graphical 3D representation is generated based on the data associated with a 3D model of a second real asset and first additional data related to the second real asset.

[0068] The methods above may be stored as program instructions in one or more computer-readable storage media, and carried out by a microprocessor. Computer-readable storage media include non-transitory media, for example, magnetic media, including hard disks and floppy disks; optical media including CD ROM disks and DVDs, and/or optical disks.

Computer-readable storage media may also include hardware devices configured to store and/or perform program instructions, including read-only memory (ROM), random access memory (RAM), flash memory and the like. Further, computer-readable media may include Solid State Drives (SSDs) and remote or distributed memory devices or services. It is understood that non- transitory media does not include signals or waves.

[0069] It is envisioned that the above systems and methods may be utilized by, for example, a municipality's technology or innovation department, department of transportation or transit authority, business affairs and consumer protection, municipal utilities and services, and/or private or semi-private companies or stakeholders with interests in infrastructure or utilities, above or below ground. In addition, the above systems may be utilized by data consumers, political and civil leaders, high level managers, partners, stakeholders, associates, system administrators, IT/IS, analysts, planners, support staff, an external or internal agent, users of output city data, citizens and/or application developers. The system and methods may be used in the context of a smart city. Thus, in the embodiments above, a system and method for creating a geospatial data environment are provided. Further still, a public API may be available for application developers, where the developers may access the data stored in database 12 to create, for example, mobile applications utilizing the data stored in the database 12 or other databases 14.

[0070] In one example, a customer or user may determine the metrics or data which is desired to be visualized. The system 10 described herein is configured to collect and store the desired data and a database 12 and use the data to create visual representations. These representations may be useful to allow inter-departmental coordination and sharing of resources. The metrics are typically related to energy, infrastructure, transportation, communications, planning /sustainability, and safety/security. The system 10 may utilize a cloud based service to carry out the functions described in the embodiments above. Accordingly, the storage and performance needs may be expanded and scaled easily. Customers, such as cities, may also implement a self-hosted cloud service that may reside behind a protected firewall. The system described herein is portable and modular to all for various deployments and include fully hosted or shaped services. Some solutions may include a dedicated hosting via physically located servers owned by and within a particular city. Access between the system 10 and the dedicated hosting may be provided through the API.

[0071] Cloud hosted data services are developed and connected to the UI and the

3D visualization engine. Data services include operational, data management and data manipulation. Operational data services are developed and used for application driven demands. The data management services are developed to allow curation, metadata look up, ontology and transaction services to support requirements. The data manipulation services are developed access to standard databases and geodatabases (e.g., MySQL, Oracle, SQLServer, etc.), standard and custom data formats (OGC, .txt, .xls, and the like), and other data sources and data streams (APIs, GeoRSS, REST calls, and the like).

[0072] To accept the data, i.e., the models of the real assets and the additional data, and present the 3D models and additional data, the system described herein includes the 3D visualization engine 16 and the UI. The UI (HTML 5, Javascript and WebGL, for example) includes menus and buttons to engage a user with easy access to projects and workspaces, connect to and load data, build and save queries, create and design visualization analysis, and search and locate data. The UI may also be a native UI for native desktop and mobile applications. Thus, this system 10 described herein provides a secure system utilizing cloud infrastructure, a web interface, multidimensional information rendering, smart and intelligent modules, a collective application market and a smart city ecosystem.

[0073] In the embodiments above, the raw data at the database 12 and/or other databases 14, including the real asset models and additional data, may be made into the visualized data at a 3D visualization engine 16 on the client device 20. Alternatively, the raw data may be made into optimized or compressed model data, cached in the cloud, and served directly to the client device 20 for rendering only, with only minimal accompanying data for annotations and the like. As another alternative, the raw data and graphical representations thereof may be completely generated in the cloud for rendering claims on the client device 20 in a streaming manner.

[0074] Further, in the embodiments above, a service may sit both in front and behind the database architecture and include an API, both public and private, that provides data on request to the client. The service may include web hooks or the like connecting it to data sources to control ingestion and processing of data into an internal format for the system described above.

[0075] It is understood that various features described in relation to one embodiment above may be implemented or used together with the other embodiments described above. It is also understood that where description of certain components may be omitted in the discussion of one embodiment, where such components are similar or identical to those described in other embodiments.

[0076] It should also be understood that various changes and modifications to the presently disclosed embodiments will be apparent to those skilled in the art. Such changes and modifications can be made without departing from the spirit and scope of the present disclosure and without diminishing its intended advantages. It is therefore intended that such changes and modifications be covered by the appended claims.

Claims

1. A system for aggregating, analyzing and graphically displaying data collected from one or more data sources, comprising:

one or more data sources;

a database configured to receive data from the one or more data sources, the database comprising a converting unit configured to convert all received data into a uniform encoding language, the data comprising data associated with a 3D model of a real asset and additional data related to the real asset;

a 3D visualization engine configured to receive the data associated with a 3D model of a real asset and the additional data related to the real asset with respect to time, generate a graphical 3D representation of the real asset and the additional information, and output the generated graphical 3D representation to a display, wherein the data associated with the 3D model and the additional data are received from the database;

a client device connected to the display and configured to display the graphical 3D representation generated at the visualization engine, the client device further configured to display a graphical user interface together with the graphical 3D representation; and

a server communicably connected between the database and a client.

2. The system of claim 1 , wherein the server is a cloud based server.

3. The system of claim 1, wherein the server is an HTML 2.0 server.

4. The system of claim 1, wherein the 3D visualization engine is located at the client device and the client device receives the data associated with the 3D model of a real asset and the additional data and the 3D visualization engine generates the graphical 3D representation at the client device.

5. The system of claim 1, wherein the 3D visualization engine is located at the server and the graphical 3D representation is completely rendered at the server and delivered to the client device via a data stream over a communication network.

6. The system of claim 1, the data associated with the 3D model of a real asset and the additional data related to the real asset are compressed at the server and delivered to client device for rendering at the client device.

7. The system of claim 1, further comprising an Application Program Interface (API) positioned between the client device and the database to facilitate communication between the client device and the database.

8. The system of claim 1, wherein the data associated with a 3D model of a real asset is displayed as a rendering of the real asset in the graphical 3D representation, and the additional data is displayed as a color on at least a portion of the rendering of the real asset in the graphical 3D representation.

9. The system of claim 8, wherein different colors are displayed to represent different values of the additional data.

10. The system of claim 9, wherein the display of the additional data on the graphical 3D representation changes with respect to time as the additional data changes with respect to time.

11. The system of claim 9, wherein the additional data includes a geospatial position tag combined with a data value, wherein the geospatial position tag corresponds to a geospatial position on the real asset where the data value was measured.

12. The system of claim 11, wherein graphical 3D representation displays the additional data on the rendering of the real asset based on the geospatial position tag.

13. A method of generating and displaying a geospatial data environment:

receiving, at a database, data from one or more sources, the data comprising data associated with a 3D model of a real asset and additional data related to the real asset; converting the received data to a uniform encoding language and storing the converted data at the database;

receiving a request to generate a graphical 3D representation;

transmitting the converted data to a 3D visualization engine;

generating a graphical 3D representation based on the data associated with a 3D model of the a real asset and the additional data;

outputting the graphical 3D representation to a display; and

displaying the graphical 3D representation of a real asset and additional data associated with the real asset.

14. An electronic client device comprising:

a display;

an input/output module;

a communication module;

a memory module; and

one or more microprocessors,

wherein the memory module stores program instructions configured to be executed by the one or more microprocessors for:

displaying a first graphical 3D representation of a first real asset generated based on data associated with a 3D model of the first real asset and first additional data related to the first real asset, wherein the data associated with a 3D model of the first real asset is displayed as rendering of the first real asset in the graphical 3D representation, and the first additional data is displayed as a color on at least a portion of the rendering of the first real asset in the graphical 3D representation,

wherein different colors are displayed to represent different values of the first additional data,

wherein the first additional data includes a geospatial position tag combined with a data value, wherein the geospatial position tag corresponds to a geospatial position on the first real asset where the data value was measured, and

wherein the graphical 3D representation includes the first additional data at a position on the rendering of the first real asset based on the geospatial position tag.

15. The electronic client device of claim 14, further comprising a 3D visualization engine, wherein the 3D visualization generates the graphical 3D representation.

16. The electronic client device of claim 14, wherein the communication module receives the graphical 3D representation via a data stream and the display displays the received graphical 3D representation.

17. The electronic client device of claim 14, wherein the instructions further include displaying a graphical user interface comprising one or more menu options.

18. The electronic client device of claim 17, wherein the instructions further include receiving an instruction indicating a selection of a menu option, and in response to receiving the instruction, displaying a second graphical 3D representation different from the first graphical 3D representation.

19. The electronic client device of claim 18, wherein the second graphical 3D representation is generated based on the data associated with the 3D model of the first real asset and second additional data related to the first real asset.

20. The electronic client device of claim 18, wherein the second graphical 3D representation is generated based on the data associated with a 3D model of a second real asset and first additional data related to the second real asset.