Patent Publication Number: US-11663694-B2

Title: Zoom-adaptive data granularity to achieve a flexible high-performance interface for a geospatial mapping system

Description:
PRIORITY APPLICATION 
     This application is a continuation of, and claims priority to U.S. patent application Ser. No. 16/681,546, filed Nov. 12, 2019, which is a continuation of, and claims priority to U.S. patent application Ser. No. 15/808,608, filed Nov. 9, 2017, which is a continuation of, and claims priority to U.S. patent application Ser. No. 15/377,668, filed Dec. 13, 2016, the disclosures of which are incorporated herein in their entirety by reference. 
    
    
     TECHNICAL FIELD 
     The present disclosure generally relates to the technical field of special-purpose machines that manage geospatial artifact data, including computerized variants of such special-purpose machines and improvements to such variants, and to the technologies by which such special-purpose machines become improved compared to other special-purpose machines that manage geospatial artifact data. In particular, the present disclosure addresses systems and methods for promoting geospatial artifact data. 
     BACKGROUND 
     Geographic mapping applications allow users to view a visual rendering of a map at various presentation levels. For example, a user can zoom in and out of the map to view the map at varying levels of granularity. At higher presentation levels (e.g., zoomed out), the number of roads, cities, stores, etc., that fall within the view of the map may be overwhelming if each is presented to a user. Accordingly, current systems often do not present each geographic landmark at higher presentation levels and provide greater granularity as the user chooses to zoom into a particular portion of the map. In some situations, however, a user may want to view geographic landmarks with greater granularity while at a higher presentation level. 
    
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
       Various ones of the appended drawings merely illustrate example embodiments of the present disclosure and are not intended to limit its scope to the illustrated embodiments. On the contrary, these examples are intended to cover alternatives, modifications, and equivalents as may be included within the scope of the disclosure. 
         FIG.  1    shows an exemplary system for promoting geospatial artifact data into a geospatial layer data set, according to some example embodiments. 
         FIG.  2    shows an example block diagram of a geospatial mapping manager, according to some example embodiments. 
         FIG.  3    shows an example method for causing a visual rendering of a geographical area to be presented on a client device, according to some example embodiments. 
         FIG.  4    shows an example method for promoting geospatial artifact data into a geospatial layer data set, according to some example embodiments. 
         FIG.  5    shows a diagrammatic representation of a computing device in the example form of a computer system within which a set of instructions for causing the computing device to perform any one or more of the methodologies discussed herein may be executed. 
     
    
    
     DETAILED DESCRIPTION 
     Reference will now be made in detail to specific example embodiments for carrying out the inventive subject matter of the present disclosure. In the following description, specific details are set forth in order to provide a thorough understanding of the subject matter. It shall be appreciated that embodiments may be practiced without some or all of these specific details. 
     Disclosed are systems, methods, and computer-readable storage media for promoting geospatial artifact data into a geospatial layer data set. A geospatial mapping system can present a visual rendering of a geographical area on a user&#39;s client device. For example, the geospatial mapping system can present a visual rendering of a world map, country map, city map, etc. The visual rendering of the geographic area can include visual renderings of geospatial artifacts that fall within the geographic area. A geospatial artifact can be a data object created to represent any geographic landmark or item. For example, a geospatial artifact can represent any event, object, path, landmark, person, vehicle, etc., that is geographically located within a geographic area. For example, a geospatial artifact can be a city, road, store, church, event, bus, school, etc., that is geographically located within a geographic area. 
     The geospatial mapping system can enable a user to adjust a presentation level at which the geographic area is presented. A presentation level can define a portion of the geographic area that is presented to the user. For example, a user can select to zoom in and out to adjust the presentation level, thereby defining the geographic area presented to the user. 
     The geospatial mapping system can maintain geospatial data defining the geographic area and the geospatial artifacts located within the geographic area. For example, the geospatial data can include map data that generally defines the geographic area, such as land, borders, bodies of water, etc. The geospatial data can also include geospatial artifact data for each geospatial artifact located within the geographic area. The geospatial artifact data for a geospatial artifact can include geographic coordinate data describing the geographic location of the geospatial artifact, as well as additional data describing the geospatial artifact. For example, the geospatial artifact data can include data describing the population of a city, name of a business, type of business, type of event, road name, etc. 
     To present a visual rendering of a geographical area, the geospatial mapping system can generate a geospatial layer data set that includes geospatial data for the geographic area. This can include map data describing the geographic area as well as a partial or complete set of the geospatial artifact data describing geospatial artifacts that are located within the geographic area. Map data may include the specific points, lines, and polygons required to draw a map on the client machine, and geospatial artifact data may include any subset of the geospatial artifact data which exists for a given set of geospatial artifacts. The geospatial mapping system can provide a generated geospatial layer data set to a user&#39;s client device, where it can be used to render the visual rendering of the geographical area. 
     The geospatial layer data set can also allow the client device to provide the user with a set of features to interact with the geospatial artifacts located within the geographic area. For example, features provided by the client device can include causing presentation of visual labels representing geospatial artifacts, adjusting presentation of the visual labels, accessing additional information describing a geospatial artifact, analytical functions, etc. 
     At higher presentation levels (e.g., zoomed out) the geographic area presented to the user can be relatively large and include a large number of geospatial artifacts. To reduce latency associated with generating and transmitting a geospatial layer data set, the geospatial mapping system can limit the amount of geospatial artifact data that is included in a geospatial layer data set based on the selected presentation level. For example, at higher presentation level that include a large number of geospatial artifacts, the geospatial mapping system can include a limited portion of the geospatial artifact data in the geospatial layer data set, such as only the geographic coordinate data associated with the geospatial artifacts. In addition, at a higher presentation level, a smaller number of individual points may be required to describe the same line because the granularity of the dataset may become large enough that multiple points are represented by a rendered pixel. Alternatively, at lower presentation levels (e.g., zoomed in) that include a smaller number of geospatial artifacts, the geospatial mapping system can include additional geospatial data in the geospatial layer data set. This additional geospatial data may either reference new geospatial artifacts or provide a more granular set of geospatial data for existing geospatial artifacts. For example, at a high presentation level, the geospatial data for the geospatial artifact referencing the United States may not have the full set of points which reference the coastline of Maine. When zooming in on Maine, however, the geospatial mapping system may choose to include more geospatial data about that specific section of the geospatial artifact. 
     While the limited portion of the geospatial artifact data may provide a user with a limited feature set to interact with geospatial artifacts, it may be insufficient to provide the user with advanced features. In some instances, a user may desire to perform advanced features while at a higher presentation level. To provide the user with these additional features, the geospatial mapping system can enable the user to promote geospatial artifact data into the geospatial layer data set. This can include geospatial artifact data for all of the geospatial artifacts included in the geographic area or for a subset of the geospatial artifacts. Once promoted, the additional geospatial artifact data can be used to provide the user with the additional features. Allowing a user to promote artifact data by request can enable the user to access the additional features when desired, while also limiting the amount of geospatial data included in a geospatial layer data set to reduce latency. 
       FIG.  1    shows an exemplary system  100  for promoting geospatial artifact data into a geospatial layer data set. While system  100  employs a client-server architecture, the present inventive subject matter is, of course, not limited to such an architecture, and could equally well find application in an event-driven, distributed, or peer-to-peer architecture system, for example. Moreover, it shall be appreciated that although the various functional components of system  100  are discussed in a singular sense, multiple instances of one or more of the various functional components may be employed. 
     As shown, system  100  can include multiple computing devices connected to communication network  102  and configured to communicate with each other through use of communication network  102 . Communication network  102  can be any type of network, including a local area network (“LAN”), such as an intranet; a wide area network (“WAN”), such as the Internet; or any combination thereof. Further, communication network  102  can be a public network, a private network, or a combination thereof. Communication network  102  can also be implemented using any number of communication links associated with one or more service providers, including one or more wired communication links, one or more wireless communication links, or any combination thereof. Additionally, communication network  102  can be configured to support the transmission of data formatted using any number of protocols. 
     Multiple computing devices can be connected to communication network  102 . A computing device can be any type of general computing device capable of network communication with other computing devices. For example, a computing device can be a personal computing device such as a desktop or workstation; a business server; or a portable computing device, such as a laptop, smart phone, or tablet personal computer (PC). A computing device can include some or all of the features, components, and peripherals of computing device  500  of  FIG.  5   . 
     To facilitate communication with other computing devices, a computing device can include a communication interface configured to receive a communication, such as a request, data, etc., from another computing device in network communication with the computing device and pass the communication along to an appropriate module running on the computing device. The communication interface can also be configured to send a communication to another computing device in network communication with the computing device. 
     As shown, system  100  includes client device  104 , geospatial mapping system  106  and secondary data source(s)  108 , such as high-scale data source(s). In system  100 , a user can interact with geospatial mapping system  106  through client device  104  connected to communication network  102  by direct and/or indirect communication. Client device  104  can be any of a variety of types of computing devices that include at least a display, a computer processor, and communication capabilities that provide access to communication network  102  (e.g., a smart phone, a tablet computer, a personal digital assistant (PDA), a personal navigation device (PND), a handheld computer, a desktop computer, a laptop or netbook, or a wearable computing device). 
     Geospatial mapping system  106  can consist of one or more computing devices and support connections from a variety of different types of client devices  104 , such as desktop computers, mobile computers, mobile communications devices (e.g., mobile phones, smart phones, tablets, etc.), smart televisions, set-top boxes, and/or any other network-enabled computing devices. Client device  104  can be of varying types, capabilities, operating systems, etc. Furthermore, geospatial mapping system  106  can concurrently accept connections from and interact with multiple client devices  104 . 
     A user can interact with geospatial mapping system  106  via client-side application  110  installed on client device  104 . In some embodiments, client-side application  110  can include a geospatial mapping system—specific component. For example, the component can be a standalone application, one or more application plug-ins, and/or a browser extension. However, the user can also interact with geospatial mapping system  106  via third-party application  112 , such as a web browser, that resides on client device  104  and is configured to communicate with geospatial mapping system  106 . In either case, client-side application  110  and/or third-party application  112  can present a user interface (UI) for the user to interact with geospatial mapping system  106 . 
     Geospatial mapping system  106  can include geospatial data storage  114  configured to store geospatial data. Geospatial data can include any type of data, such as digital data, documents, text files, audio files, video files, etc. Geospatial data can be data describing a geographic area. For example, geospatial data can include map data defining the geographic area as well as geospatial artifact data for each geospatial artifact located within the geographic area. The geospatial artifact data for a geospatial artifact can include geographic coordinate data describing the geographic location of the geospatial artifact, as well as additional data describing the geospatial artifact. For example, the geospatial artifact data can include data describing the population of a city, name of a business, type of business, type of event, road name, etc. 
     Geospatial data storage  114  can be a storage device, multiple storage devices, or one or more servers. Alternatively, geospatial data storage  114  can be a cloud storage provider or network storage. High functionality data management system  106  can store data in a storage area network (SAN) device, in a redundant array of inexpensive disks (RAID), etc. Geospatial data storage  114  can store data using one or more partition types, such as FAT, FAT32, NTFS, EXT2, EXT3, EXT4, ReiserFS, BTRFS, and so forth. 
     System  100  can also include secondary data source(s)  108  that store geospatial data. For example, secondary data source(s)  108  can include secondary data storage(s)  116  configured to store geospatial data. 
     Geospatial mapping system  106  can include geospatial mapping manager  118  configured to provide a user with a visual rendering of a geographic area. Geospatial mapping manager  118  can receive a request from client device  104  to view a visual rendering of a geographic area, and in response, provide client device  104  with a geospatial layer data set for the geographic area. The geospatial layer data set can include geospatial data for the geographic area that client device  104  can use to render the visual rendering of the geographic area. 
     The geographic area can be defined by a presentation level selected by a user. For example, the presentation level can indicate a zoom level at which the user would like to view a specified geographic area. The user can adjust the presentation level to view a selected portion of a map at a lower presentation level (e.g., zoomed in) or higher presentation level (e.g., zoomed out), thereby adjusting the geographic area. In some embodiments, the request received from client device  104  can include data identifying the presentation level selected by the user. Geospatial mapping manager  118  can use the received data to determine the geographic area to be presented to the user. 
     The geospatial layer data set for a geographic area can include map data describing the geographic area as well as a partial or complete set of the geospatial artifact data describing geospatial artifacts that are located within the geographic area. In some embodiments, geospatial mapping manager  118  can generate a geospatial layer data set in response to receiving the request from client device  104 . For example, in response to receiving the request, geospatial mapping manager  118  can search geospatial data storage  114  and/or secondary data source(s)  108  for geospatial data for the requested geographic area. Geospatial mapping manager  118  can use data gathered as part of the search to generate the geospatial layer data set. 
     Alternatively, geospatial mapping manager  118  can access a previously generated geospatial layer data set in response to receiving the request from client device  104 . For example, geospatial mapping manager  118  can generate geospatial layer data sets from data gathered from secondary data source(s)  108  and/or geospatial data storage  114 . The previously generated geospatial data sets can be stored in geospatial data storage  114  and geospatial mapping manager  118  can communicate with geospatial data storage  114  to retrieve a previously generated geospatial data set in response to receiving a request. 
     In addition to enabling client device  104  to present a visual rendering of the geographic area, the geospatial data included in the geospatial layer data set can also enable a user of client device  104  to utilize one or more features to interact with the geospatial artifacts. For example, a feature can include causing a label representing a geospatial artifact to be presented, adjusting presentation of the visual labels, accessing additional information describing a geospatial artifact, analytical functions such as creating a histogram or timeline, etc. 
     Geospatial mapping manager  118  can limit the amount of geospatial artifact data included in a geospatial layer data set. For example, if a large number of geospatial artifacts are located within a geographic area (e.g., when the user selects to view the map at a higher presentation level), geospatial mapping manager  118  can include a limited set of geospatial artifact data for the geospatial artifacts. For example, the limited set of geospatial data can include limited data describing the geospatial artifacts, such as geographic coordinate data for the geospatial artifacts. As another example, the limited data set can include geospatial data for only a subset of the geospatial artifacts included in a geographic area. 
     Limiting the amount of geospatial artifact data included in the geospatial layer data set can reduce latency associated with generating and/or transmitting the geospatial layer data set. Alternatively, geospatial mapping manager  118  can provide a complete set of geospatial artifact data when a relatively lower number of geospatial artifacts are located within a geographic area (e.g., when the user selects to view the map at a lower presentation level). 
     Geospatial mapping manager  118  can promote geospatial artifact data into a geospatial layer data set to provide a user with additional and/or advanced features to interact with a geospatial artifact located in a geographic area. In some instances, the limited set of geospatial artifact data included in a geospatial layer data set may be insufficient to provide one or more features for interacting with a geospatial artifact. For example, additional data beyond the geographic coordinate data of a geospatial artifact may be needed to provide a feature such as causing presentation of additional data associated with the geospatial artifact or analytical functions. A user may desire to access these additional features while at a higher viewing level (e.g., without having to zoom in). 
     In this type of situation, geospatial mapping manager  118  can promote additional geospatial artifact data into a geospatial layer data set. For example, geospatial mapping manager  118  can receive a request from client device  104  indicating that a user of client device  104  would like to utilize a feature that cannot be provided based on the geospatial artifact data included in the geospatial layer data set. In response, geospatial mapping manager  118  can promote additional geospatial artifact data into the geospatial layer data set, which can then be provided to client device  104  to provide the requested feature. 
       FIG.  2    shows an example block diagram of geospatial mapping manager  118 . To avoid obscuring the inventive subject matter with unnecessary detail, various functional components (e.g., modules) that are not germane to conveying an understanding of the inventive subject matter have been omitted from  FIG.  2   . However, a skilled artisan will readily recognize that various additional functional components may be supported by high functionality data manager  120  to facilitate additional functionality that is not specifically described herein. Furthermore, the various functional modules depicted in  FIG.  2    may reside on a single computing device or may be distributed across several computing devices in various arrangements such as those used in cloud-based architectures. 
     As shown, high functionality data manager  120  includes communication module  202 , geospatial layer data set generation module  204 , and promotion module  206 . Interface module  202  can provide client device  104  with data that enables client device  104  to present a map interface on a display of client device  104 . A map interface can be an interactive user interface that allows a user to view and interact with geospatial data. For example, a map interface can present a user with a visual rendering of a geographic area. Further, a map interface can include one or more user interface elements (e.g., buttons, text boxes, scroll bars, etc.) that enable a user to modify presentation of the geographic area, adjust settings, utilize features, etc. For example, the map interface can enable a user to define a geographic area by adjusting a presentation level. As another example, the map interface can enable a user to select to utilize features on a geospatial artifact and/or a group of geospatial artifacts, such as causing a label representing the geospatial artifact(s) to be presented within the map interface. 
     Geospatial layer data set generation module  204  can be configured to generate a geospatial layer data set. Geospatial layer data set generation module  204  can gather geospatial data from geospatial data storage  114  and/or secondary data sources  108 , which can be used to generate the geospatial layer data set. A geospatial layer data set can include geospatial data for a specified geographic area. For example, the geospatial layer data set can include geospatial data, such as map data describing the geographic area. The geospatial layer data set can also include geospatial artifact data for geospatial artifacts located within the geographic area. 
     A geospatial layer data set can be used to present a user with a visual rendering of a geographic area. For example, a geospatial layer data set can be provided to client device  104 , where client device  104  can utilize the geospatial layer data set to present a visual rendering of the geographic area. Alternatively, geospatial mapping manager  118  can utilize the geospatial layer data set to provide data to client device  104 , which can be used by client device  104  to present the visual rendering of the geographic area. 
     In some embodiments, geospatial layer data set generation module  204  can generate a geospatial layer data set in response to receiving a request from client device  104 . The request can include data defining a geographic area that the user would like view. For example, a user can utilize the map interface to define the geographic area by adjusting the presentation level, causing client device  104  to transmit the request to geospatial mapping manager  118 . In response to geospatial mapping manager  118  receiving the request, geospatial layer data set generation module  204  can gather geospatial data from geospatial data storage  114  and/or secondary data source(s)  108  for the requested geographic area. Geospatial layer data set generation module  204  can use the gathered geospatial data to generate the geospatial layer data set. 
     In some embodiments, geospatial layer data set generation module  204  can pre-generate geospatial layer data sets. For example, geospatial layer data set generation module  204  can generate geospatial layer data sets for geographic areas based on available presentation levels. 
     The pre-generated geospatial layer data sets can be stored in geospatial data storage  114  and used to present a visual rendering of a geographic area on client device  104 . For example, in response to receiving a request from client device  104  that defines a geographic area, geospatial mapping manager  118  can access geospatial data storage  114  to access an appropriate geospatial layer data set to satisfy the received request. 
     In some embodiments, geospatial layer data set generation module  204  can limit the amount of geospatial artifact data included in a geospatial layer data set to reduce latency associated with generating and/or transmitting the geospatial layer data set. For example, when a geographic area includes a large number of geospatial artifacts (e.g., when the user is at a higher presentation level), geospatial layer data set generation module  204  can include a limited set of geospatial artifact data in the geospatial layer data set. Alternatively, when a geographic area includes a lower number of geospatial artifacts (e.g., when the user is at a lower presentation level), geospatial layer data set generation module  204  can include a complete set of geospatial artifact data in the geospatial layer data set. 
     In some embodiments, geospatial mapping manager  118  can promote geospatial artifact data into a geospatial layer data set. Promoting geospatial artifact data into a geospatial layer data set can include accessing the geospatial artifact data from geospatial data storage  114  and/or secondary data source(s)  108 , and modifying the geospatial layer data set to include the geospatial artifact data. In some embodiments, promoting geospatial artifact data describing a geospatial artifact can further include copying the geospatial data from secondary data source(s)  108  and storing the copied geospatial artifact data in geospatial data storage  114 , where it is associated and/or otherwise linked to a data object for the geospatial artifact. 
     Promoting the additional geospatial artifact data into a geospatial layer data set can allow a user to utilize additional features associated with the geospatial artifacts without requiring the user to adjust the presentation layer (e.g., zoom in). For example, a user can view a label associated with geospatial artifacts while remaining at a high presentation level. 
     Promotion module  206  can be configured to promote geospatial artifact data into a generated geospatial layer data set. Promotion module  206  can receive a request from client device  104  to promote geospatial artifact data into a geospatial layer data set and, in response, search geospatial data storage  114  and secondary data source(s)  108  to gather additional geospatial artifact data to include the geospatial layer data set. Promotion module  206  can then update the geospatial layer data set to include the additional geospatial artifact data. 
     Additionally, in some embodiments, promotion module  206  can store the geospatial data received from secondary data source(s)  108  in geospatial data storage  114 . Further, the stored data can be associates with corresponding data objects. For example, geospatial data received from secondary data source(s)  108  that describes a geospatial artifact can be stored in geospatial data storage  114  and associated with a data object for the geospatial artifact. 
     In some embodiments, the request received from client device  104  can include data identifying a set of geospatial artifacts that a user would like to interact with and thus have geospatial artifact data for the set of geospatial artifacts promoted to the geospatial layer data set. For example, the map interface can enable the user to select geospatial artifact by type, geographic area, etc., that the user would like to promote. For example, the user can select to promote geospatial artifact data for all stores, churches, etc. The resulting request sent to geospatial mapping system  106  can include data identifying the set of geospatial artifacts, which promotion module  206  can use to search geospatial data storage  114  and/or secondary data source(s)  108  for geospatial artifact data. 
       FIG.  3    shows an example method  300  for causing a visual rendering of a geographical area to be presented on a client device. Method  300  may be embodied in computer-readable instructions for execution by one or more processors such that the operations of method  300  may be performed in part or in whole by geospatial mapping system  106 ; accordingly, method  300  is described below by way of example with reference thereto. However, it shall be appreciated that at least some of the operations of method  300  may be performed on various other hardware configurations and method  300  is not intended to be limited to geospatial mapping system  106 . 
     At operation  302 , geospatial mapping system  106  receives a request from client device  104  to view a visual rendering of a geographical area. The request can include data identifying the geographical area. For example, the request can include data identifying a presentation level (e.g., zoom level) selected by a user of the client device that defines the geographic area. 
     At operation  304 , geospatial layer data set generation module  204  generates a geospatial layer data set for the geographic area. The geospatial layer data set can include geospatial data describing the geographic area, such as map data and geospatial artefact data describing geospatial artifacts located in the geographic area. 
     In some embodiments, geospatial layer data set generation module  204  can search geospatial data storage  114  and secondary data source(s)  108  to gather the geospatial data to include in the geospatial layer data set. Further, the geospatial layer data set generation module  204  can include a limited set of geospatial artefact data in the geospatial layer data set. The limited set of geospatial artifact data can include limited data describing a geospatial artifact (e.g., only geographic coordinate data and label data), and/or geospatial artifact data describing only a subset of the geospatial artifacts located in the geographic area. Including a limited set of geospatial artifact data can reduce the time and resources required to generate the geospatial layer data set. 
     At operation  306 , interface module  202  can provide the geospatial layer data set to client device  104 . Client device  104  can utilize the received geospatial layer data set to present a visual rendering of the geographic area. For example, client-side application  110  can cause the visual rendering of the geographic area to be presented in a map interface. 
     The visual rendering of the geographic area can include visual representations of geospatial artifacts included in the geographic area. For example, client device  104  can use the label data and geographic coordinate data describing one or more geospatial artifacts to present a visual label, such as a graphical icon, representing the geospatial artifact. The visual label can be presented at a location to represent the geographic location of the geospatial artifact. 
     In some embodiments, the visual labels can represent a group of geospatial artifacts rather than a separate label being presented at each geospatial artifact. At higher presentation levels this can provide a user with a cleaner view of geographic area. 
     Although a visual representation of the geospatial artifacts is presented to the user, in some embodiments, additional features cannot be accessed with respect to the presented geospatial artifacts. For example, the user may not be able to select a geospatial artifact to access additional information describing the geospatial artifact without altering the presentation level (e.g., zooming in) or causing geospatial artifact data for the geospatial artifacts to be promoted into the geospatial layer data set. 
     At operation  308 , geospatial mapping system  106  receives, from client device  104 , data indicating an updated presentation level selected by a user of client device  104 . The updated presentation level can define a smaller geographic as a result of the user selecting to zoom in to the presented geographic area. 
     At operation  310 , geospatial layer data set generation module  204  generates an updated geospatial layer data set for the updated geographic area. The updated geospatial layer data set for the updated geographic area can include additional geospatial artifact data for the geospatial artifacts included in the updated geographic area. 
     At operation  312 , interface module  202  provides the updated geospatial layer data set to client device  104 . Client device  104  can utilize the updated geospatial layer data set to present a visual rendering of the updated geographic area. For example, client-side application  110  can cause the visual rendering of the updated geographic area to be presented in a map interface. Further, the additional geospatial artifact data can provide the user with additional features, such as accessing additional information describing a geospatial artifact. A user can therefore adjust the presentation level (e.g., zoom in) to passively access additional features associated with the geospatial artifacts included in a geographic area. 
       FIG.  4    shows an example method  400  for promoting geospatial artifact data into a geospatial layer data set. Method  400  may be embodied in computer-readable instructions for execution by one or more processors such that the operations of method  400  may be performed in part or in whole by geospatial mapping system  106 ; accordingly, method  400  is described below by way of example with reference thereto. However, it shall be appreciated that at least some of the operations of method  400  may be deployed on various other hardware configurations and method  400  is not intended to be limited to geospatial mapping  106 . 
     At operation  402 , geospatial mapping system  106  accesses a geospatial layer data set for a geographic area defined by a presentation level. The geospatial layer data set for the geographic area includes a limited geospatial artifact data set for geospatial artifacts located within the geographic area. For example, geospatial mapping system  106  can gather a pre-generated geospatial layer data set from geospatial data storage  114 . Alternatively, geospatial layer data set generation module  204  can generate the geospatial layer data set. 
     At operation  404 , geospatial mapping system  106  provides the geospatial layer data set for the geographic area to client device  104 . Client device  104  uses the geospatial layer data set for the geographic area to present a visual rendering of the geographic area. The limited geospatial artifact data set included in the geospatial layer data set for the geographic area enables client device  104  to provide a limited feature set for interacting with the geospatial artifacts located within the geographic area. For example, a user can view a label representing the geospatial artifacts, however may not be able to interact with the geospatial artifact further to access additional information. 
     At operation  406 , geospatial mapping system  106  receives, from client device  104 , a request to change, annotate, edit, or utilize an additional feature set on a subset of geospatial artifacts located within the geographic area. For example, a user may have selected to annotate a subset of geospatial artifacts such as stores, churches, etc. 
     At operation  408 , promotion module  206  promotes, to the geospatial layer data set for the geographic area, an additional geospatial artifact data set for the subset of geospatial artifacts, yielding an updated geospatial layer data set for the geographic area. For example, promotion module  206  can access the geospatial artifact data from geospatial data storage  114  and/or secondary data source(s)  108 . Promotion module  206  then modifies the geospatial layer data set to include the additional geospatial data set for the subset of geospatial artifact. 
     At operation  410 , interface module  202  provides the updated geospatial layer data set for the geographic area to client device  104 . The additional geospatial artifact data set included in the updated geospatial layer data set enables client device  104  to provide the advanced feature set for interacting with the subset of geospatial artifacts located within the geographic area. Accordingly, a user can actively access additional features associated with the geospatial artifacts included in a geographic area by promoting geospatial artifact data into the geospatial artifact layer data set. 
       FIG.  5    shows a block diagram illustrating components of a computing device  500 , according to some example embodiments, able to read instructions from a machine-readable medium (e.g., a machine-readable storage medium) and perform any one or more of the methodologies discussed herein. Specifically,  FIG.  5    shows a diagrammatic representation of computing device  500  in the example form of a system, within which instructions  502  (e.g., software, a program, an application, an applet, an app, a driver, or other executable code) for causing computing device  500  to perform any one or more of the methodologies discussed herein may be executed. For example, instructions  502  include executable code that causes computing device  500  to execute methods  300  and  400 . In this way, these instructions transform the general, non-programmed computing device into a particular computing device programmed to carry out the described and illustrated functions in the manner described herein. Computing device  500  may operate as a standalone device or may be coupled (e.g., networked) to other machines. 
     By way of non-limiting example, computing device  500  may comprise or correspond to a television, a computer (e.g., a server computer, a client computer, a PC, a tablet computer, a laptop computer, or a netbook), a set-top box (STB), a PDA, an entertainment media system (e.g., an audio/video receiver), a cellular telephone, a smart phone, a mobile device, a wearable device (e.g., a smart watch), a portable media player, or any machine capable of outputting audio signals and capable of executing instructions  502 , sequentially or otherwise, that specify actions to be taken by computing device  500 . Further, while only a single computing device  500  is illustrated, the term “machine” shall also be taken to include a collection of computing devices  500  that individually or jointly execute instructions  502  to perform any one or more of the methodologies discussed herein. 
     Computing device  500  may include processors  504 , memory  506 , storage unit  508 , and I/O components  510 , which may be configured to communicate with each other such as via bus  512 . In an example embodiment, processors  504  (e.g., a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a digital signal processor (DSP), an application specific integrated circuit (ASIC), a radio-frequency integrated circuit (RFIC), another processor, or any suitable combination thereof) may include, for example, processor  514  and processor  516  that may execute instructions  502 . The term “processor” is intended to include multi-core processors that may comprise two or more independent processors (sometimes referred to as “cores”) that may execute instructions contemporaneously. Although  FIG.  5    shows multiple processors, computing device  500  may include a single processor with a single core, a single processor with multiple cores (e.g., a multi-core processor), multiple processors with a single core, multiple processors with multiples cores, or any combination thereof. 
     Memory  506  (e.g., a main memory or other memory storage) and storage unit  508  are both accessible to processors  504  such as via bus  512 . Memory  506  and storage unit  508  store instructions  502  embodying any one or more of the methodologies or functions described herein. In some embodiments, data storage  516  resides on storage unit  508 . Instructions  502  may also reside, completely or partially, within memory  506 , within storage unit  508 , within at least one of processors  504  (e.g., within the processor&#39;s cache memory), or any suitable combination thereof, during execution thereof by computing device  500 . Accordingly, memory  506 , storage unit  508 , and the memory of processors  504  are examples of machine-readable media. 
     As used herein, “machine-readable medium” means a device able to store instructions and data temporarily or permanently and may include, but not be limited to, random-access memory (RAM), read-only memory (ROM), buffer memory, flash memory, optical media, magnetic media, cache memory, other types of storage (e.g., erasable programmable read-only memory (EEPROM)), or any suitable combination thereof. The term “machine-readable medium” should be taken to include a single medium or multiple media (e.g., a centralized or distributed database, or associated caches and servers) able to store instructions  502 . The term “machine-readable medium” shall also be taken to include any medium, or combination of multiple media, that is capable of storing instructions (e.g., instructions  502 ) for execution by a machine (e.g., computing device  500 ), such that the instructions, when executed by one or more processors of computing device  500  (e.g., processors  504 ), cause computing device  500  to perform any one or more of the methodologies described herein (e.g., methods  300  and  400 ). Accordingly, a “machine-readable medium” refers to a single storage apparatus or device, as well as “cloud-based” storage systems or storage networks that include multiple storage apparatus or devices. The term “machine-readable medium” excludes signals per se. 
     Furthermore, the “machine-readable medium” is non-transitory in that it does not embody a propagating signal. However, labeling the tangible machine-readable medium as “non-transitory” should not be construed to mean that the medium is incapable of movement—the medium should be considered as being transportable from one real-world location to another. Additionally, since the machine-readable medium is tangible, the medium may be considered to be a machine-readable device. 
     The I/O components  510  may include a wide variety of components to receive input, provide output, produce output, transmit information, exchange information, capture measurements, and so on. The specific I/O components  510  that are included in a particular machine will depend on the type of machine. For example, portable machines such as mobile phones will likely include a touch input device or other such input mechanisms, while a headless server machine will likely not include such a touch input device. It will be appreciated that I/O components  510  may include many other components that are not specifically shown in  FIG.  5   . I/O components  510  are grouped according to functionality merely for simplifying the following discussion and the grouping is in no way limiting. In various example embodiments, I/O components  510  may include input components  518  and output components  520 . Input components  518  may include alphanumeric input components (e.g., a keyboard, a touch screen configured to receive alphanumeric input, a photo-optical keyboard, or other alphanumeric input components), point-based input components (e.g., a mouse, a touchpad, a trackball, a joystick, a motion sensor, or other pointing instruments), tactile input components (e.g., a physical button, a touch screen that provides location and/or force of touches or touch gestures, or other tactile input components), audio input components, and the like. Output components  520  may include visual components (e.g., a display such as a plasma display panel (PDP), a light emitting diode (LED) display, a liquid crystal display (LCD), a projector, or a cathode ray tube (CRT)), acoustic components (e.g., speakers), haptic components (e.g., a vibratory motor, resistance mechanisms), other signal generators, and so forth. 
     Communication may be implemented using a wide variety of technologies. I/O components  510  may include communication components  522  operable to couple computing device  500  to network  524  or devices  526  via coupling  528  and coupling  530 , respectively. For example, communication components  522  may include a network interface component or other suitable device to interface with network  524 . In further examples, communication components  522  may include wired communication components, wireless communication components, cellular communication components, near field communication (NFC) components, Bluetooth® components (e.g., Bluetooth® Low Energy), WiFi® components, and other communication components to provide communication via other modalities. The devices  526  may be another machine or any of a wide variety of peripheral devices (e.g., a peripheral device coupled via a Universal Serial Bus (USB)). 
     Modules, Components, and Logic 
     Certain embodiments are described herein as including logic or a number of components, modules, or mechanisms. Modules may constitute either software modules (e.g., code embodied on a machine-readable medium or in a transmission signal) or hardware modules. A hardware module is a tangible unit capable of performing certain operations and may be configured or arranged in a certain manner. In example embodiments, one or more computer systems (e.g., a standalone, client, or server computer system) or one or more hardware modules of a computer system (e.g., a processor or a group of processors) may be configured by software (e.g., an application or application portion) as a hardware module that operates to perform certain operations as described herein. 
     In various embodiments, a hardware module may be implemented mechanically or electronically. For example, a hardware module may comprise dedicated circuitry or logic that is permanently configured (e.g., as a special-purpose processor, such as a field-programmable gate array (FPGA) or an ASIC) to perform certain operations. A hardware module may also comprise programmable logic or circuitry (e.g., as encompassed within a general-purpose processor or other programmable processor) that is temporarily configured by software to perform certain operations. It will be appreciated that the decision to implement a hardware module mechanically, in dedicated and permanently configured circuitry, or in temporarily configured circuitry (e.g., configured by software) may be driven by cost and time considerations. 
     Accordingly, the term “hardware module” should be understood to encompass a tangible entity, be that an entity that is physically constructed, permanently configured (e.g., hardwired), or temporarily configured (e.g., programmed) to operate in a certain manner and/or to perform certain operations described herein. Considering embodiments in which hardware modules are temporarily configured (e.g., programmed), each of the hardware modules need not be configured or instantiated at any one instance in time. For example, where the hardware modules comprise a general-purpose processor configured using software, the general-purpose processor may be configured as respective different hardware modules at different times. Software may accordingly configure a processor, for example, to constitute a particular hardware module at one instance of time and to constitute a different hardware module at a different instance of time. 
     Hardware modules can provide information to, and receive information from, other hardware modules. Accordingly, the described hardware modules may be regarded as being communicatively coupled. Where multiple of such hardware modules exist contemporaneously, communications may be achieved through signal transmission (e.g., over appropriate circuits and buses that connect the hardware modules). In embodiments in which multiple hardware modules are configured or instantiated at different times, communications between or among such hardware modules may be achieved, for example, through the storage and retrieval of information in memory structures to which the multiple hardware modules have access. For example, one hardware module may perform an operation and store the output of that operation in a memory device to which it is communicatively coupled. A further hardware module may then, at a later time, access the memory device to retrieve and process the stored output. Hardware modules may also initiate communications with input or output devices, and can operate on a resource (e.g., a collection of information). 
     The various operations of example methods described herein may be performed, at least partially, by one or more processors that are temporarily configured (e.g., by software) or permanently configured to perform the relevant operations. Whether temporarily or permanently configured, such processors may constitute processor-implemented modules that operate to perform one or more operations or functions. The modules referred to herein may, in some example embodiments, comprise processor-implemented modules. 
     Similarly, the methods described herein may be at least partially processor-implemented. For example, at least some of the operations of a method may be performed by one or more processors or processor-implemented modules. The performance of certain of the operations may be distributed among the one or more processors, not only residing within a single machine, but deployed across a number of machines. In some example embodiments, the processor or processors may be located in a single location (e.g., within a home environment, an office environment, or a server farm), while in other embodiments the processors may be distributed across a number of locations. 
     The one or more processors may also operate to support performance of the relevant operations in a “cloud computing” environment or as a “software as a service” (SaaS). For example, at least some of the operations may be performed by a group of computers (as examples of machines including processors), with these operations being accessible via a network (e.g., the Internet) and via one or more appropriate interfaces (e.g., APIs). 
     Electronic Apparatus and System 
     Example embodiments may be implemented in digital electronic circuitry; in computer hardware, firmware, or software; or in combinations of them. Example embodiments may be implemented using a computer program product, for example, a computer program tangibly embodied in an information carrier, for example, in a machine-readable medium for execution by, or to control the operation of, data processing apparatus, for example, a programmable processor, a computer, or multiple computers. 
     A computer program can be written in any form of programming language, including compiled or interpreted languages, and it can be deployed in any form, including as a standalone program or as a module, subroutine, or other unit suitable for use in a computing environment. A computer program can be deployed to be executed on one computer or on multiple computers at one site, or distributed across multiple sites and interconnected by a communication network. 
     In example embodiments, operations may be performed by one or more programmable processors executing a computer program to perform functions by operating on input data and generating output. Method operations can also be performed by, and apparatus of example embodiments may be implemented as, special-purpose logic circuitry (e.g., an FPGA or an ASIC). 
     The computing system can include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other. In embodiments deploying a programmable computing system, it will be appreciated that both hardware and software architectures merit consideration. Specifically, it will be appreciated that the choice of whether to implement certain functionality in permanently configured hardware (e.g., an ASIC), in temporarily configured hardware (e.g., a combination of software and a programmable processor), or in a combination of permanently and temporarily configured hardware may be a design choice. 
     Language 
     Although the embodiments of the present inventive subject matter have been described with reference to specific example embodiments, it will be evident that various modifications and changes may be made to these embodiments without departing from the broader scope of the inventive subject matter. Accordingly, the specification and drawings are to be regarded in an illustrative rather than a restrictive sense. The accompanying drawings that form a part hereof show by way of illustration, and not of limitation, specific embodiments in which the subject matter may be practiced. The embodiments illustrated are described in sufficient detail to enable those skilled in the art to practice the teachings disclosed herein. Other embodiments may be used and derived therefrom, such that structural and logical substitutions and changes may be made without departing from the scope of this disclosure. This Detailed Description, therefore, is not to be taken in a limiting sense, and the scope of various embodiments is defined only by the appended claims, along with the full range of equivalents to which such claims are entitled. 
     Such embodiments of the inventive subject matter may be referred to herein, individually and/or collectively, by the term “invention” merely for convenience and without intending to voluntarily limit the scope of this application to any single invention or inventive concept if more than one is in fact disclosed. Thus, although specific embodiments have been illustrated and described herein, it should be appreciated that any arrangement calculated to achieve the same purpose may be substituted for the specific embodiments shown. This disclosure is intended to cover any and all adaptations or variations of various embodiments. Combinations of the above embodiments, and other embodiments not specifically described herein, will be apparent, to those of skill in the art, upon reviewing the above description. 
     All publications, patents, and patent documents referred to in this document are incorporated by reference herein in their entirety, as though individually incorporated by reference. In the event of inconsistent usages between this document and those documents so incorporated by reference, the usage in the incorporated references should be considered supplementary to that of this document; for irreconcilable inconsistencies, the usage in this document controls. 
     In this document, the terms “a” or “an” are used, as is common in patent documents, to include one or more than one, independent of any other instances or usages of “at least one” or “one or more.” In this document, the term “or” is used to refer to a nonexclusive or, such that “A or B” includes “A but not B,” “B but not A,” and “A and B,” unless otherwise indicated. In the appended claims, the terms “including” and “in which” are used as the plain-English equivalents of the respective terms “comprising” and “wherein.” Also, in the following claims, the terms “including” and “comprising” are open-ended; that is, a system, device, article, or process that includes elements in addition to those listed after such a term in a claim are still deemed to fall within the scope of that claim.