Patent Application
20160266777
The present disclosure is related to the subject matter of commonly assigned, co-pending application Ser. No. 14/015,864 filed on Aug. 30, 2013, co-pending application Ser. No. 14/015,856, filed on Aug. 30, 2013, and co-pending application No. 15/165,915, filed on even date herewith.
1. Technical Field
The present disclosure generally relates to computer systems and in particular to computer-implemented methods of presenting data in a graphical overlay.
2. Description of the Related Art
The management and operation of cities and/or enterprises is a challenging task, particularly with the ever-increasing size and number of entities within them. In order to make well-informed decisions regarding city and/or enterprise operations, relationships between and among entities, such as buildings, equipment, etc., and related information such as maintenance history and schedules, must be available and understood. The modeling of complex relationships among such entities is challenging and becomes more difficult as the complexities of cities/enterprises increase. Semantic models have been used to model the relationships among city/enterprise entities, and specifically have been used to describe linkages between and among different sets of data across various entities. However, in order to learn anything about the relationships and associations defined by a semantic model, a user must construct a set of fairly complex queries (e.g., structured query language (SQL) queries) in order to retrieve desired relational information about the entities. Additionally, users often need ways to navigate such complex and layered datasets beyond the current practice of using map-based metaphors, structured queries, visual time sequences, SQL queries, etc.
Disclosed is a method for presenting data in a graphical overlay. The method displaying the graphical overlay on a spatial rendering of data, where the graphical overlay includes a spatial rendering of data including one of a geospatial map, a logical map, and a system map. A first lens, including at least one first context, is overlaid on a first region of the graphical overlay, where the at least one first context is accessible by manipulation of the first lens. The at least one first context is activated within the first lens, and in response to activating the at least one first context, a first dataset, which corresponds to the first context, is obtained from at least one of a plurality of sources. The first dataset is displayed within the first lens, where the displayed first dataset is a visual representation of a first context dataset. A second lens including at least one second context, is overlaid on a second region of the graphical overlay. The at least one second context may be activated within the second lens. In response to activating the at least one second context within the second lens, a second dataset corresponding to the second context is obtained, and the second dataset is displayed within the second lens while simultaneously displaying the first dataset within the first lens. The displayed second dataset is a visual representation of a second context dataset. In response to simultaneously displaying the visual representations of the first and second context datasets, a correlation between the first and second datasets may be determined. In addition, a first region of the graphical overlay is circumscribed within each of the first lens and the second lens, and the first lens and the second lens are separated to provide one of a partially overlapping and a non-overlapping spatial relationship between the first and the second lens. In response to separating the first lens and the second lens, the first circumscribed region of the spatial rendering of data (i.e., geospatial, logical, or system map) within each of the first and second lenses are preserved, and a second non-circumscribed region may be concealed. The first dataset is thus displayed within the first lens and the second dataset is displayed within the second lens.
In some embodiments, the first lens is oriented in a first position, where the first dataset corresponds to the first position, and the first lens is rotated around an axis of rotation until the first lens is oriented in a second position. In response to rotating the first lens around the axis of rotation, the first dataset is reconfigured to provide a modified first dataset, and the modified first dataset is displayed within the first lens, where the modified first dataset corresponds to the second position. A rotational position of the first lens may be associated with specific points in time, where the first position corresponds to a first point in time and the first dataset represents the first dataset at the first point in time. In response to rotating the first lens in a first direction around the axis of rotation, to a second position that corresponds to a second point in time occurring after the first point in time, a corresponding later-in-time version of the first dataset is displayed within the first lens, where the later-in-time version of the first dataset corresponding to the second position includes projected data. In response to rotating the first lens in a second direction around the axis of rotation, to a second position that corresponds to a second point in time occurring before the first point in time, a corresponding earlier-in-time version of the first dataset is displayed within the first lens, where the earlier-in-time version of the first dataset corresponding to the second position includes historical data.
The above summary contains simplifications, generalizations and omissions of detail and is not intended as a comprehensive description of the claimed subject matter but, rather, is intended to provide a brief overview of some of the functionality associated therewith. Other systems, methods, functionality, features and advantages of the claimed subject matter will be or will become apparent to one with skill in the art upon examination of the following figures and detailed written description.
The description of the illustrative embodiments can be read in conjunction with the accompanying figures. It will be appreciated that for simplicity and clarity of illustration, elements illustrated in the figures have not necessarily been drawn to scale. For example, the dimensions of some of the elements are exaggerated relative to other elements. Embodiments incorporating teachings of the present disclosure are shown and described with respect to the figures presented herein, in which:
The illustrative embodiments provide a method for displaying a graphical overlay on a spatial rendering of data. A first lens, including a first dataset, is overlaid on a first region of the graphical overlay. A second lens, including a second dataset, is overlaid on a second region of the graphical overlay. The first and second datasets are simultaneously displayed, and a correlation between the first and second datasets is determined. In addition, separation of the overlapping first and second lenses results in preservation of a circumscribed region within each of the first and second lenses. The first dataset may also correspond to a first orientation position of the first lens. Rotation of the lens around an axis of rotation to a second orientation position results in reconfigured of the first dataset to provide a modified first dataset which corresponds to the second position. In some embodiments, a rotational position of the lens may also be associated with specific points in time, where a first position corresponds to a first point in time and the first dataset represents the first dataset at the first point in time. Rotation of the lens to a second position corresponds to a second point in time occurring before or after the first point in time, where a corresponding earlier-in-time or later-in-time version of the first dataset corresponds to the second position.
In the following detailed description of exemplary embodiments of the disclosure, specific exemplary embodiments in which the disclosure may be practiced are described in sufficient detail to enable those skilled in the art to practice the disclosure, and it is to be understood that other embodiments may be utilized and that logical, architectural, programmatic, mechanical, electrical and other changes may be made without departing from the spirit or scope of the present disclosure. The following detailed description is, therefore, not to be taken in a limiting sense, and the scope of the present disclosure is defined by the appended claims and equivalents thereof.
In the following detailed description, numerous specific details such as specific method orders, structures, elements, and connections have been set forth. It is to be understood however that these and other specific details need not be utilized to practice embodiments of the present disclosure. In other circumstances, well-known structures, elements, or connections have been omitted, or have not been described in particular detail in order to avoid unnecessarily obscuring this description.
References within the specification to “one embodiment,” “an embodiment,” or “embodiments” are intended to indicate that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the present disclosure. The appearance of such phrases in various places within the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. Moreover, various features are described which may be exhibited by some embodiments and not by others. Similarly, various requirements are described which may be requirements for some embodiments but not other embodiments.
It is understood that the use of specific component, device and/or parameter names (such as those of the executing utility/logic described herein) are for example only and not meant to imply any limitations on the disclosure. The disclosure may thus be implemented with different nomenclature/terminology utilized to describe the components/devices/parameters herein, without limitation. Each term utilized herein is to be given its broadest interpretation given the context in which that terms is utilized.
Those of ordinary skill in the art will appreciate that the hardware components and basic configuration depicted in the presented figures may vary. For example, the illustrative components within the data processing system (DPS 100,
With reference now to the figures, and beginning with
A DPS, such as DPS 100, can include at least one processing unit (CPU) 122, a system memory 126 coupled to a memory controller 128, and a system interconnect fabric 130 that couples memory controller 128 to CPU 122 and other components of DPS 100. System interconnect fabric 130 in an embodiment can be an address and data bus. Commands on system interconnect fabric 130 are communicated to various system components under the control of bus arbiter 132.
DPS 100 can further include cache memory 123 for high speed storage of frequently used data. Cache memory 123 can be connected to or communicatively coupled with CPU 122. While cache memory 123 is shown operatively connected to CPU 122, cache memory 123 can also operatively be a part of system memory 126.
DPS 100 further includes computer readable storage media, such as one or more multimedia drives 138, including for example hard disk drives. Multimedia drives 138 provide non-volatile storage for DPS 100. DPS 100 also includes one or more user interface devices, which allow a user to provide input and receive output from DPS 100. For example, user interface devices can include displays 134, universal serial bus (USB) ports 136, keyboards 140, and pointing devices such as a mouse 142. Multimedia drives 138 and the various user interface devices can be communicatively coupled to system interconnect fabric 130 by an input-output (I/O) interface 135. Although the description of computer readable storage media above refers primarily to a hard disk, it should be appreciated by those skilled in the art that other types of media which are readable by a computer, such as removable magnetic disks, CD-ROM disks, magnetic cassettes, flash memory cards, digital video disks, Bernoulli cartridges, and other later-developed hardware, may also be used in the exemplary computer operating environment.
DPS 100 also comprises storage 152, within which data/instructions/code may be stored. Storage 152 is communicatively coupled to system interconnect fabric 130. In addition to the above described hardware components of DPS 100, various features of the disclosure are completed via software (or firmware) code or logic stored within system memory 126 or other storage (e.g., storage 152) and executed by CPU 122. In one embodiment, data/instructions/code from storage 152 populates the system memory 126, which is also coupled to system interconnect fabric 130 via the memory controller 128.
DPS 100 may also operate in a networked environment using logical connections to one or more remote computers or data processing systems, such as DPS 102. DPS 102 may be a computer, a server, a router or a peer device and typically includes many or all of the elements described relative to DPS 100. In a networked environment, program modules employed by DPS 100, or portions thereof, may be stored in a remote memory storage device 150. The logical connections depicted in
To facilitate the collection and analysis of data/information from various sources, the illustrated operations environment 200 may include network-specific semantic models, which contain information related to a particular network (i.e., domain), including specifications, maintenance records/schedule, failure history, composition, and cost, among others. Moreover, in various embodiments, the operations environment 200 includes a reference semantic model which provides a linkage between/among the network-specific semantic models (i.e., between/among multiple data sets), and can be used to model complex relationships between and among the various network entities, for example in a city or enterprise, such as devices, equipment, buildings, infrastructure, etc. Thus, the reference semantic model can be used to model the relationship of such network entities to one another and to other non-tangible items mentioned above such as maintenance records/schedule, failure history, composition, and cost, among others. By modeling these relationships and associations, specific interactions between and among network entities may be better understood. However, in order to extract this information from the semantic models, complex queries (e.g., structured query language (SQL) queries) are used to retrieve the desired relational information. Furthermore, in various embodiments, in addition to data obtained via one or more semantic models as mentioned above, data within the operations environment 200 may include data from one or more of a plurality of other data sources such as historical data, projected data, user inputted data, web content, streaming content, data obtained from a local database, and data obtained from a remote database, among others. Users also often need ways to navigate such large, complex, and layered datasets beyond the current practice of using map-based metaphors, structured queries, visual time sequences, SQL queries, etc. Thus, the present disclosure provides a solution that addresses a need for an intuitive, singular way to render data (e.g., from one or more of a plurality of data sources) geospatially or in the context of an entire system or set of systems. Further, the present disclosure provides a solution that addresses a need for an intuitive way to rapidly visualize and comprehend complex, layered datasets, from one or more of a plurality of data sources, by providing a method for visually navigating data in a graphical overlay.
The lens 302 is activated by selection of a transportation network icon 330 (e.g., by a mouse click and hold or via an interactive touch screen) and overlaying the icon on a region of the graphical overlay 300 (e.g., by a mouse drag or via an interactive touch screen). The lens 302 thus corresponds to a transportation network, and is one of a plurality of networks accessible via a network selection panel 328. Other networks accessible via the network selection panel 328 include a water management network 334, a healthcare network 336, a public safety network 338, an energy network 340, a fire network 342, and a public services network 344. The networks shown as accessible via the network selection panel 328 are for illustrative purposes only, and may, in other embodiments, include networks not listed here. For example, the networks can include those shown in
Context visibility, which in some embodiments is equivalently used to describe context activation, within the lens 302 may be controlled by way of interactive icons 308, 312, 316. In some embodiments, as discussed further below, various contexts within the lens 302 are accessible by manipulation of the lens 302. As used herein, the term “manipulation of the lens” may include one or more of a variety of actions related to the lens 302 such as lens activation, interfacing with one or more of the interactive icons 308, 312, 316, lens translations (e.g., across the graphical overlay 300), and lens rotation, among others. As shown in
Activation of the transportation alerts/warnings context results in an icon 322 displayed within the lens 302 on the graphical overlay 300, where icon 322 corresponds to an area of traffic congestion. Within the framework of the various embodiments described herein, displaying a context within a lens is equivalently a visual representation of a context dataset obtained from at least one of the plurality of data sources as described above. Thus, as shown in
Visibility of various transportation network contexts within the lens 404 is controlled by way of interactive icons 408, 410, 412, and visibility of water management network contexts within the second lens 414 is controlled by way of interactive icons 418, 422. As shown in
As an example, consider that both the road maintenance records/schedule context (represented by icon 408) and the transportation alerts/warnings context (represented by icon 410) are activated, as described with reference to
Visibility of various transportation network contexts within the lens 504 is controlled by way of interactive icons 508, 510, 512, and visibility of water management network contexts within the second lens 514 is controlled by way of interactive icons 518, 522. Activation of at least one of the transportation network contexts results in the at least one activated transportation network context being displayed within the first lens 504, as indicated by arrow 526, and activation of at least one of the water management network contexts results in the at least one activated water management network context being displayed within the second lens 514, as indicated by arrow 527. By way of example, consider that both a road maintenance records/schedule context (represented by icon 508) and a transportation alerts/warnings context (represented by icon 510) are activated, resulting in icons 530 and 528 displayed within the first lens 504 on the graphical overlay 500. Also, consider that both the water pipe maintenance records/schedule context (represented by icon 518) and the water management alerts/warnings context (represented by icon 522) are activated, resulting in icons 532 and 534 displayed within the second lens 514 on the graphical overlay 500. Although the first lens 504 and the second lens 514 are in a partially overlapping spatial relation to one another, as compared to the fully overlapping spatial relation shown in
Visibility of various transportation network contexts within the lens 604 is controlled by way of interactive icons 608, 610, 612, and visibility of water management network contexts within the lens 614 is controlled by way of interactive icons 618, 622. Activation of at least one of the transportation network contexts results in the at least one activated transportation network context being displayed within the first lens 604, as indicated by arrow 627, and activation of at least one of the water management network contexts results in the at least one activated water management network context being displayed within the second lens 614, as indicated by arrow 626. In the example of
The at least one transportation network context displayed throughout the entire graphical overlay 700 may be activated by default upon selection of a transportation network icon 738, or the at least one transportation network context may be user-activated. Additionally, throughout the various embodiments described herein, one or more lenses can be activated by an external event trigger. Similarly, one or more domain contexts may be activated by an external event trigger such that an already active lens is populated with data and/or icons corresponding to the externally triggered domain context. Returning to
While the above discussion related primarily to embodiments for displaying data (e.g., from one or more of a plurality of data sources) geospatially, the following discussion relates primarily to embodiments useful for rapidly visualizing and comprehending complex, layered datasets, from one or more of a plurality of data sources, by providing a method for visually navigating data in a graphical overlay. Moreover, various embodiments facilitate manipulation of visualized data in a unique way which allows for better separation and uniting (e.g., visually) of causal factors (e.g., as discussed with reference to
In some embodiments, the lens 804, and thus lenses 802 and 806, correspond to a first network and includes at least one first context. The first network may include one of a plurality of networks accessible via the operations environment 200 (
Consider, for example, that lens 804, and thus lenses 802 and 806, correspond to a transportation network. As discussed above, for example with reference to
Continuing with the example of a transportation network, consider that a road maintenance record/schedule context has been activated within the lens 804, and thus also within lenses 802 and 806, which all represent the same lens which have been oriented in different rotational positions. As a result of activating the road maintenance records/schedules context, a first dataset corresponding to the road maintenance records/schedules context is displayed within the lens 804, which is oriented in the first position, as represented by icons 810/812. In some embodiments, a rotational position may be associated with specific points in time, and the first position may correspond to a first point in time. Also, the first dataset corresponding to the road maintenance records/schedules context represents the first dataset at the first point in time. Thus, for example, the first dataset displayed within the lens 804 (represented by icons 810/812) may represent areas of roadway that are undergoing maintenance and/or repair within a current time-frame. As used herein, the term “current time-frame” may include the present time and/or a particular window of time (e.g., happening now, within the last 24 hours, etc.) that also includes the present time. The current time-frame may be pre-defined and/or be user-defined.
As discussed above, the lens 804 may be rotated in a clockwise direction, as represented by lens 806 and indicated by arrow 816, to a second position indicated by bezel 818. In embodiments where a rotational position is associated with specific points in time, the second position, indicated by bezel 818, may correspond to a second point in time occurring after the first point in time, indicated by bezel 808. Thus, rotation of the lens 804 in the clockwise direction results in retrieval of a corresponding later-in-time version of the first dataset corresponding to the second position, as represented by icon 824, where the later-in-time version of the first dataset is a projected dataset. Therefore, in some embodiments, the later-in-time version of the first dataset (i.e., the projected data) displayed within the lens 806 (represented by icon 824) represents areas of roadway that are scheduled to undergo maintenance and/or repair at a future time (i.e., after the current time-frame).
Similarly, the lens 804 may be rotated in a counter-clockwise direction, as represented by lens 802 and indicated by arrow 820, to a second position indicated by bezel 822. In embodiments where a rotational position is associated with specific points in time, the second position, indicated by bezel 822, may correspond to a second point in time occurring before the first point in time, indicated by bezel 808. Thus, rotation of the lens 804 in the counter-clockwise direction results in retrieval of a corresponding earlier-in-time version of the first dataset corresponding to the second position, as represented by icons 826/828/830, where the earlier-in-time version of the first dataset is a historical dataset. For example, in some embodiments, the earlier-in-time version of the first dataset (i.e., the historical data) displayed within the lens 802 (represented by icons 826/828/830) represents areas of roadway that have previously undergone maintenance and/or repair (i.e., before the current time-frame).
As discussed above, lens rotation results in reconfiguration of the first dataset to provide a modified first dataset (e.g., an earlier-in-time and/or later-in-time version of the first dataset). Further, as used herein, reconfiguration of the first dataset by way of lens rotation (i.e., by way of manipulation of the lens) may be equivalently referred to as “cycling” of the first dataset. In some embodiments, for example in the case of two or more stacked lenses, “cycling” may also refer to stepping through individual datasets corresponding to each of the stacked lenses, as discussed in more detail with reference to
While
As shown in the example of
Also, the ellipsis 1037 is shown to indicate additional steps that may be inserted into the sequence of events represented by method 1000, for example, by the addition of additional rotational positions, among others. Moreover, while the method 1000 discussed herein illustrates an example of navigating datasets across a plurality of networks, it will be readily understood that the embodiments discussed above related to
Furthermore, in other embodiments, method 1000 may represent cycling through a plurality of context datasets of the same network by way of rotation of an individual lens. For example, consider an example where all the lenses shown in method 1000 represent the same lens which is simply oriented in various positions. Thus, taking the example of a transportation network, lens rotation as described above with reference to method 1000 may result in cycling through individual contexts such as a road maintenance records/schedule context (e.g., represented by data 1005), a transportation alerts/warnings context (e.g., represented by data 1007/1009), as well as others. Moreover, in all embodiments which include two or more stacked lenses described herein and with reference to methods 1000/1020/1040 of
Also, the ellipsis 1077 is shown to indicate additional steps that may be inserted into the sequence of events represented by method 1020, for example, by the addition of additional rotational positions, among others. Moreover, while the method 1020 discussed herein illustrates an example of navigating datasets across a plurality of networks, it will be readily understood that the embodiments discussed above related to
Furthermore, in other embodiments, method 1020 may represent cycling through and stacking (i.e., layering) a plurality of context datasets of the same network by way of rotation of an individual lens. For example, consider an example where all the lenses shown in method 1020 represent the same lens which is simply oriented in various positions. Thus, taking the example of a transportation network, lens rotation as described above with reference to method 1020 may result in cycling through and stacking (i.e., layering) individual contexts such as a road maintenance records/schedule context (e.g., represented by data 1045), a transportation alerts/warnings context (e.g., represented by data 1047/1049), as well as others.
From the position indicated by bezel 1086, the lens 1046 is rotated (e.g., by way of bezel 1086) in a direction indicated by arrow 1088 to another position indicated by bezel 1090 of lens 1048. In some embodiments, rotation to the position indicated by bezel 1090 results in stacking (i.e., layering) of the context datasets associated with the networks related to lenses 1046, 1048. Moreover, rotation to the position indicated by bezel 1090 results in displaying the context dataset associated with the network related to lens 1048 (i.e., data 1066/1068/1070) and ghosted images 1074/1076 of the context dataset associated with the network related to lens 1046 (i.e., data 1062/1064). From the position indicated by bezel 1090, the lens 1048 is rotated (e.g., by way of bezel 1090) in a direction indicated by arrow 1092 to another position indicated by bezel 1094 (e.g., equivalent to the position indicated by bezel 1017) of the plurality of stacked lenses 1050, (representing the stacking of lenses 1044, 1046, 1048), where the plurality of context datasets related to all lenses are again revealed, without further ghosted images. Thus, similar to the plurality of stacked lenses 1042, the plurality of stacked lenses 1050 includes the plurality of data 1060, 1062, 1064, 1066, 1068, 1070 corresponding to the plurality of networks associated with all of the stacked lenses 1044, 1046, 1048.
In addition, the ellipsis 1098 is shown to indicate additional steps that may be inserted into the sequence of events represented by method 1040, for example, by the addition of additional rotational positions, among others. Moreover, while the method 1040 discussed herein illustrates an example of navigating datasets across a plurality of networks, it will be readily understood that the embodiments discussed above related to
Furthermore, in other embodiments, method 1040 may represent cycling through and stacking (i.e., layering) a plurality of context datasets, including a ghosting effect, of the same network by way of rotation of an individual lens. For example, consider an example where all the lenses shown in method 1040 represent the same lens which is simply oriented in various positions. Thus, taking the example of a transportation network, lens rotation as described above with reference to method 1040 may result in cycling through and stacking (i.e., layering) individual contexts, such as a road maintenance records/schedule context (e.g., represented by data 1062/1064), and a ghosted image of a transportation alerts/warnings context (e.g., represented by data 1072), as well as others.
The various embodiments described above, and including the discussion of the flow charts below, collectively simplify and visualize the data mining process, and provide an intuitive and simple interface to visualize a plurality of data sources in such a way that users of all skill levels, from a layman to an expert user, are able to quickly understand the visualized data and thus more easily predict, and fix problems. For example, the embodiments described herein further provide the ability to visualize data sources both internal and external to any particular network within which a user is working. Moreover, the various embodiments provide the ability to manipulate the visualization of data in a unique way which allows for better separation and uniting (i.e., visually) of causal factors.
Method 1100 starts with the display of a graphical overlay, such as the graphical overlay 700 having a plurality of streets, on a spatial rendering of data (block 1102). A first lens 714 corresponding to a first network, and including at least one first context, is overlaid on a first region of the graphical overlay 700 (block 1104). The at least one first context is accessible by manipulation of the first lens. In some embodiments, the first network corresponds to one of a water network, a public safety network, a sewer network, a transportation network, a social services network, an emergency management network, and an energy network. The at least one first context is activated (block 1106), for example, by way of interactive icons 718, 722. However, in some embodiments, a default context for each lens is already active, thus no initial explicit context activation is necessary unless an alternative, non-default context, is required. Activation of the at least one first context, whether such activation is by default or by explicit user activation, results in obtaining a first dataset corresponding to the first context from at least one of a plurality of data sources (block 1108). In various embodiments, the one of the plurality of data sources includes at least one of a semantic model, a set of historical data, a set of projected data, a user input, web content, streaming content, a local database, and a remote database, among others. The first dataset is displayed within the first lens 714 (block 1110). Moreover, the displayed first dataset is a visual representation of a first context dataset obtained from the at least one of the plurality of data sources. At least one second context is activated (block 1112). Thereafter, a second dataset corresponding to the second context is obtained from the at least one of the plurality of data sources, and the second dataset is displayed throughout the entire graphical overlay, while simultaneously displaying the first dataset within the first lens (block 1114). The displayed second dataset is a visual representation of a second context dataset obtained from the at least one of the plurality of data sources. In the method 1100, regardless of the region on which the first lens 714 is overlaid, the first lens 714 (and thus the at least one first context) and the at least one second context are in a fully overlapping spatial relation to each other.
Method 1200 starts with the display of a graphical overlay, such as the graphical overlay 400 having a plurality of streets, on a spatial rendering of data (block 1202). A first lens 404 corresponding to a first network, and including at least one first context, is overlaid on a first region of the graphical overlay 400 (block 1204). The at least one first context is activated within the first lens, and a first dataset, which corresponds to the first context, is obtained from at least one of a plurality of data sources. A second lens 414 corresponding to a second network, and including at least one second context, is overlaid on a second region of the graphical overlay 400 (block 1206). The at least one second context is accessible by manipulation of the second lens. In various embodiments, the spatial relation between the first and second lenses 404, 414 includes one of a non-overlapping relation, a partially overlapping relation, and a fully overlapping relation. The at least one second context is activated within the second lens 414 (block 1208). Responsive to activating the at least one second context, a second dataset corresponding to the second context is obtained from the at least one of a plurality of data sources (block 1210). Thereafter, the second dataset is displayed within the second lens, while simultaneously displaying the first dataset within the first lens (block 1212). The displayed second dataset is a visual representation of a second context dataset obtained from the at least one of the plurality of data sources. By simultaneously displaying the visual representations of the first and second context datasets, and if the first and second lenses are in one of a partially overlapping and a fully overlapping relation, a correlation between the first and second datasets can be determined (block 1214), for example according to one of an inference engine determination and a determination according to a set of rules. As a result of identifying such correlations, well-informed decisions can be made regarding the management and operations of the affected networks within the city and/or region represented by the graphical overlay 400 (i.e., the operations environment).
Method 1300 starts with the overlay of a first lens on a graphical overlay (block 1302), which includes a spatial rendering of data including one of a geospatial map, a logical map, and a system map. The first lens includes a first context and a first dataset corresponding to the first context. The first lens is oriented in a first position. In some embodiments, the first network corresponds to one of a water network, a public safety network, a sewer network, a transportation network, a social services network, an emergency management network, and an energy network. An option to monitor temporal changes within the data (i.e., navigate time) is presented (decision block 1304). In some embodiments, if temporal changes are not monitored, then the first dataset is displayed within the first lens (block 1306). Further, the first dataset corresponds to the first position. The first lens is rotated around an axis of rotation until the first lens is oriented in a second position (block 1308). In response to rotating the first lens around the axis of rotation, the first dataset is reconfigured to provide a modified first dataset (block 1310). An option to activate ghosting of the data is presented (decision block 1314). In some embodiments, if ghosting is not activated, the modified first dataset is displayed within the first lens (block 1318). Moreover, the modified first dataset corresponds to the second position. In other embodiments, if ghosting is activated, the modified first dataset corresponding to the second position, and a ghosted image of the first dataset corresponding to the first position are simultaneously displayed (block 1320), for example in the first lens. In other embodiments, if temporal changes are monitored, a rotational position of the first lens is associated with specific points in time (block 1312). For example, the first position may correspond to a first point in time and the first dataset represents the first dataset at the first point in time. One of two lens rotation directions is selected (block 1316). In some embodiments, the first lens is rotated in a first direction (e.g., a clockwise direction) around the axis of rotation to a second position that corresponds to a second point in time which occurs after the first point in time, and where a corresponding later-in-time version of the first dataset is displayed (block 1322). In some embodiments, the later-in-time version of the first dataset is a projected dataset. In other embodiments, the first lens is rotated in a second direction (e.g., a counter-clockwise direction) around the axis of rotation to a second position that corresponds to a second point in time which occurs before the first point in time, and where a corresponding earlier-in-time version of the first dataset is displayed (block 1324). In some embodiments, the earlier-in-time version of the first dataset is a historical dataset.
Method 1400 starts with the overlay of a first lens on a graphical overlay (block 1402), which includes a spatial rendering of data including one of a geospatial map, a logical map, and a system map. A first dataset is displayed within the first lens. An option to modify a displayed context aspect is presented (decision block 1404). In some embodiments, the displayed context aspect is changed, and a rotational position of the first lens is associated with a first aspect of the at least one context, where the first dataset corresponds to the first aspect of the at least one context (block 1408). In response to rotation of the first lens around the axis of rotation to a second rotational position, a modified first dataset is displayed within the first lens (block 1410). Moreover, the modified first dataset corresponds to a second aspect of the at least one context. In other embodiments, the displayed context aspect is not changed, and a second lens is overlaid on the graphical overlay (block 1406). The first lens and the second lens are in a fully overlapping relation to each other, and a second dataset is displayed within the second lens, while simultaneously displaying the first dataset within the first lens. Also, a first region of the graphical overlay is circumscribed within each of the first lens and the second lens. Thereafter, an option to either modify a displayed context aspect of the first and/or second lens, or to pull apart (i.e., to separate) the first and second lenses is presented (block 1412). In some embodiments, when a displayed context aspect of one or both of the first and second lenses is to be changed, the method 1400 returns to associate a lens rotational position with a first aspect (block 1408), and rotation of either one or both of the first and second lenses to a second rotational position results in displaying a modified dataset that corresponds to a second context aspect (block 1410). In other embodiments, the first and second lens are separated (block 1414), for example to allow for investigation of the circumscribed first region through inspection of a single network (i.e., a single lens), and the first and second lenses are thus in one of a partially overlapping and non-overlapping spatial relationship. Separation of the first and second lenses results in simultaneous preservation of the first circumscribed region of the graphical overlay (i.e., a first region of a geospatial map) within each of the first and second lenses (block 1416). In addition, in some embodiments, any non-circumscribed region of the graphical overlay may be concealed. After separation of the first and second lenses, the first dataset is displayed within the first lens and second dataset is displayed within the second lens, for example, while the first and second lens are in one of a partially overlapping and non-overlapping spatial relationship.
In each of the flow charts above, one or more of the methods may be embodied in a computer readable medium containing computer readable code such that a series of steps are performed when the computer readable code is executed on a computing device. In some implementations, certain steps of the methods are combined, performed simultaneously or in a different order, or perhaps omitted, without deviating from the spirit and scope of the disclosure. Thus, while the method steps are described and illustrated in a particular sequence, use of a specific sequence of steps is not meant to imply any limitations on the disclosure. Changes may be made with regards to the sequence of steps without departing from the spirit or scope of the present disclosure. Use of a particular sequence is therefore, not to be taken in a limiting sense, and the scope of the present disclosure is defined only by the appended claims.
As will be appreciated by one skilled in the art, aspects of the present disclosure may be embodied as a system, method or computer program product. Accordingly, aspects of the present disclosure may take the form of an entirely hardware embodiment or an embodiment combining software (including, for example, firmware, resident software, micro-code, etc.) and hardware aspects that may all generally be referred to herein as a “circuit,” “module” or “system.” Furthermore, aspects of the present disclosure may take the form of a computer program product embodied in one or more computer readable storage devices or other computer readable medium(s) having computer readable program code embodied thereon.
Any combination of one or more computer readable medium(s) may be utilized. The computer readable medium may be a computer readable signal medium or a computer readable storage device. A computer readable storage device may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage device would include the following: a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage device may be any tangible medium that can contain or store a program for use by or in connection with an instruction execution system, apparatus, or device.
A computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may be any computer readable medium that is not a computer readable storage device and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.
Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, R.F, etc., or any suitable combination of the foregoing. Computer program code for carrying out operations for aspects of the present disclosure may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C++ or the like and conventional procedural programming languages, such as the “C” programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).
Aspects of the present disclosure are described below with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the disclosure. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
These computer program instructions can configure a computer, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions stored in the computer readable medium produce an article of manufacture including instructions which implement the function/act specified in the flowchart and/or block diagram block or blocks. The computer program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide processes for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
The article of manufacture containing the programming code is used by either executing the code directly from the storage device, by copying the code from the storage device into another storage device such as a hard disk, RAM, etc., or by transmitting the code for remote execution using transmission type media such as digital and analog communication links. The methods of the disclosure may be practiced by combining one or more machine-readable storage devices containing the code according to the present disclosure with appropriate processing hardware to execute the code contained therein. An apparatus for practicing the disclosure could be one or more processing devices and storage systems containing or having network access to program(s) coded in accordance with the disclosure.
Thus, it is important that while an illustrative embodiment of the present disclosure is described in the context of a fully functional computer (server) system with installed (or executed) software, those skilled in the art will appreciate that the software aspects of an illustrative embodiment of the present disclosure are capable of being distributed as a program product in a variety of forms, and that an illustrative embodiment of the present disclosure applies equally regardless of the particular type of media used to actually carry out the distribution.
While the disclosure has been described with reference to exemplary embodiments, it will be understood by those skilled in the art that various changes may be made and equivalents may be substituted for elements thereof without departing from the scope of the disclosure. In addition, many modifications may be made to adapt a particular system, device or component thereof to the teachings of the disclosure without departing from the essential scope thereof. Therefore, it is intended that the disclosure not be limited to the particular embodiments disclosed for carrying out this disclosure, but that the disclosure will include all embodiments falling within the scope of the appended claims. Moreover, the use of the terms first, second, etc. do not denote any order or importance, but rather the terms first, second, etc. are used to distinguish one element from another.
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
The corresponding structures, materials, acts, and equivalents of all means or step plus function elements in the claims below are intended to include any structure, material, or act for performing the function in combination with other claimed elements as specifically claimed. The description of the present disclosure has been presented for purposes of illustration and description, but is not intended to be exhaustive or limited to the disclosure in the form disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the disclosure. The embodiment was chosen and described in order to best explain the principles of the disclosure and the practical application, and to enable others of ordinary skill in the art to understand the disclosure for various embodiments with various modifications as are suited to the particular use contemplated.
While particular embodiments of the present disclosure have been shown and described, it will be obvious to those skilled in the art that, based upon the teachings herein, changes and modifications may be made without departing from this disclosure and its broader aspects. Consequently, the appended claims are to encompass within their scope all such changes and modifications as are within the true spirit and scope of this disclosure and embodiments of the disclosure are intended to be limited only by the scope of the appended claims, giving full cognizance to equivalents in all respects.
The present application is a continuation of U.S. patent application Ser. No. 14/472,676, titled “PRESENTING A DATA IN A GRAPHICAL OVERLAY,” filed on Aug. 29, 2014, the contents of which is incorporated herein by reference in its entirety.
| Number | Date | Country | |
|---|---|---|---|
| Parent | 14472676 | Aug 2014 | US |
| Child | 15165952 | US |
