Patent Description:
Anonymous non-patent publication "Oracle Fusion Middleware User's Guide for Oracle MapViewer <NUM> Release <NUM> (<NUM>. <NUM>) E10145-<NUM>" relates to uses of a tool for rendering maps. <CIT> relates to a personal wireless navigation system. <NPL>" relates to a scalable tile map service.

This specification describes technologies relating to reducing latency in transmitting and presenting map user interfaces.

In general, one innovative aspect of the subject matter described in this specification is specified by method claim <NUM>. Other embodiments of this aspect include corresponding systems, apparatus, and computer programs, configured to perform the actions of the methods, encoded on computer storage devices.

These and other embodiments can each optionally include one or more of the following features. In some aspects, the visual characteristic for each sub-region includes a particular color assigned to the sub-region and that is presented within the sub-region in the image.

The image file may be renderable using fewer computing resources than required to generate the canvas. Some aspects can include reducing a data size of the image file using compression techniques that include: assigning, to each sub-region of the image, a particular red, green, blue (RGB) color in which the sub-region of the image is presented and storing, in the image file and for each particular sub-region, the RGB color for the sub-region and data specifying locations of the particular sub-region within the image.

Some aspects can include receiving, at the one or more servers and from the client device, data specifying a selection of a particular location within the image. An updated image file can be generated that depicts a map of the particular sub-region that corresponds to the selected location in response to the selection. This generating can include rendering a map of the particular sub-region using the mapping service and generating an image of the rendered map. An image file representing the updated image can be provided to the client device. Some aspects can include receiving, from the client device, data specifying a zoom level for the image at the time of the selection. A level of granularity for the selection can be determined based on the zoom level. The particular sub-region that corresponds to the selected location can be determined based on the level of granularity for the selection.

In some aspects, the image file includes a Portable Network Graphics (PNG) file format. Some aspects can include providing, by the one or more servers and to the client device, one or more additional image files that each represents a map of at least one of the sub-regions in response to the request and prior to receiving a request for the one or more additional image files.

The latency in providing and presenting an interactive map user interface at a client device can be reduced by providing a compressed image file with an index to data that can be presented in response to user interactions, rather than loading scripts, canvases, graphics, Document Object Model (DOM) elements and other data onto the client device. For example, the amount of networking resources required to provide an image file (e.g., a compressed image file) over the Internet may be substantially less than the amount of networking resources required to provide scripts, canvases, and DOM elements used to generate the map at the client device.

Similarly, the demand placed upon computing resources of the client device can be reduced using the compressed image file as the client device's processor does not have to load the scripts or DOM elements or generate the canvases. In addition, the amount of memory (e.g., RAM) of the client device used to present the interactive map user interface can be reduced using the image file, which frees up memory for other applications and increases the speed at which data is processed by the client device. By assigning a particular color to each entire sub-region of a map image, the size of the image file that stores the image can be reduced (e.g., compressed), resulting in faster transmission times between devices and less consumed network bandwidth used to transmit the image file. Embodiments can therefore address problems associated with delivery and display of interactive map data.

A system can reduce the latency in providing and presenting interactive map user interfaces. For example, the system can generate an image of a map generated by a mapping service. The image can depict a map of a particular region and its sub-regions. The system can also generate an electronic index that maps locations within the image (e.g., x-y coordinates of the image) to the sub-regions of the image and provide the electronic index and the image to a client device. The electronic index can also map the sub-regions to data for the sub-regions. In this way, when a user interacts with the image of the map at a location that corresponds to a particular sub-region, e.g., by hovering over or selecting a location that corresponds to the sub-region, data for the sub-region can be presented to the user in an interactive way.

Providing the image to the client device, e.g., over the Internet, can require less computing and networking resources than generating a map at the client device using a mapping service. This also increases the speed at which map user interfaces are presented to the user. The amount of computing and networking resources can be further reduced, and the speed further increased, by compressing the image. In some implementations, the image can be compressed by assigning a particular color to each sub-region of the image. For example, an entire sub-region may be depicted in the particular color assigned to the sub-region rather than depicting different colors for roads, terrain, etc. In this way, the size of the image file can be reduced, allowing for quicker transfer over a network and less network bandwidth to transfer the image over the network. For example, because all of the area of a given sub-region is the same color, only a single color code (e.g., RGB value) needs to be sent for the entire area of the image representing the sub-region rather than sending different color codes for multiple different portions of the sub-region. In addition, the client device can present the compressed image quicker using compressed image rendering technologies, e.g., implemented by graphics processing units (GPUs).

To further reduce latency in presenting interactive user interfaces, additional images of maps may be provided prior to the maps being requested. The additional map images can be stored at the client device, e.g., in a cache, to enable quicker presentation of the maps if the user requests the maps. For example, the system may provide more detailed maps of each sub-region depicted in the image generated in response to the request in case the user selects one of the sub-regions for a more detailed view.

<FIG> is an example environment <NUM> in which a data management system <NUM> provides interactive map user interfaces. For example, the data management system <NUM> may provide interactive map user interfaces to client devices, e.g. the client device <NUM>, in response to requests received from the client devices. The data management system <NUM> can send the interactive map user interfaces over a data communication network <NUM>, e.g., a local area network (LAN), a wide area network (WAN), a mobile communication network, the Internet, or a combination thereof. The network <NUM> can include servers, hubs, routers, switches, interface devices, transmission media, and other networking components that enable devices to send and receive data to other devices.

A client device <NUM> is an electronic device that is capable of requesting and receiving electronic resources and other data over a network <NUM>. Example client devices <NUM> include personal computers, mobile communication devices (e.g., smartphones, tablet computing devices, and/or smart watches), and other devices that can send and receive data over the network <NUM>. A client device <NUM> typically includes a user application, such as a web browser, to facilitate the sending and receiving of data over the network <NUM>. The web browser can enable a user to interact with text, images, videos, music, and other information typically located on a web page at a website.

A client device <NUM> can include other applications, e.g., native applications developed for a particular type of device or for a particular platform. For example, the client device <NUM> includes a map viewer <NUM> that presents interactive map user interfaces <NUM> to a user of the client device <NUM>. The map viewer <NUM> may be implemented in a web browser, a native application, or another type of application program.

The interactive map user interface <NUM> presents a map of a particular region. For example, the interactive map user interface <NUM> can present a map of a particular region specified by a request received from the client device <NUM>. The interactive map user interface <NUM> can also present data related to the particular region and/or sub-regions of the region included in the map. As described below, the presented data can include account data related to an online account that the user of the client device <NUM> is authorized to access. The data can be presented in response to user interactions with the map. For example, if a user of the client device <NUM> hovers a cursor or other pointer over a location that corresponds to a particular sub-region, the data for the sub-region may be presented to the user. An example interactive map user interface is illustrated in <FIG> and described in more detail below.

The data management system <NUM> can manage data for users and/or organizations and provide the data for presentation to the users, e.g., in user interfaces generated by the data management system <NUM>. For example, the data management system <NUM> can manage online account data for multiple different accounts of multiple different account holders. In a particular example, the data management system <NUM> can manage content delivery account data for multiple different organizations. The systems and techniques described below can also be applied to various other types of data.

The account data managed by the account management system <NUM> can include any data related to an account, such as performance data for content items (e.g., number of impressions, click through rates, conversion rates, etc.), budget information for account holders, and/or content item distribution criteria. The account data for each account holder is stored in an account data storage device <NUM>, which may include multiple data storage devices located in one or more data centers. The account data for each account holder may be stored separately and securely such that account data for one account holder is not provided to users of a different account holder.

At least a portion of the account data is stored with data identifying a corresponding geographic location for the data. For example, data for a content delivery campaign includes data specifying a number of impressions of a content item, a number of selections of the content item, a number of conversions resulting from presentations of the content item, and/or other appropriate campaign data. The data for each event (e.g., impression, selection, conversion, etc.) includes a designation of the geographic location at which the event occurred. For example, if the content item was presented on a client device located in Seattle, the data for the impression can indicate that the impression occurred in Seattle. In this way, the data can be filtered based on location and metrics associated with each location can be determined.

The data management system <NUM> includes one or more front-end servers <NUM>, a data selector <NUM>, and a map user interface generator <NUM>. The data selector <NUM> and the map user interface generator <NUM> can also be implemented in one or more servers. For example, the front-end server(s) <NUM>, the data selector <NUM>, and the map user interface generator <NUM> may be implemented in one or more servers located in one or more locations (e.g., data centers). The front-end server(s) <NUM>, data selector <NUM>, and user interface generator <NUM> can communicate data between each other, for example, over a network.

The front-end server(s) <NUM> receive requests for data from client devices and provides the requested data to the client devices. The front-end server(s) <NUM> can act as an interface between client devices and the data selector <NUM> and the map user interface generator <NUM>. For example, the front-end server(s) <NUM> can forward requests for data to the data selector <NUM>. In turn, the data selector <NUM> can obtain the appropriate data from the account data storage device <NUM> and provide the data to the front-end server(s) <NUM>. The front-end server(s) <NUM> can then provide the data to the client device that submitted the request.

The front-end server(s) <NUM> can also determine whether a received request is requesting a map user interface. For example, the request may specify that it is requesting a map user interface that depicts account data for a particular region. In another example, the user of a client device may interact with a map user interface in a manner that triggers a request for another map user interface. For example, the user may zoom in or out of a map user interface to view a different region or a more detailed view of a sub-region. In this example, the request may specify the region to include in a map user interface.

If the front-end server(s) <NUM> determines that a request is requesting a map user interface, the front-end server(s) <NUM> can request a map user interface from the map user interface generator <NUM>. The map user interface generator <NUM> can generate an interactive map user interface for the requested region and provide the interactive map user interface to the front-end server(s) <NUM>. In turn, the front-end server(s) <NUM> provide the interactive map user interface to the client device.

In some implementations, the data selector <NUM> can determine whether to provide a map user interface to a client device <NUM>. For example, the data selector <NUM> may determine whether to provide a map user interface based on the data that is being provided to the client device <NUM>. The data selector <NUM> may determine to provide a map user interface if the data includes data specific to multiple different geographic locations. For example, the data may include, for each of the multiple different geographic locations, a conversion rate for a content item when the content item has been provided in the geographic location. In this example, the data selector <NUM> may determine to provide a map user interface that presents the conversion rates at their appropriate locations on the map.

The map user interface generator <NUM> generates interactive map user interfaces that present data for geographic locations depicted in the map. For example, the map user interface generator <NUM> may generate an interactive map user interface that depicts a map of a particular region specified by a request received from a client device. The interactive map user interfaces generated by the map user interface generator <NUM> can include an image of a more complex map and an index of data that corresponds to geographic locations depicted by the image. In this way, the latency in rendering the interactive map user interface at the client device <NUM> can be reduced as compared to generating the map at the client device <NUM> using code (e.g., scripts), DOM elements, and other data obtained from a mapping service. In addition, the demand on the computing resources of the client device <NUM> used to render the interactive map user interface can be reduced, thereby improving the performance of the client device <NUM>.

The map user interface generator <NUM> includes one or more map rendering servers <NUM>. The map rendering server(s) <NUM> can use a mapping service <NUM> and a map client <NUM> to render maps of geographic regions. The mapping service <NUM> can include a web mapping service that provides maps or portions of maps to map clients <NUM> in response to requests for maps. For example, the mapping service <NUM> may select map tiles, overlays, and other map data to provide to the map client <NUM> based on a request for a map of a particular region. The mapping service <NUM> can select the map tiles, overlays, and other map data from a map data storage device <NUM>.

The map client <NUM> can request maps from the mapping service <NUM>, organize map data received from the mapping service, and render the map. In some implementations, the map client <NUM> uses multiple scripts to generate a map canvas, organize map tiles on the canvas, arrange overlays over the map tiles, locate other map data on the map, and render the map, e.g., at a display or in memory. To render the map, the map client <NUM> may also load multiple DOM elements that are used by the scripts to render maps.

The map client <NUM> can interact with the mapping service <NUM> to render maps requested by client devices, e.g., the client device <NUM>. By rendering the map at the map rendering server(s) <NUM> rather than at the client device <NUM>, the map can be rendered more quickly as the map rendering server(s) have more powerful and a greater number of computing resources with which to render the map. In addition, the map client <NUM> can interact with the mapping service <NUM> without submitting requests over the Internet, further reducing the amount of time required to render a map.

The map user interface generator <NUM> also includes a map image file generator <NUM>, an index generator <NUM>, and a file compressor <NUM>. The map image file generator <NUM> can generate an image of the map rendered by the map client <NUM> and generate an image file that represents the image. For example, the map image file generator <NUM> may capture a screenshot of the rendered map and generate an image file that represents the captured image. The image file may be a Portable Network Graphics (PNG) file, a Graphics Interchange Format (GIF) file, a Joint Photographic Experts Group (JPEG) file, or another appropriate type of image file.

The map image file generator <NUM> includes a border detector <NUM> and a visual characteristic selector <NUM>. The border detector <NUM> can detect visual borders within the image of the map generated by the map image file generator <NUM>. For example, the image may depict a particular region that includes sub-regions defined by borders. In a particular example, the region may be the United States and the sub-regions may be the individual states. The border detector <NUM> can use border detecting techniques, e.g., edge detection, to detect the borders between the sub-regions.

In some implementations, the border detector <NUM> can also identify the sub-regions depicted by the image based on the borders and/or on data specifying the region depicted by the image. For example, knowing the region and the sub-regions within the image, the border detector <NUM> can determine which bordered areas of the image correspond to each sub-region. The border detector <NUM> can determine the sub-regions by comparing shapes defined by the borders in the image and known shapes for each sub-region.

The visual characteristic selector <NUM> can select a visual characteristic to associate with each sub-region depicted in the image of the map. For example, the visual characteristic may be a color (e.g., based on the RGB color model or the Red, Green, Blue, Alpha (RGBA color model)), a shading, a hatching, a color intensity, or some other appropriate visual characteristic. In some implementations, the visual characteristic selector <NUM> selects the visual characteristic for each sub-region based on data for each sub-region. For example, the interactive map user interface may be generated to present the performance of content items when the content items are presented at client devices located in the sub-regions. In this example, the visual characteristic selector <NUM> selects the visual characteristic for each sub-region based on the performance measure for each sub-region. A sub-region in which the content item has a better performance may be presented in a brighter color than a sub-region in which the content item has poorer performance.

In another example, each sub-region may be depicted in the same color, while the shade or brightness of the color varies based on the data for the sub-region. For example, each sub-region may be depicted in the color blue. The visual characteristic selector <NUM> may select a brightness or shade of blue for each sub-region based on the data for each sub-region. In yet another example, the visual characteristic of each sub-region may be selected randomly or pseudo-randomly to differentiate the different sub-regions.

The index generator <NUM> can generate an electronic index that maps locations within the image of the map to sub-regions depicted in the image. For example, the electronic index may map each x-y coordinate of the image to its corresponding sub-region. The electronic index may also map data for each sub-region to the sub-regions depicted by the image of the map. For example, the index generator <NUM> can obtain the data for the sub-regions from the data selector <NUM>. In some implementations, the electronic index maps the data for a sub-region to a unique visual characteristic (e.g., unique RGB or RGBA value) assigned to the sub-region. In this way, when a user interacts with the image at the sub-region, e.g., at one of the x-y coordinates for the sub-region or the unique visual characteristic, the data for the sub-region can be obtained from the index and presented to the user.

The file compressor <NUM> can compress the image file that represents the image of the map for faster transfer over the network <NUM> and faster rendering to a user of the client device <NUM>. In some implementations, the file compressor <NUM> compresses the image file using the unique visual characteristic selected for each sub-region depicted in the image. For example, the unique visual characteristic for each sub-region may be a unique color assigned to each sub-region. In the example, the file compressor <NUM> can compress the image file by assigning to the image area for each particular sub-region the unique color of that sub-region. In this way the image file only has to store, for each sub-region, the x-y coordinates that correspond to the sub-region and the RGB color value for the sub-region. An application of the client device <NUM> (e.g., a web browser) can use the x-y coordinates for each sub-region and the unique RGB color for each sub-region to render the image of the map at the client device <NUM>.

The file compressor <NUM> provides the compressed image file and the electronic index generated by the index generator <NUM> to the front-end server(s) <NUM>. In turn, the front-end server(s) provide the image file and the index to the client device <NUM>. The map viewer <NUM> of the client device <NUM> can then render the image of the map represented by the image file in an interactive map user interface.

The front-end server(s) <NUM> can also provide code, routines, or scripts to the client device <NUM> that causes the client device <NUM> to perform certain operations in response to certain user interactions with the image of the map. For example, a script may cause the client device <NUM> to access the electronic index to obtain and present data related to a particular sub-region in response to the user hovering a pointer (e.g., mouse cursor) over a location of the image that corresponds to the particular sub-region. For example, if a user hovers a pointer over a particular sub-region, the client device <NUM> can obtain the data for the particular sub-region from the electronic index and present the data to the user of the client device <NUM>. The client device <NUM> can identify the sub-region for which to obtain data based on a location of the user interaction with respect to the image of the map. For example, the client device <NUM> can detect the x-y coordinates of the pointer during a hover event (e.g., the pointer remaining in the same position for at least a threshold amount of time) and obtain data from the electronic index that corresponds to the detected x-y coordinates. In another example, the client device <NUM> can determine the color of the image at the location of the pointer during a hover event and obtain data from the electronic index that corresponds to the color.

In some implementations, the map user interface generator <NUM> generates two images of the map. The first image may be an image of the map rendered by the map rendering server(s). For example, the first image may depict the rendered map with any roads, waterbodies, colors for types of terrain, etc. The second image may be an image that has particular RGB colors for particular sub-regions. In this example, the second image may be an overlay over the first image, but not visible to the user of the client device <NUM>. Instead, the second image may be used to map the location of user interactions to the sub-regions depicted in the image, as described above. In this way, the map presented to the user can look the same as maps typically provided by the mapping service <NUM>, while still realizing the improvements in rendering speed and network bandwidth consumption.

In some implementations, the map user interface generator <NUM> generates additional images of maps and indexes and provides each of the additional images and indexes to the client device <NUM> in response to a request for an interactive map user interface. For example, the request may specify a particular region that includes multiple sub-regions. In this example, the map user interface generator <NUM> may generate an image of a map for each sub-region and an electronic index for each sub-region. The image of a particular sub-region may depict sub-regions of the particular sub-region. Similarly, the electronic index for a particular sub-region may include data for each sub-region of the particular sub-region.

The map user interface generator <NUM> can transmit the additional images and electronic indexes to the client device <NUM> with the original image generated in response to the request or after the original image has been transmitted to the client device <NUM>. The client device <NUM> can store the additional images and electronic indexes in a cache of the client device <NUM>. The client device <NUM> can present the additional images in response to user interaction with the interactive map user interface that includes the original image (or another image). For example, the user may select a particular sub-region depicted by the original image. In response, the client device <NUM> can obtain the image of the selected sub-region from the cache and present the image without requesting a new interactive map user interface from the data management system <NUM>. In this way, detailed maps of the sub-regions can be rendered much more quickly and network traffic can be reduced.

<FIG> is a screenshot <NUM> of example interactive map user interface <NUM>. In this example, the interactive map user interface <NUM> is presented in a web browser. In some implementations, the interactive map user interface <NUM> is presented by another application program, e.g., a native application.

The example interactive map user interface <NUM> includes an image <NUM> of a map of a particular region. In this example, the image <NUM> of the map depicts several southeastern states. Each state is a sub-region of the southeast region. Although not shown in <FIG>, each state can include a visual characteristic specific to that state. For example, the visual characteristic may be a color (e.g., based on the RGB color model), a shading, a hatching, a color intensity, or some other appropriate visual characteristic that differentiates the different states. In a particular example, the state of Georgia may be green, while the state of Alabama may be blue. In another example, each state may be the same base color. However, each state may be a different intensity, shade, or brightness of that color. For example, each state may be a different shade of blue.

The visual characteristic for each state may be based on data that corresponds to each state. For example, the interactive map user interface <NUM> may present, for each state, the number of conversions resulting from the presentation of a particular content item in that state. In this example, the area of each state may be presented in the same color with the shade of the color being based on the number of conversions for each state. For example, the state with the most conversions may be the darkest, while the state with the fewest conversions may be the lightest.

The data for each state can be stored in an electronic index that maps the data and visual characteristic to each state. When the user interacts with a state, e.g., by hovering a cursor over the state or selecting the state, the data for that state can be presented. For example, the state of Georgia is being hovered over by a cursor <NUM>. In response, the number of conversions for a content item that occurred as a result of the content item being presented on a device located in Georgia is being presented in an overlay <NUM>. The overlay <NUM> is presented over the image <NUM>. In particular, the overlay <NUM> is presented over the state of Georgia in the image <NUM>.

In some implementations, a first type of user interaction may cause presentation of data over the image <NUM> and a second type of user interaction may cause a different map to be presented in the interactive map user interface <NUM>. For example, a hover over a state may cause data for the state to be presented in an overlay over the state. In addition, a selection of the state, e.g., by clicking on the state, may cause a detailed map of the state to be presented. For example, if the state of Georgia is selected, a map of Georgia that depicts sub-regions of Georgia may be presented. The sub-regions of the state view may be counties, cities, telephone area codes, zip codes, or other ways of segmenting a larger region.

In some implementations, the level of granularity of a selection may be based on a zoom level of the interactive map user interface as the time the state was selected. For example, if the zoom level is greater than a threshold, e.g., greater than <NUM>%, the selection may be deemed to be of a county, city, postal code, or area code within the state that corresponds to the location in the image where the selection occurred. In this example, the interactive map user interface <NUM> may be updated to present an image of a map of the selected county, city, postal code, or area code. If the zoom level is less than a threshold, e.g., less than <NUM>%, the selection may be deemed to be of the entire state. In this example, the interactive map user interface <NUM> may be updated to present an image of a map of the selected state.

In some implementations, a selection of a state (or another type of user interaction), causes a user interface to be presented that enables a user to input or modify data. For example, selection of a state may cause an overlay to be presented that enables a user to modify or input a bid for a content item, select keywords for which the content item is distributed, or input another appropriate parameter. The data input to the overlay may be applied to the selected state. For example, if the user modifies a bid after selecting Georgia, the bid may be used in determining whether to present the content item on client devices located in Georgia.

In some implementations, selection of a state (or other sub-region) while the state is being presented for a particular campaign results in a toggle between active and inactive status for the campaign. For example, if the state is inactive for the campaign (e.g., content items for the campaign are not eligible to be provided to client devices located in the state), a selection of the state may toggle the status of the state to the active status for the campaign (e.g., contents items are eligible to be provided to client devices located in the state). In this example, the client device would provide, in response to the selection and to the data management system <NUM>, data specifying that the state has been toggled for the campaign. In response, the data management system <NUM> may update distribution criteria for the campaign based on the change in status for the state.

<FIG> is a flow chart of an example process <NUM> for providing an interactive map user interface. Operations of the process <NUM> can be implemented, for example, by one or more data processing apparatus, such as the data management system <NUM> of <FIG>. The process <NUM> can also be implemented by instructions stored on computer storage medium, where execution of the instructions by a data processing apparatus cause the data processing apparatus to perform the operations of the process <NUM>.

A request for presentation of an interactive map user interface is received (<NUM>). For example, a client device may submit a request for an interactive map user interface that depicts a particular geographic region. The request may also specify data related to the particular geographic region that a user of the client device would like to view. For example, the request may specify the geographic location of South America and selection data for a particular content item when the content item is presented at devices located in South America.

A map of the particular region is rendered using a mapping service (<NUM>). For example, as described above, a map client can interact with a mapping service to generate a map canvas, organize map tiles on the canvas, locate overlays over the map tiles, locate other map data on the map, and render the map, e.g., at a display or in memory. The rendering can include generating a canvas of the particular region and loading programming elements (e.g., scripts) and graphic elements (e.g., map tiles, overlays, etc.) that are used to generate the map.

An image file that represents an image of the rendered map is generated (<NUM>). For example, an image of the rendered map may be captured by taking a screenshot of a display that is presenting the rendered map. An image file that represents the captured image can then be generated. The image file may be a PNG, GIF, JPEG, or other appropriate image file format.

One or more sub-regions are detected within the image (<NUM>). For example, borders within the image may be detected using a border detection technique. The shapes between borders can then be compared to the shapes of known sub-regions of the particular geographic region to identify the sub-regions.

A different visual characteristic is assigned to each sub-region (<NUM>). For example, a different color may be assigned to each sub-region. The colors may be based on the RGB model or another appropriate computer-readable color model. In another example, the visual characteristics may be different shadings, hatchings, color intensities, or some other appropriate visual characteristic.

An electronic index is generated (<NUM>). The electronic index can map each location within the image to a corresponding sub-region that includes the location. The electronic index can also map each sub-region to data related to the sub-region. For example, the interactive map user interface may be requested to present particular data related to the sub-regions. The particular data for each sub-region can be included in the electronic index.

In some implementations, the electronic index maps x-y coordinates of each location to its corresponding sub-region. In some implementations, the electronic index maps the visual characteristics to the sub-regions. For example, the electronic index may map each sub-region to its unique RGB color.

A user interface of the client device is configured to present the image (<NUM>). For example, data that causes presentation of the image may be provided to the client device. This data can include the image file representing the image, the electronic index, and code (e.g., routines or scripts) that cause the client device to present the image. This data may cause the image to be presented with each of the different sub-regions being presented according to the different visual characteristic that corresponds to the different sub-region. For example, each sub-region may be presented in its RGB color. In some implementations, the image file that represents the image may be compressed prior to transmitting the image file to the client device. An example process for compressing an image file is illustrated in <FIG> and described below.

The client device can access the electronic index in response to user interactions with the image. For example, if the user hovers a pointer over the location of a particular sub-region, the client device can detect the location (e.g., x-y coordinates) of the hover within the image. The client device can then access the electronic index to determine the sub-region being hovered and retrieve data for the sub-region from the electronic index. The client device can then present the retrieved data in the user interface, e.g., over the sub-region that received the user interaction.

The data provided to the client device can cause the client device to perform other operations in response to certain user interactions. For example, the client device may toggle the active/inactive status of a campaign for a particular sub-region in response to a selection of the image at the particular sub-region. In this example, a script may cause the client device to transmit to a content distribution system data specifying a toggle of the active/inactive status of the particular sub-region.

In another example, a selection of a particular sub-region may cause the client device to request a map of the particular sub-region. In this example, a script may cause the client device to access its cache to determine whether an image file representing an image of the particular sub-region is stored in the cache. If so, the client device can obtain the image file from the cache and present the image of the particular sub-region in the user interface. If not, the script can cause the client device to request an image of the map of the particular sub-region.

<FIG> is a flow chart of an example process <NUM> for compressing an image. Operations of the process <NUM> can be implemented, for example, by one or more data processing apparatus, such as the file compressor <NUM> of <FIG>. The process <NUM> can also be implemented by instructions stored on computer storage medium, where execution of the instructions by a data processing apparatus cause the data processing apparatus to perform the operations of the process <NUM>.

An image file is received (<NUM>). The image file may represent an image of a particular region and may depict sub-regions of the particular region. The image file may be a PNG, GIF, JPEG, or other appropriate image file format.

Data specifying locations within the image for each of multiple different sub-regions are received (<NUM>). For example, the data may specify, for each sub-region, the x-y coordinates (or ranges of x-y coordinates) within the image that correspond to each sub-region.

A different color is identified for each sub-region (<NUM>). For example, each sub-region may be assigned a different color based on the RGB color model.

The image file is compressed (<NUM>). The image file may be compressed based on the locations of each sub-region and the color assigned to each sub-region. For example, the image file may store, for each sub-region, the color assigned to the sub-region and its corresponding locations. Compressing an image in this way can result in a much lower cost per pixel (e.g., in terms of data size of the image per display pixel) when the image includes solid colored sub-regions as each sub-region can be represented in the image file using less data than if the sub-regions were multi-colored.

By compressing the image file in this way, the image file can be more quickly transmitted over a network and using less bandwidth than a non-compressed image file. In addition, a GPU of the client device can more quickly present the compressed image file than it could present a non-compressed image file that includes detailed data of each location within the image.

Whilst embodiments are generally described with reference to a map interface for a content delivery management system, it will be appreciated that the subject matter is applicable in alternative systems where data is provided to a user and is not limited to content delivery management.

Embodiments of the subject matter described in this specification can be implemented as one or more computer programs, i.e., one or more modules of computer program instructions, encoded on computer storage medium for execution by, or to control the operation of, data processing apparatus.

Thus, particular embodiments of the subject matter have been described.

Claim 1:
A method (<NUM>) comprising:
receiving (<NUM>), from a client device (<NUM>), a request for presentation of an interactive map user interface (<NUM>, <NUM>) that depicts (i) a particular geographic region and (ii) data related to an online account for multiple different sub-regions of the particular region, the data related to the online account including performance data representing a number of user interactions with multiple content items and designating a geographic location at which the interaction occurred;
rendering (<NUM>), by one or more servers (<NUM>) and using a mapping service, a map of the particular region, the rendering comprising generating a canvas of the particular region and loading a plurality of programming elements and graphic elements that are used to generate the map;
generating (<NUM>), by the one or more servers and based on the rendered map, an image file representing an image of the rendered map;
detecting (<NUM>) one or more sub-regions within the image based at least on visual borders depicted by the image;
assigning (<NUM>) a different visual characteristic to each different sub-region within the image based on the performance data for the different sub-regions, wherein different numbers of user interactions with the content items are represented by the different visual characteristics;
generating (<NUM>) an electronic index that maps each location within the image to a corresponding sub-region that includes the location; and
configuring (<NUM>), by the one or more servers, a user interface of the client device to present (i) the image (<NUM>) with each of the different sub-regions being presented according to the different visual characteristic corresponding to the different sub-region and (ii) account data (<NUM>) related to at least one given subregion when the client device (<NUM>) detects a user interaction (<NUM>) with the given sub-region of the image (<NUM>).