Representation of overlapping visual entities

RELATED APPLICATION

0001This application is a continuation of and claims priority to U.S. application Ser. No. 12/764,798, filed on Apr. 21, 2010, and entitled “Representation of Overlapping Visual Entities,” the disclosure of which is incorporated in its entirety by reference herein.

BACKGROUND

0002Due to the massive amount of data available for consumption in today's electronic environment, data visualization can be problematic. For example, a mapping application can have access to a multitude of locations (e.g., restaurants, banks, hotels, parks, and so on) that can be displayed as part of a map view. The sheer number of locations available for display, however, can cause a particular map view to become cluttered and reduce the usability of the map view.

SUMMARY

0003This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter.

0004Various embodiments present a combined visual entity that represents overlapping visual entities. The combined visual entity can include a primary visualization that represents one of the overlapping visual entities and annotations that represent others of the overlapping visual entities. For example, a map view can include multiple geographical entities that overlap. A primary visualization can be rendered that represents one of the multiple geographical entities. The primary visualization can be visually annotated (e.g., with symbols, letters, or other visual indicators) to indicate others of the multiple geographical entities. In some embodiments, a zoom operation can cause visual entities to be added and/or removed from the combined visual entity.

0005In some embodiments, overlapping visual entities are grouped into a cluster that can be opened to reveal individual visual entities that form the cluster. According to one or more embodiments, a cluster is represented on a map by a visual representation known as a foundation. A user can interact with the foundation to cause the cluster to be opened to reveal a flyout that includes individual visual entities that form the cluster. In some embodiments, the visual entities can represent geographical locations in a map view. A user can also interact with an individual visual entity of the flyout to acquire more information about the visual entity.

BRIEF DESCRIPTION OF THE DRAWINGS

0006The same numbers are used throughout the drawings to reference like features.

0007<figref idref="DRAWINGS">FIG. 1</figref> illustrates an operating environment in which various principles described herein can be employed in accordance with one or more embodiments.

0008<figref idref="DRAWINGS">FIG. 2</figref> illustrates how a cluster of visual entities can be visualized in accordance with one or more embodiments.

0009<figref idref="DRAWINGS">FIG. 3</figref> illustrates how a foundation can be expanded to reveal a flyout in accordance with one or more embodiments.

0010<figref idref="DRAWINGS">FIG. 4</figref> illustrates how a foundation can be used to illustrate a cluster in a street view scenario in accordance with one or more embodiments.

0011<figref idref="DRAWINGS">FIG. 5</figref> illustrates how interaction with a flyout can cause information about a flyout entity to be presented in accordance with one or more embodiments.

0012<figref idref="DRAWINGS">FIG. 6</figref> illustrates how interaction with a flyout can cause information about a flyout entity to be presented in accordance with one or more embodiments.

0013<figref idref="DRAWINGS">FIG. 7</figref> is a flow diagram that describes steps in a method in accordance with one or more embodiments.

0014<figref idref="DRAWINGS">FIG. 8</figref> is a flow diagram that describes steps in a method in accordance with one or more embodiments.

0015<figref idref="DRAWINGS">FIG. 9</figref> is a flow diagram that describes steps in a method in accordance with one or more embodiments.

0016<figref idref="DRAWINGS">FIG. 10</figref> is a flow diagram that describes steps in a method in accordance with one or more embodiments.

0017<figref idref="DRAWINGS">FIG. 11</figref> is a flow diagram that describes steps in a method in accordance with one or more embodiments.

0018<figref idref="DRAWINGS">FIG. 12</figref> is a flow diagram that describes steps in a method in accordance with one or more embodiments.

0019<figref idref="DRAWINGS">FIG. 13</figref> illustrates how overlapping data sets can be visualized in accordance with one or more embodiments.

0020<figref idref="DRAWINGS">FIG. 14</figref> illustrates an example combined visual entity in accordance with one or more embodiments.

0021<figref idref="DRAWINGS">FIG. 15</figref> is a flow diagram that describes steps in a method in accordance with one or more embodiments.

0022<figref idref="DRAWINGS">FIG. 16</figref> is a flow diagram that describes steps in a method in accordance with one or more embodiments.

0023<figref idref="DRAWINGS">FIG. 17</figref> is a flow diagram that describes steps in a method in accordance with one or more embodiments.

0024<figref idref="DRAWINGS">FIG. 18</figref> illustrates an example system that can be used to implement one or more embodiments.

DETAILED DESCRIPTION

0025Overview

0026Various embodiments present a combined visual entity that represents overlapping visual entities. The combined visual entity can include a primary visualization that represents one of the overlapping visual entities and annotations that represent others of the overlapping visual entities. For example, a map view can include multiple geographical entities that overlap. A primary visualization can be rendered that represents one of the multiple geographical entities. The primary visualization can be visually annotated (e.g., with symbols, letters, or other visual indicators) to indicate others of the multiple geographical entities. In some embodiments, a zoom operation can cause visual entities to be added and/or removed from the combined visual entity.

0027In some embodiments, overlapping visual entities are grouped into a cluster that can be opened to reveal the individual visual entities that form the cluster. A visual entity can represent a data entity, such as a geographical location, a business, a residence, an instance of content, a data file, and so on. In some example operating scenarios, overlapping visual entities can represent geographical locations on a map that are combined to form a cluster, and the cluster can be opened to reveal the individual geographical locations that form the cluster. In at least some embodiments, the cluster can be opened independent of a zoom operation. According to one or more embodiments, a cluster is represented on a map by a visual representation known as a foundation. A user can interact with the foundation to cause the cluster to be opened to reveal a flyout that includes individual visual entities (e.g., geographic locations) that form the cluster. A user can also interact with an individual entity of the flyout to acquire more information about the entity. In at least some embodiments, user interaction can include hovering operations, proximity operations (e.g., user interaction within a certain proximity of a foundation or other entity), clicking operations, keyboard selection operations, touch operations, and the like.

0028In the discussion that follows, a section entitled “Operating Environment” is provided and describes one example environment in which one or more embodiments can be employed. Following this, a section entitled “Example Cluster Visualizations” describes how clusters of entities can be visualized in accordance with one or more embodiments. Next, a section entitled “Constructing and Interacting with Clusters” describes how a cluster can be formed and how a visualization of a cluster can be interacted with in accordance with one or more embodiments. Following this, a section entitled “Representation of Overlapping Visual Entities” describes how a combined visualization can be used to visually indicate overlapping data sets in accordance with one or more embodiments. Last, a section entitled “Example System” describes an example system that can be utilized to implement one or more embodiments.

0029Consider now an example operating environment in which one or more embodiments can be implemented.

0030Operating Environment

0031<figref idref="DRAWINGS">FIG. 1</figref> illustrates an operating environment in accordance with one or more embodiments, generally at <b>100</b>. Environment <b>100</b> includes a computing device <b>102</b> having one or more processors <b>104</b>, one or more computer-readable storage media <b>106</b> and one or more applications <b>108</b> that reside on the computer-readable storage media and which are executable by the processor(s). The computer-readable storage media can include, by way of example and not limitation, all forms of volatile and non-volatile memory and/or storage media that are typically associated with a computing device. Such media can include ROM, RAM, flash memory, hard disk, removable media and the like. One specific example of a computing device is shown and described below in <figref idref="DRAWINGS">FIG. 18</figref>.

0032In addition, computing device <b>102</b> includes a software application in the form of a web browser <b>110</b>. Any suitable web browser can be used examples of which are available from the assignee of this document and others. In addition, computer-readable storage media <b>106</b> can include a layer manager <b>112</b> and a cluster manager <b>114</b> that are configured to operate as described below. Each of layer manager <b>112</b> and cluster manager <b>114</b> can be implemented as a standalone component that can be utilized by applications <b>108</b> and/or browser <b>110</b>. Alternately or additionally, layer manager <b>112</b> and/or cluster manager <b>114</b> can be implemented as part of applications <b>108</b> and/or browser <b>110</b>. Examples of Applications <b>108</b> can include a mapping platform (e.g., utilizing 2D and/or 3D maps), an operating system, a file explorer, and so on.

0033In operation, layer manager <b>112</b> handles layers of data for the applications <b>108</b>. For example, a mapping application can include multiple layers of map data that can be used to populate a map view. Each of the multiple layers can include different types of entities and map data. For example, a first layer may include restaurants, a second layer may include educational institutions, a third layer may include locations defined by an end-user, and so on. In some embodiments, multiple layers can be overlaid, one on another, to create a particular map view. To manage layer data, layer manager <b>112</b> is configured to handle a variety of different tasks, such as tracking a location for a visual entity, maintaining different visual forms for a visual entity, managing the z-order (e.g., layer order) of different layers and/or visual entities, and so on.

0034In at least some embodiments, cluster manager <b>114</b> works in a mapping context to enable various visual entities to be grouped into a cluster. A visual entity can represent a data entity, such as a geographical location, an instance of media content, a data file, and the like. The cluster manager can group visual entities into a cluster by determining overlap between visual entities in a particular display region. When a particular group of visual entities overlap by at least a threshold amount, the group of visual entities can be formed into a cluster. Overlap can be measured using a variety of different metrics, such as screen pixels, world-coordinates (e.g., GPS coordinates, latitude, longitude, and so on), street addresses, and so on. Example ways of determining overlap are discussed below.

0035According to some embodiments, layer manager <b>112</b> and cluster manager <b>114</b> are configured to interact and communicate to group visual entities into clusters and to place visual entities and clusters in a particular display view. Layer manager <b>112</b> can provide cluster manager <b>114</b> with different types of information that can be used by the cluster manager to create and manage clusters. Examples of this information include:

0036Entity list: This is a list of visual entities and/or data entities in a particular system. For example, in a map scenario, this can include a list of geographic entities and visual representations of the geographic entities that are available to populate a map.

0037Visible entities: This is a list of the visual entities that are in a current view. For example, this may include geographical entities that are represented in a current map view.

0038Existing clusters: This is a list of clusters that are currently in existence.

0039Visual entities: This includes a location and dimension for each visual entity. For example, this information may include a location (e.g., in screen coordinates) and a dimension (e.g., in pixels relative to the screen coordinates) of a visual entity.

0040Z-order: This includes a z-order for visual entities, clusters, and/or layers in a particular system. For example, a particular visual entity can have a z-order that indicates that the entity is to be displayed above (e.g., occlude) other visual entities in a display view.

0041Entity status: This indicates changes in entity status for a particular render pass. For example, this information can indicate that an entity was added, removed, or changed z-order for a particular render pass. In some embodiments, the term “render pass” refers to a re-draw of entities in a display view. A render pass can occur responsive to changes in a display view, such as a zoom operation, the addition or removal of entities, a change in cluster membership, and so on.

0042Layer Membership: This indicates which entities belong to which layer and an order for each of the layers in a layer set.

0043In some embodiments, cluster manager <b>114</b> can receive some or all of this information from layer manager <b>112</b>, process the information, and generate further information that can be passed back to the layer manager to populate a particular display view. Examples of this further information can include:

0044(1) Updated entity list: This can include an updated list of entities (including cluster entities) and a list of entities that were removed from existing clusters.

0045(2) Entity layers: This can include a list of layers that include entities included in clusters.

0046(3) Cluster membership: This can include an indication of a cluster membership for an entity.

0047(4) Entity change: This can include an indication of visual entities and/or clusters that should be added or removed from a display view.

0048(5) Cluster z-order: This can include a z-order for entities in a particular cluster.

0049(6) Visual elements: This can include a visual representation to be used to represent a cluster. In some embodiments, each of multiple clusters can be associated with a unique visual representation.

0050In addition the above-mentioned features, environment <b>100</b> includes a network <b>116</b>, such as the Internet, and one or more web sites <b>118</b> from and to which content can be received and sent. Such content can include map content that can be operated upon by layer manager <b>112</b> and/or cluster manager <b>114</b>, as described above and below. It is to be appreciated and understood that the layer manager and/or the cluster manager can reside on a server or network-accessible computer, other than computing device <b>102</b>.

0051Computing device <b>102</b> can be embodied as any suitable computing device such as, by way of example and not limitation, a desktop computer, a portable computer, a handheld computer such as a personal digital assistant (PDA), cell phone, a mobile device, and the like.

0052Although not expressly illustrated in <figref idref="DRAWINGS">FIG. 1</figref>, environment <b>100</b> can include a plug-in framework (e.g., embodied on computing device <b>102</b>) that enables developers, programmers, and other parties to utilize the techniques and processes discussed herein in separate implementations.

0053Having described an example operating environment, consider now a discussion of example clusters in accordance with one or more embodiments.

0054Example Cluster Visualizations

0055<figref idref="DRAWINGS">FIG. 2</figref> illustrates one example way in which multiple overlapping visual entities can be visualized as a cluster in a mapping context in accordance with one or more embodiments. A map view <b>202</b> displays a group of visual entities and includes a map region <b>204</b>. A map view <b>206</b> illustrates a map view that is displayed after a zoom-out operation occurs on map view <b>202</b>. The map view <b>206</b> includes map region <b>204</b> as well as additional visual entities. As illustrated in map view <b>206</b>, the increase in the map scale resulting from the zoom-out operation has caused visual entities within map region <b>204</b> to be grouped together such that some visual entities visually occlude other visual entities.

0056Further illustrated in <figref idref="DRAWINGS">FIG. 2</figref> is a map view <b>208</b> that includes map region <b>204</b> and a foundation <b>210</b>. In accordance with some embodiments, foundation <b>210</b> is a visual representation of a cluster that is created using visual entities from map region <b>204</b>. Thus, the overlapping group of visual entities displayed in map region <b>204</b> of map view <b>206</b> can be replaced with foundation <b>210</b>. Foundation <b>210</b> can represent a unified visual representation that a user can interact with to view visual entities included in the cluster and to find out more information about the visual entities.

0057In some embodiments, a visualization for a foundation can be defined for an application by an application developer and/or the visualization can be selected by an end-user. Thus, at least in some embodiments, a visualization for a foundation is customizable to provide a unique visual appearance for a cluster.

0058<figref idref="DRAWINGS">FIG. 3</figref> illustrates one example way in which user interaction with a foundation can reveal visual entities that form a cluster in accordance with one or more embodiments. A map view <b>300</b> includes the foundation <b>210</b> discussed above with reference to <figref idref="DRAWINGS">FIG. 2</figref>. At a map view <b>302</b>, a user has placed a cursor over the foundation <b>210</b> (e.g., by manipulating the cursor with a mouse), which has caused a flyout <b>304</b> to replace foundation <b>210</b>. Flyout <b>304</b> includes visual entities that form the cluster represented by foundation <b>210</b>. As illustrated, the visual entities are tied together as part of flyout <b>304</b> by graphic lines, indicating that the visual entities represent clustered entities and that the visual entities may not be displayed at a correct location for an underlying data entity.

0059In some embodiments, a visualization for a flyout can be defined for an application by an application developer and/or the visualization can be selected by an end-user. Thus, at least in some embodiments, a flyout visualization is customizable to provide a unique visual appearance for visual entities in a cluster.

0060At a map view <b>306</b>, the user has moved the cursor away from flyout <b>304</b>, thus causing flyout <b>304</b> to be replaced with foundation <b>210</b>. Thus, in some embodiments, foundation <b>210</b> and flyout <b>304</b> have a dynamic relationship that responds to user interaction with the foundation and/or the flyout.

0061<figref idref="DRAWINGS">FIG. 4</figref> illustrates one example way of using a foundation to represent a cluster in a street view paradigm in accordance with one or more embodiments. As part of <figref idref="DRAWINGS">FIG. 4</figref> are a street view <b>400</b> and a foundation <b>402</b>. In some embodiments, street view <b>400</b> is a two-dimensional approximation of a three-dimensional view. For example, street view <b>400</b> can approximate the view of a person who is traveling (e.g., walking or driving) along a street. In the street view context, some visual entities can occlude other visual entities. For example, if several visual entities are located at the same address (e.g., in an office building), the visual entities can become cluttered and some of the visual entities can partially or totally occlude others. Thus, a foundation/flyout combination (represented by foundation <b>402</b>) can be used to represent a cluster of visual entities at a particular location in street view <b>400</b>.

0062In some embodiments, the design of a foundation and/or flyout can be configured to convey meaning in a particular context. For example, a visualization for a foundation can include a building at a particular location and an associated flyout can include a map of different locations within the building.

0063<figref idref="DRAWINGS">FIG. 5</figref> illustrates one example way of interacting with a foundation to view visual entities in a cluster in accordance with one or more embodiments. At <b>500</b>, a foundation <b>502</b> is illustrated. As discussed above and below, in some embodiments a foundation is a visual representation of clustered entities. At <b>504</b>, user interaction with foundation <b>502</b> causes an underlying cluster to open and reveal a flyout <b>506</b>. At <b>508</b>, user interaction with a visual entity <b>510</b> reveals information about visual entity <b>510</b>. In this particular example, the information is included in a popup window <b>512</b>.

0064At <b>514</b>, user interaction with the popup window <b>512</b> causes the popup window to expand and reveal further information about the visual entity <b>510</b>. In this particular example embodiment, the further information includes selectable links that can be selected to navigate to functionality associated with the represented entity.

0065<figref idref="DRAWINGS">FIG. 6</figref> illustrates an alternative embodiment of a foundation/flyout combination in accordance with one or more embodiments. At <b>600</b>, a foundation <b>602</b> is displayed that represents a cluster of visual entities. In this particular example embodiment, foundation <b>602</b> is annotated to indicate aspects of one or more of the visual entities of the underlying cluster. For example, foundation <b>602</b> includes an “R” which indicates that one of the entities is a restaurant, a “C” which indicates that one of the entities is a coffee shop, and a “P” which indicates that one of the entities is associated with parking.

0066At <b>604</b>, user interaction with foundation <b>602</b> causes a popup window <b>606</b> to be displayed. At <b>608</b>, a user interacts with the popup window <b>606</b>. According to some embodiments, user interaction with popup window <b>606</b> can include causing a cursor to hover over the popup window. At <b>610</b>, the user interaction with popup window <b>606</b> causes the popup window to expand to reveal more information about visual entities included in the cluster represented by foundation <b>602</b>. In this particular example embodiment, the information includes a scrollable list of business entities that are part of the cluster. At <b>612</b>, user interaction with one of the listed business entities causes popup window <b>606</b> to be populated with more information about the business entity.

0067Constructing and Interacting with Clusters

0068<figref idref="DRAWINGS">FIG. 7</figref> is a flow diagram that describes steps in a method in accordance with one or more embodiments. The method discussed with reference to <figref idref="DRAWINGS">FIG. 7</figref>, in addition to any other of the methods discussed herein, can be implemented in connection with any suitable hardware, software, firmware or combination thereof. In at least some embodiments, aspects of the methods discussed herein can be implemented by software modules, such as layer manager <b>112</b> and/or cluster manager <b>114</b> discussed in <figref idref="DRAWINGS">FIG. 1</figref>. It is to be appreciated and understood that the methods discussed herein can be performed by a suitably-configured server, a network-accessible computing device, and/or a client computing device.

0069Step <b>700</b> ascertains visual entities that are available in the system to be displayed. For example, in a mapping scenario, the visual entities can represent geographical locations that can occur in a particular map view. The visual entities can be stored at a local resource (e.g., computing device <b>102</b>) and/or available from a remote resource. Step <b>702</b> determines a location for each visual entity in the system. In some embodiments, the location may be in terms of screen location (e.g., screen coordinates), real-world location (e.g., GPS coordinates, street address, latitude/longitude coordinates, and so on), computer directory location, and so on. Step <b>704</b> determines that a group of visual entities forms a cluster. Example ways of performing step <b>704</b> are discussed in more detail below. Step <b>706</b> renders a visual representation of the cluster. Example visual representations of a cluster are discussed above (e.g., a foundation) and below.

0070According to some embodiments, a data entity can opt in or opt out of the clustering process. For example, when a particular data entity opts into the clustering process, a visual entity that represents the data entity will be considered when determining clusters. When a particular data entity opts out of the clustering process, however, a visual entity that represents the data entity will be omitted when determining clusters.

0071As an illustration of this notion, consider the following example implementation scenario involving a tourist attraction data entity. When the tourist attraction registers with a particular data layer (e.g., to be included in a map), the tourist attraction provides an indication that it is opting out of the clustering process. When the clustering process is performed for a map region where the tourist attraction occurs, the tourist attraction is not considered in forming a cluster. Thus, according to some embodiments, the clustering process would normally group a visual representation of the tourist attraction with other visual entities to form a cluster. Since the tourist attraction has opted out of the clustering process, however, a visual representation of tourist attraction is not included as part of a cluster, e.g., as part of a foundation. Thus, in some embodiments, a visual representation of the tourist attraction can be rendered separately from an adjacent foundation.

0072<figref idref="DRAWINGS">FIG. 8</figref> is a flow diagram that describes steps in a method in accordance with one or more embodiments. In some embodiments, the method can be implemented to form a cluster that includes multiple visual entities. Step <b>800</b> sorts visual entities to determine x-coordinate overlap. In some embodiments, a configurable x-coordinate threshold overlap can be specified that can be used to determine if two or more visual entities overlap such that they can be members of a cluster. For example, with respect to x-coordinate overlap, a threshold overlap of N pixels can be specified. When two or more visual entities overlap by N pixels or more as projected on an x-axis, the visual entities can be considered an x-pass group for purposes of a preliminary cluster determination. In some embodiments, the acts of sorting discussed above and below can be accomplished in linear time using a linear sort algorithm (e.g., Radix sort).

0073Step <b>802</b> determines x-pass groups based on collections of visual entities that exceed an x-coordinate overlap threshold. As illustrated in the projection from step <b>802</b>, the entities within box <b>804</b> and box <b>806</b> exceed an x-pass overlap threshold and thus are grouped as x-pass groups. Step <b>808</b> sorts the x-pass groups by y-coordinate overlap.

0074Step <b>810</b> forms clusters using x-pass groups that include collections of visual entities that exceed a y-coordinate overlap threshold. A configurable threshold y-coordinate overlap can be specified or the threshold x-coordinate overlap discussed above can be utilized in sorting the x-pass groups by y-coordinate overlap. As illustrated in the projection from step <b>810</b>, a cluster <b>812</b> and a cluster <b>814</b> have been formed as a result of step <b>810</b>.

0075In some embodiments, a maximum number of visual entities permitted in a cluster can be specified. For example, a maximum of 5 visual entities per cluster can be specified. If a cluster exceeds the maximum number of visual entities, the cluster can be broken up into separate clusters and/or visual entities can be removed from the cluster until it reaches the maximum size. Although not expressly illustrated in <figref idref="DRAWINGS">FIG. 8</figref>, a final step can be performed whereby clusters that exceed a maximum number of visual entities can be broken up into multiple clusters (e.g., two or more smaller clusters) and/or visual entities can be removed from a cluster that exceeds a maximum number of visual entities. In some embodiments, visual entities that are removed from a cluster can be displayed separately from a foundation.

0076<figref idref="DRAWINGS">FIG. 9</figref> is a flow diagram that describes steps in a method in accordance with one or more embodiments. In some embodiments, the method can be implemented to form a cluster that includes multiple geographic entities. Examples of geographic entities include street addresses, businesses, residential locations, and so on. Step <b>900</b> determines geographic coordinates for each geographic entity of a collection of geographic entities. Examples of geographic coordinates include latitude coordinates, longitude coordinates, GPS coordinates, and so on. Step <b>902</b> forms a cluster that includes geographic entities with matching geographic coordinates. One example way of performing step <b>902</b> is to compute a hash value using geographical coordinates for each geographic entity. For example, a one-pass linear bucketing of the geographical coordinates can be performed. Geographic entities with identical and/or similar hash values are then grouped together to form a cluster.

0077Step <b>904</b> renders a visual representation of the cluster. According to some embodiments, this method of forming clusters can be useful in a street view scenario (see, e.g., the discussion above with respect to <figref idref="DRAWINGS">FIG. 4</figref>) to form clusters using geographical entities that occur at the same or similar location (e.g., a particular street address).

0078The methods discussed herein for determining entity overlap and/or forming clusters are provided for purposes of example only and are not to be interpreted as limiting the claimed subject matter. It is to be appreciated that a variety of different methods and techniques can be utilized to form clusters without departing from the spirit and scope of the claimed embodiments. For example, some techniques can simply look at pixel occlusion, some can consider the shape of entities in forming a cluster (e.g., utilizing a shape collision detection algorithm), and so on.

0079While certain embodiments are discussed herein with respect to forming clusters based on entity overlap, some embodiments can additionally or alternatively form clusters utilizing entities that are like or similar in nature. For example, some clustering techniques can form clusters using similar entities, such as a restaurant cluster, a tourist attraction cluster, a coffee shop cluster, and so on. Thus, in some embodiments, a cluster-forming technique can consider the proximity and/or overlap of entities and can also consider the nature of each of the entities. For example, if two entities are of disparate types (e.g., one is a restaurant and the other is a sporting goods store), the two entities may not be included in the same cluster.

0080<figref idref="DRAWINGS">FIG. 10</figref> is a flow diagram that describes steps in a method in accordance with one or more embodiments. In some embodiments, the method can be implemented to cluster and/or de-cluster entities in response to a zoom operation. Step <b>1000</b> receives an indication of an initiation of a zoom level change. According to some embodiments, step <b>1000</b> can be performed responsive to user interaction with a zoom (e.g., zoom-in or zoom-out) function. Step <b>1002</b> ungroups visual entities that form a first cluster. In some embodiments, the first cluster can be ungrouped responsive to receiving the indication of the zoom level change. Step <b>1004</b> receives an indication of completion of the zoom level change. In some embodiments, the zoom level change can include a zoom-in and/or a zoom-out operation.

0081Step <b>1006</b> determines whether or not the visual entities form a cluster. Example ways of determining that visual entities form a cluster are discussed above and below. If the visual entities form a cluster (“Yes”), step <b>1008</b> renders a visual representation of a second cluster. In some embodiments, the second cluster may include the same visual entities as the first cluster, fewer visual entities than the first cluster, or more visual entities than the first cluster. If the visual entities do not form a cluster (“No”), step <b>1010</b> renders separate visual entities.

0082<figref idref="DRAWINGS">FIG. 11</figref> is a flow diagram that describes steps in a method in accordance with one or more embodiments. Step <b>1100</b> renders a foundation. In some embodiments, the foundation includes a visual representation of a cluster. Step <b>1102</b> receives an indication of a user interaction with the foundation. Examples of user interaction with a foundation are discussed above and below. Step <b>1104</b> renders a flyout. In some embodiments, a flyout can be rendered responsive to receiving the indication of the user interaction with the foundation and/or the flyout can replace the foundation in a display view. Step <b>1106</b> receives an indication of a focus shift away from the flyout. For example, a cursor that is hovered over the flyout can be moved away from the flyout. In some embodiments, and responsive to receiving the indication of the focus shift away from the flyout, the method can return to step <b>1100</b>.

0083<figref idref="DRAWINGS">FIG. 12</figref> is a flow diagram that describes steps in a method in accordance with one or more embodiments. In some embodiments, the method can be implemented to present information about a visual entity included in a cluster. Step <b>1200</b> renders a flyout. Step <b>1202</b> receives an indication of a user interaction with a visual entity included in the flyout. Examples of user interaction are discussed above and below. Step <b>1204</b> presents information about the visual entity responsive to receiving the indication of the user interaction.

0084A number of optional variations and additions to the methods and techniques discussed herein can be implemented to account for various operating scenarios. The following is a non-exclusive list of example optional variations and additions.

0085(1) The determination of visual entities to include in a cluster can be made using visual entities that are included in a display view during a current render pass.

0086(2) When a z-order for a visual entity or a cluster changes during a render pass, the z-order in existing clusters simply needs to be updated.

0087(3) When a change during a render pass simply involves the addition of a visual entity, determine if there is overlap of the added visual entity with existing visual entities.

0088(4) When a change during a render pass simply involves a zoom operation, re-cluster using existing clusters.

0089(5) For a particular render pass, simply re-render a cluster (e.g., a foundation) if its entity set has changed.

0090(6) Locate and remove any duplicate visual entities. For example, if multiple map entries are created for a single business entity, all but one of the entries can be removed from the system.

0091While certain embodiments are discussed herein with reference to utilizing a flyout to disambiguate clustered entities, this is not intended to be limiting. In some embodiments, a user interaction with a foundation can cause a zoom-in operation that reveals individual entities included in a cluster. For example, when a user interacts with a foundation included as part of a display view, the display view can automatically zoom-in on the area of the foundation such that the visual entities represented by the foundation no longer overlap and are displayed as separate visual entities.

0092Alternatively or additionally, in some embodiments user interaction with a foundation can cause a list of entities represented by the foundation to be presented. For example, when a user interacts with a foundation included as part of a display view, a list of entities represented by the foundation can be displayed in a window that is included as part of or is adjacent to the display view.

0093Having described example ways of constructing and interacting with clusters, consider now various embodiments that illustrate example ways of using annotations to indicate overlapping data sets.

0094Representation of Overlapping Visual Entities

0095In at least some embodiments, overlapping visual entities can be represented via a combined visual entity. In some example scenarios, overlapping visual entities can be associated with multiple data sets that can be layered to create a display view. For example, as discussed above with respect to a mapping scenario, multiple layers of map data can be overlaid to generate a particular map view. To aid in visualizing multiple layered data sets, annotations for visual entities can be utilized.

0096<figref idref="DRAWINGS">FIG. 13</figref> illustrates one example implementation of using annotations to visualize multiple layers of data sets according to some embodiments. A first layer view which includes multiple visual entities is illustrated generally at <b>1300</b>. In this particular example, first layer view <b>1300</b> includes multiple visual entities that represent restaurants in a particular geographical area, as illustrated by the “R” icons. A second layer view is illustrated generally at <b>1302</b> and includes multiple visual entities that are different from those illustrated in first layer view <b>1300</b>. In this particular example, second layer view <b>1302</b> includes multiple visual entities that represent business entities that accept a particular payment method (e.g., a particular credit card), as illustrated by the “$” icons. An overlapping layer view is illustrated generally at <b>1304</b> and includes visual entities from first layer view <b>1300</b> and second layer view <b>1302</b>, as well as combined visual entities that represent overlap between the layer views. For example, a combined visual entity <b>1306</b> represents overlap between first layer view <b>1300</b> and second layer view <b>1302</b>. In some embodiments, combined visual entity <b>1306</b> represents a restaurant that accepts the particular payment method indicated by the “$” symbol. In this particular example embodiment, the visual entity that represents a restaurant is annotated with the “$” symbol to indicate overlap between the different layers.

0097In at least some embodiments, methods discussed above for forming clusters can be utilized to determine when annotations should be used to indicate overlapping data sets. For example, the technique discussed above with respect to <figref idref="DRAWINGS">FIG. 8</figref> can be utilized to determine that visual entities associated with multiple different data sets overlap. A visual entity can be displayed with annotations to indicate the overlap of the multiple visual entities.

0098In some embodiments, a combined visual entity can include a foundation. For example, a foundation can be displayed with annotations to visually indicate that multiple visual entities (e.g., in multiple data layers) overlap. Responsive to a user interaction with the annotated foundation, a flyout can be presented that displays the separate visual entities that are represented by the annotated foundation.

0099<figref idref="DRAWINGS">FIG. 14</figref> displays an example combined visual entity in accordance with some embodiments, generally at <b>1400</b>. Combined visual entity <b>1400</b> includes a primary visualization <b>1402</b> and annotations <b>1404</b>, <b>1406</b>, and <b>1408</b>. In this particular example embodiment, primary visualization <b>1402</b> represents a business entity associated with lodging. The annotations represent other data layers that overlap with the primary visualization <b>1402</b>. For example, annotation <b>1404</b> represent a coffee shop, annotation <b>1406</b> represents an entity that accepts a particular payment method, and annotation <b>1408</b> represents a dining establishment. Thus, combined visual entity <b>1400</b> presents a visual indication of an overlap between these particular data sets.

0100Alternatively or additionally to the symbol and/or character-based annotation of a combined visually entity, color can also be used as a visual indicator for a combined visual entity. For example, a particular color can be associated with a particular overlap of visual entities and/or data layers and can indicate to a viewer that the combined visual entity represents the particular visual entities.

0101<figref idref="DRAWINGS">FIG. 15</figref> is a flow diagram that describes steps in a method in accordance with one or more embodiments. In some embodiments, the method can be implemented to register visualizations that can be used to indicate overlapping data sets. Step <b>1500</b> registers a default visualization for a visual entity. According to some embodiments, the default visualization can be used when the visual entity is a primary visualization for a particular region of a display view. Step <b>1502</b> registers an annotation for the visual entity. In some embodiments, the annotation can be used to annotate a primary visualization for a different visual entity to indicate overlap between the visual entity and the different visual entity.

0102<figref idref="DRAWINGS">FIG. 16</figref> is a flow diagram that describes steps in a method in accordance with one or more embodiments. As discussed above, in some embodiments visual entities may be associated with different layers of data. Thus, at least in some embodiments the method can be utilized to render a combined visual representation of entities from multiple different data layers. Step <b>1600</b> ascertains a position for each visual entity to be rendered. As discussed above, in some embodiments the position can be in terms of a screen position (e.g., an x-coordinate, a y-coordinate, and so on), geographical coordinates, and so on. Step <b>1602</b> determines that multiple visual entities overlap. Step <b>1604</b> retrieves a visualization for each of the overlapping visual entities. The visualization for each entity can be a primary visualization and/or an annotation. Step <b>1606</b> renders a combined visual entity that includes visualizations for the multiple overlapping visual entities. In some embodiments, the combined visual entity can include a primary visualization for one of the overlapping visual entities and one or more annotations for others of the overlapping visual entities.

0103<figref idref="DRAWINGS">FIG. 17</figref> is a flow diagram that describes steps in a method in accordance with one or more embodiments. Step <b>1700</b> determines that multiple visual entities overlap. Step <b>1702</b> renders a combined visual entity that includes visualizations for the multiple overlapping visual entities. In some embodiments, the combined visual entity can include a primary visualization and one or more annotations.

0104Step <b>1704</b> receives an indication of a zoom-in operation. In at least some embodiments, the zoom-in operation can occur responsive to user interaction with an application such as a mapping application. Step <b>1706</b> determines that a visual entity of the multiple overlapping visual entities no longer overlaps. Step <b>1708</b> removes the visual entity from the combined visual entity. In some embodiments, this step can include removing an annotation from the combined visual entity or replacing a primary visualization associated with the combined visual entity.

0105While several of the example embodiments discussed herein are discussed with respect to a map implementation, it is to be appreciated that methods, techniques, and visualizations discussed herein can be applied in other scenarios without departing from the spirit and scope of the claimed embodiments. For example, clusters can be formed that represent groups of data files, instances of media content, flow charts, schematics, groups of persons at a particular location, and/or other entities to which the methods, techniques, and visualizations discussed herein can be applied.

0106Example System

0107<figref idref="DRAWINGS">FIG. 18</figref> illustrates an example computing device <b>1800</b> that can be used to implement the various embodiments described above. Computing device <b>1800</b> can be, for example, computing device <b>102</b> of <figref idref="DRAWINGS">FIG. 1</figref> or any other suitable computing device.

0108Computing device <b>1800</b> includes one or more processors or processing units <b>1802</b>, one or more memory and/or storage components <b>1804</b>, one or more input/output (I/O) devices <b>1806</b>, and a bus <b>1808</b> that allows the various components and devices to communicate with one another. Bus <b>1808</b> represents one or more of any of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, and a processor or local bus using any of a variety of bus architectures. Bus <b>1808</b> can include wired and/or wireless buses.

0109Memory/storage component <b>1804</b> represents one or more computer storage media. Component <b>1804</b> can include volatile media (such as random access memory (RAM)) and/or nonvolatile media (such as read only memory (ROM), Flash memory, optical disks, magnetic disks, and so forth). Component <b>1804</b> can include fixed media (e.g., RAM, ROM, a fixed hard drive, etc.) as well as removable media (e.g., a Flash memory drive, a removable hard drive, an optical disk, and so forth).

0110One or more input/output devices <b>1806</b> allow a user to enter commands and information to computing device <b>1800</b>, and also allow information to be presented to the user and/or other components or devices. Examples of input devices include a keyboard, a cursor control device (e.g., a mouse), a microphone, a scanner, and so forth. Examples of output devices include a display device (e.g., a monitor or projector), speakers, a printer, a network card, and so forth.

0111Various techniques may be described herein in the general context of software or program modules. Generally, software includes routines, programs, objects, components, data structures, and so forth that perform particular tasks or implement particular abstract data types. An implementation of these modules and techniques may be stored on or transmitted across some form of computer readable media. Computer readable media can be any available medium or media that can be accessed by a computing device. By way of example, and not limitation, computer readable media may comprise “computer-readable storage media”.

0112“Computer-readable storage media” include volatile and non-volatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules, or other data. Computer-readable storage media include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by a computer. Thus, whereas computer readable media may include signals per se, computer-readable storage media does not include signals per se.

0113Conclusion

0114Various embodiments enable overlapping visual entities to be grouped into a cluster that can be opened to reveal individual entities that form the cluster. According to one or more embodiments, a cluster is represented on a map or other application display by a visual representation known as a foundation. A user can interact with the foundation to cause the cluster to be opened to reveal a flyout that includes individual entities (e.g., geographic locations) that form the cluster. A user can also interact with an individual entity of the flyout to acquire more information about the individual entity. In at least some embodiments, a foundation can be annotated to indicate one or more entities in a cluster.

0115Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.