Patent Grant
8799799
The present disclosure relates to systems and techniques for geographical data integration, analysis, and visualization. More specifically, the present disclosure relates to interactive maps including data objects.
Interactive geographical maps, such as web-based mapping service applications and Geographical Information Systems (GIS), are available from a number of providers. Such maps generally comprise satellite images or generic base layers overlaid by roads. Users of such systems may generally search for and view locations of a small number of landmarks, and determine directions from one location to another. In some interactive graphical maps, 3D terrain and/or 3D buildings may be visible in the interface.
The systems, methods, and devices described herein each have several aspects, no single one of which is solely responsible for its desirable attributes. Without limiting the scope of this disclosure, several non-limiting features will now be discussed briefly.
The systems, methods, and devices of the present disclosure may provide, among other features, high-performance, interactive geospatial and/or data object map capabilities in which large amounts of geographical, geospatial, and other types of data, geodata, objects, features, and/or metadata are efficiently presented to a user on a map interface. In various embodiments, an interactive geospatial map system (also referred to as an interactive data object map system) may enable rapid and deep analysis of various objects, features, and/or metadata by the user. In some embodiments, a layer ontology may be displayed to the user. In various embodiments, when the user rolls a selection cursor over an object/feature an outline of the object/feature is displayed. Selection of an object/feature may cause display of metadata associated with that object/feature. In various embodiments, the interactive data object map system may automatically generate feature/object lists and/or histograms based on selections made by the user. Various aspects of the present disclosure may enable the user to perform geosearches, generate heatmaps, and/or perform keyword searches, among other actions.
In an embodiment, a computer system is disclosed comprising an electronic data structure configured to store a plurality of features or objects, wherein each of the features or objects is associated with metadata; a computer readable medium storing software modules including computer executable instructions; one or more hardware processors in communication with the electronic data structure and the computer readable medium, and configured to execute a user interface module of the software modules in order to: display an interactive map on an electronic display of the computer system; include on the interactive map one or more features or objects, wherein the features or objects are selectable by a user of the computer system, and wherein the features or objects are accessed from the electronic data structure; receive a first input from the user selecting one or more of the included features or objects; and in response to the first input, access, from the electronic data structure, the metadata associated with each of the selected features or objects; determine one or more metadata categories based on the accessed metadata; organize the selected features or objects into one or more histograms based on the determined metadata categories and the accessed metadata; and display the one or more histograms on the electronic display.
According to an aspect, the features or objects may comprise vector data.
According to another aspect, the features or objects may comprise at least one of roads, terrain, lakes, rivers, vegetation, utilities, street lights, railroads, hotels or motels, schools, hospitals, buildings or structures, regions, transportation objects, entities, events, or documents.
According to yet another aspect, the metadata associated with the features or objects may comprise at least one of a location, a city, a county, a state, a country, an address, a district, a grade level, a phone number, a speed, a width, or other related attributes.
According to another aspect, the features or objects may be selectable by a user using a mouse and/or a touch interface.
According to yet another aspect, each histogram of the one or more histograms may be specific to a particular metadata category.
According to another aspect, each histogram of the one or more histograms may comprise a list of items of metadata specific to the particular metadata category of the histogram, wherein the list of items is organized in descending order from an item having the largest number of related objects or features to an item having the smallest number of related objects or features.
According to yet another aspect, the one or more histograms displayed on the electronic display may be displayed so as to partially overlay the displayed interactive map.
According to another aspect, the one or more hardware processors may be further configured to execute the user interface module in order to: receive a second input from the user selecting a second one or more features or objects from the one or more histograms; and in response to the second input, update the interactive map to display the second one or more features or objects on the display; and highlight the second one or more features or objects on the interactive map.
According to yet another aspect, updating the interactive map may comprise panning and/or zooming.
According to another aspect, highlighting the second one or more features may comprise at least one of outlining, changing color, bolding, or changing contrast.
According to yet another aspect, the one or more hardware processors may be further configured to execute the user interface module in order to: receive a third input from the user selecting a drill-down group of features or objects from the one or more histograms; and in response to the third input, drill-down on the selected drill-down group of features or objects by: accessing the metadata associated with each of the features or objects of the selected drill-down group; determining one or more drill-down metadata categories based on the accessed metadata associated with each of the features or objects of the selected drill-down group; organizing the features or objects of the selected drill-down group into one or more drill-down histograms based on the determined drill-down metadata categories and the accessed metadata associated with each of the features or objects of the selected drill-down group; and displaying on the interactive map the one or more drill-down histograms.
According to another aspect, the one or more hardware processors may be further configured to execute the user interface module in order to enable the user to further drill down into the one or more drill-down histograms.
According to yet another aspect, the one or more hardware processors may be further configured to execute the user interface module in order to: receive a feature or object hover over input from the user; and in response to receiving the hover over input, highlight, on the electronic display, metadata associated with the particular hovered over feature or object to the user.
According to another aspect, one or more hardware processors may be further configured to execute the user interface module in order to: receive a feature or object selection input from the user; and in response to receiving the selection input, display, on the electronic display, metadata associated with the particular selected feature or object to the user.
In another embodiment, a computer system is disclosed comprising: an electronic data structure configured to store a plurality of features or objects, wherein each of the features or objects is associated with metadata; a computer readable medium storing software modules including computer executable instructions; one or more hardware processors in communication with the electronic data structure and the computer readable medium, and configured to execute a user interface module of the software modules in order to: display an interactive map on a display of the computer system, the interactive map comprising a plurality of map tiles accessed from the electronic data structure, the map tiles each comprising an image composed of one or more vector layers; include on the interactive map a plurality of features or objects accessed from the electronic data structure, the features or objects being selectable by a user, each of the features or objects including associated metadata; receive an input from a user including at least one of a zoom action, a pan action, a feature or object selection, a layer selection, a geosearch, a heatmap, and a keyword search; and in response to the input from the user: request, from a server, updated map tiles, the updated map tiles being updated according to the input from the user; receive the updated map tiles from the server; and update the interactive map with the updated map tiles.
According to an aspect, the one or more vector layers may comprise at least one of a regions layer, a buildings/structures layer, a terrain layer, a transportation layer, or a utilities/infrastructure layer.
According to an aspect, each of the one or more vector layers may be comprised of one or more sub-vector layers.
In yet another embodiment, a computer system is disclosed comprising: one or more hardware processors in communication with the computer readable medium, and configured to execute a user interface module of the software modules in order to: display an interactive map on a display of the computer system, the interactive map comprising a plurality of map layers; determine a list of available map layers; organizing the list of available map layers according to a hierarchical layer ontology, wherein like map layers are grouped together; and display on the interactive map the hierarchical layer ontology, wherein the user may select one or more of the displayed layers, and wherein each of the available map layers is associated with one or more feature or object types.
According to an aspect, the map layers may comprise at least one of vector layers and base layers.
The following aspects of the disclosure will become more readily appreciated as the same become better understood by reference to the following detailed description, when taken in conjunction with the accompanying drawings.
In general, a high-performance, interactive data object map system (or “map system”) is disclosed in which large amounts of geographical, geospatial, and other types of data, geodata, objects, features, and/or metadata are efficiently presented to a user on a map interface. The interactive data object map system allows for rapid and deep analysis of various objects, features, and/or metadata by the user. For example, millions of data objects and/or features may be simultaneously viewed and selected by the user on the map interface. A layer ontology may be displayed to the user that allows the user to select and view particular layers. In various embodiments, when the user rolls a selection cursor over an object/feature (and/or otherwise selects the object/feature) an outline of the object/feature is displayed. Selection of an object/feature may cause display of metadata associated with that object/feature.
In an embodiment, the user may rapidly zoom in and out and/or move and pan around the map interface to variously see more or less detail, and more or fewer objects. In various embodiments, the interactive data object map system may automatically generate feature/object lists and/or histograms based on selections made by the user. In various embodiments, the user may perform geosearches (based on any selections and/or drawn shapes), generate heatmaps, and/or perform keyword searches, among other actions as described below.
In an embodiment, the interactive data object map system includes server-side computer components and/or client-side computer components. The client-side components may implement, for example, displaying map tiles, showing object outlines, allowing the user to draw shapes, and/or allowing the user to select objects/features, among other actions. The server-side components may implement, for example, composition of layers into map tiles, caching of composed map tiles and/or layers, and/or providing object/feature metadata, among other actions. Such functions may be distribution in any other manner. In an embodiment, object/feature outlines and/or highlighting are accomplished on the client-side through the use of a UTF grid.
In order to facilitate an understanding of the systems and methods discussed herein, a number of terms are defined below. The terms defined below, as well as other terms used herein, should be construed to include the provided definitions, the ordinary and customary meaning of the terms, and/or any other implied meaning for the respective terms. Thus, the definitions below do not limit the meaning of these terms, but only provide exemplary definitions.
Ontology: A hierarchical arrangement and/or grouping of data according to similarities and differences. The present disclosure describes two ontologies. The first relates to the arrangement of vector layers consisting of map and object data as used by the interactive data object map system (as described below with reference to
Database: A broad term for any data structure for storing and/or organizing data, including, but not limited to, relational databases (Oracle database, mySQL database, etc.), spreadsheets, XML files, and text file, among others.
Data Object, Object, or Feature: A data container for information representing specific things in the world that have a number of definable properties. For example, a data object can represent an entity such as a person, a place, an organization, a market instrument, or other noun. A data object can represent an event that happens at a point in time or for a duration. A data object can represent a document or other unstructured data source such as an e-mail message, a news report, or a written paper or article. Each data object may be associated with a unique identifier that uniquely identifies the data object. The object's attributes (e.g. metadata about the object) may be represented in one or more properties. For the purposes of the present disclosure, the terms “feature,” “data object,” and “object” may be used interchangeably to refer to items displayed on the map interface of the interactive data object map system, and/or otherwise accessible to the user through the interactive data object map system. Features/objects may generally include, but are not limited to, roads, terrain (such as hills, mountains, rivers, and vegetation, among others), street lights (which may be represented by a streetlight icon), railroads, hotels/motels (which may be represented by a bed icon), schools (which may be represented by a parent-child icon), hospitals, other types of buildings or structures, regions, transportation objects, and other types of entities, events, and documents, among others. Objects displayed on the map interface generally comprise vector data, although other types of data may also be displayed. Objects generally have associated metadata and/or properties.
Object Type: Type of a data object (e.g., Person, Event, or Document). Object types may be defined by an ontology and may be modified or updated to include additional object types. An object definition (e.g., in an ontology) may include how the object is related to other objects, such as being a sub-object type of another object type (e.g. an agent may be a sub-object type of a person object type), and the properties the object type may have.
Properties: Also referred to as “metadata,” includes attributes of a data object/feature. At a minimum, each property/metadata of a data object has a type (such as a property type) and a value or values. Properties/metadata associated with features/objects may include any information relevant to that feature/object. For example, metadata associated with a school object may include an address (for example, 123 S. Orange Street), a district (for example, 509c), a grade level (for example, K-6), and/or a phone number (for example, 800-0000), among other items of metadata. In another example, metadata associated with a road object may include a speed (for example, 25 mph), a width (for example, 2 lanes), and/or a county (for example, Arlington), among other items of metadata.
Property Type: The data type of a property, such as a string, an integer, or a double. Property types may include complex property types, such as a series data values associated with timed ticks (e.g. a time series), etc.
Property Value: The value associated with a property, which is of the type indicated in the property type associated with the property. A property may have multiple values.
Link: A connection between two data objects, based on, for example, a relationship, an event, and/or matching properties. Links may be directional, such as one representing a payment from person A to B, or bidirectional.
Link Set: Set of multiple links that are shared between two or more data objects.
Embodiments of the disclosure will now be described with reference to the accompanying Figures, wherein like numerals refer to like elements throughout. The terminology used in the description presented herein is not intended to be interpreted in any limited or restrictive manner, simply because it is being utilized in conjunction with a detailed description of certain specific embodiments of the disclosure. Furthermore, embodiments of the disclosure may include several novel features, no single one of which is solely responsible for its desirable attributes or which is essential to practicing the embodiments of the disclosure herein described.
The map interface 100 of
In general, the user interface of
The map interface 100 includes various highlighted features 122 and feature icons. For example, the map interface 100 includes roads, buildings and structures, utilities, lakes, rivers, vegetation, and railroads, among other features. The user may interact with the map interface 100 by, for example, rolling over and/or clicking on various features. In one embodiment, rolling over and/or placing the mouse pointer over a feature causes the feature to be outlined and/or otherwise highlighted. Additionally, the name of the feature and/or other information about the feature may be shown in the feature information box 114.
The user of the map system may interact with the user interface of
In an embodiment, the user may select one or more of the base layers which may be used during composition of the map tiles. For example, selection of the overhead imagery base layer will produce map tiles in which the underlying map tile imagery is made up of recent aerial imagery. Similarly, selection of the topographic base layer will produce map tiles in which the underlying map tile imagery includes topographic map imagery.
Further, in an embodiment, the user may select one or more of the vector layers which may be used during composition of the map tiles. For example, selecting the transportation layer results in transportation-related objects and/or features being displayed on the map tiles. Transportation-related features may include, for example, roads, railroads, street signs, and/or street lights, among others. Examples of transportation-related features may be seen in the user interface of
In an embodiment, the user of the map system may create and save map layers. These saved map layers may be listed as user layers in the layers window 202.
In an embodiment, the user of the map system may select one or more of the layers and/or sub-layers of the layer ontology. As shown in
In an embodiment, additional hierarchical levels of layers may be displayed to the user. For example, the vector layers window 206 may include sub-sub-layers (for example, the education sub-layer may be divided into elementary schools, secondary schools, and post-secondary schools). Alternatively, fewer hierarchical levels may be displayed to the user.
In an embodiment, each of the vector layers shown in the vector layers window 206 may be made up of many layers of map vector data. In this embodiment, the map system may advantageously generate a simplified layer ontology, such as the one shown in 206. The simplified layer ontology allows the user to easily select layers of interest from a reduced number of layers, rather than a large number of discrete layers. As described above, vector layers may contain data regarding associated features and/or objects. Thus, features visible in the map interface correspond to the currently active/selected layers. In an embodiment, the layer ontology may have an arbitrary depth.
Feature histogram 304 is shown in a selection window included in the user interface of
In an embodiment, the user of the map system may select a subset of the selected features for further analysis and/or histogram generation. For example, the user may select a subset comprising selected objects belonging to the road category by, for example, clicking on the roads item 308. This selection may result in “drilling down” to histograms of that subset of features, as shown in
In an embodiment, items selected in the feature histogram are correspondingly highlighted in the map interface of the map system. For example, in the map interface of
In
In various embodiments, the user of the map system may select either the list of features, or the feature histogram, of the selection window to view information about the selected features.
In various embodiments, the user may select a feature in order to view a feature information window. The feature information window may include, for example, metadata associated with the selected feature. For example, the user may select a building feature, resulting in a display of information associated with that building feature such as the building size, the building name, and/or the building address or location, among others. Metadata associated with features/objects may include any information relevant to that feature/object. For example, metadata associated with a school may include an address (for example, 123 S. Orange Street), a district (for example, 509c), a grade level (for example, K-6), and/or a phone number (for example, 800-0000), among other items of metadata. In an embodiment, a history of the object, changes made to the object, and/or user notes related to the object, among other items, may be displayed. In an embodiment, a user may edit metadata associated with a selected feature.
In
In an embodiment, the user of the map system may perform a search by clicking and/or touching a search button. The map system may then perform a search of an object database for any objects matching the criteria specified in the geosearch. For example, in the example of
In the map system a heatmap may be generated on any object type, and/or on multiple object types. In an embodiment, different heatmap radiuses may be set for different object types. For example, the user may generate a heatmap in which streetlights have a 20 m radius, while hospitals have a 500 m radius. In an embodiment, the heatmap may be generated based on arbitrary shapes. For example, rather than a circular-based heatmap, the heatmap may be rectangular-based or ellipse-based. In an embodiment, the heatmap may be generated based on error ellipses and/or tolerance ellipses. A heatmap based on error ellipses may be advantageous when the relevant objects have associated error regions. For example, when a location of an object is uncertain, or multiple datapoints associated with an object are available, an error ellipse may help the user determine the actual location of the object.
Contiguous regions of characters in the UTF grid indicate the bounds of a particular feature, and may be used by the client-side components to provide the feature highlighting and/or outlining. For example, when a user hovers a mouse pointer over a feature on a map tile, the map system determines the character and portion of the UTF grid associated with the pixel hovered over, draws a feature outline based on the UTF grid, and may additionally access metadata associated with the feature based on the feature identifier associated with the feature. In an embodiment, the UTF grid is sent to the client-side components in a JSON (JavaScript Object Notation) format.
At block 602, the map system provides a user interface (for example, the user interface of
Inputs received from the user may include, for example, hovering over, rolling over, and/or touching and object in the user interface (606); filling out a text field (614); drawing a shape in the user interface (608), and/or drawing a selection box and/or shape in the user interface (610); among other actions or inputs as described above.
At block 612, any of inputs 606, 614, 608, and 610 may cause the map system to perform client-side actions to update the user interface. For example, hovering over an object (606) may result in the client-side components of the map system to access the UTF grid, determine the boundaries of the object, and draw an outline around the hovered-over object. In another example, filling out a text field (614) may include the user inputting data into the map system. In this example, the user may input geographic coordinates, metadata, and/or other types of data to the map system. These actions may result in, for example, the client-side components of the map system storing the inputted data and/or taking an action based on the inputted data. For example, the user inputting coordinates may result in the map interface being updated to display the inputted information, such as an inputted name overlaying a particular object. In yet another example, the actions/inputs of drawing a shape (608) and/or drawing a selection (610) may result in the client-side components of the map system to update the user interface with colored and/or highlighted shapes (see, for example,
In an embodiment, one or more blocks in
At block 620, the client-side components of the map system detect that the user is hovering over and/or touching an object in the user interface. At block 622, and as described above, the client-side components may access the UTF grid to determine the feature identifier and object boundaries associated with the hovered-over object. Then, at block 624, the client-side components may render the feature shape on the image or map interface. The feature shape may be rendered as an outline and/or other highlighting.
At block 636, the client-side components detect whether the user has selected the object. Objects may be selected, for example, if the user clicks on the object and or touches the object. If the user has selected the object, then at block 628, the client-side components query the server-side components to retrieve metadata associated with the selected object. In an embodiment, querying of the server-side components may include transmitting the feature identifier associated with the selected object to the server, the server retrieving from a database the relevant metadata, and the server transmitting the retrieved metadata back to the client-side components.
At block 630, the metadata is received by the client-side components and displayed to the user. For example, the metadata associated with the selected object may be displayed to the user in the user interface in a dedicated metadata window, among other possibilities.
In an embodiment, one or more blocks in
Server-side operations of the map system may include composing and updating the map tiles that make up the map interface. For example, when the user changes the selection of the base layer and/or one or more of the vector layers, the map tiles are re-composed and updated in the map interface to reflect the user's selection. Selection of objects resulting in highlighting of those objects may also involve re-composition of the map tiles. Further, UTF grids may be generated by the server-side components for each map tile composed.
At block 702, the user interface is provided to the user. At block 704 an input from the user is received. Inputs received from the user that may result in server-side operations may include, for example, an object selection (706), a change in layer selection (708), a geosearch (710), generating a heatmap (712), searching from the search box (714), and/or panning or zooming the map interface, among others.
At block 716, the client-side components of the map system may query the server-side components in response to any of inputs 706, 708, 710, 712, and 714 from the user. The server-side components then update and re-compose the map tiles and UTF grids of the map interface in accordance with the user input (as described below in reference to
At block 718, the client-side components receive the updated map tile information from the server, and at block 720 the user interface is updated with the received information.
In an embodiment, additional information and/or data, in addition to updated map tiles, may be transmitted to the client-side components from the server-side components. For example, object metadata may be transmitted in response to a user selecting an object.
In an embodiment, one or more blocks in
At block 730, a query is received by the server-side components from the client-side components. Such a query may originate, for example, at block 716 of
At block 734, the map system determines whether the layers necessary to compose the requested map tiles are cached. For example, when a layer is selected by the user, that layer may be composed by the map system and placed in a memory of the server-side components for future retrieval. Caching of composed layers may obviate the need for recomposing those layers later, which advantageously may save time and/or processing power.
If the required layers are cached, then at block 740 the layers are composed into the requested map tiles and, at block 742, transmitted to the client-side components.
When the required layers are not cached, at block 736, the server-side components calculate and/or compose the requested layer and or layers, and may then, at block 738, optionally cache the newly composed layers for future retrieval. Then, at blocks 740 and 742, the layers are composed into map tiles and provided to the client-side components.
In an embodiment, entire map tiles may be cached by the server-side components. In an embodiment, the size and/or quality of the map tiles that make up that map interface may be selected and/or dynamically selected based on at least one of: the bandwidth available for transmitting the map tiles to the client-side components, the size of the map interface, and/or the complexity of the layer composition, among other factors. In an embodiment, the map tiles comprise images, for example, in one or more of the following formats: PNG, GIF, JPEG, TIFF, BMP, and/or any other type of appropriate image format.
In an embodiment, the layer and object data composed into layers and map tiles comprises vector data. The vector data (for example, object data) may include associated metadata, as described above. In an embodiment, the vector, layer, and/or object data and associated metadata may originate from one or more databases and/or electronic data stores.
In an embodiment, one or more blocks in
In an embodiment, the map system may display more than 50 million selectable features to a user simultaneously. In an embodiment, the map system may support tens or hundreds of concurrent users accessing the same map and object data. In an embodiment, map and object data used by the map system may be mirrored and/or spread across multiple computers, servers, and/or server-side components.
In an embodiment, rather than updating the map tiles to reflect a selection by the user of one or more objects, the map system may show an approximation of the selection to the user based on client-side processing.
In an embodiment, a user may drag and drop files, for example, vector data and/or vector layers, onto the user interface of the map system, causing the map system to automatically render the file in the map interface.
In an embodiment, icons and/or styles associated with various objects in the map interface may be updated and/or changed by the user. For example, the styles of the various objects may be specified in or by a style data file. The style data file may be formatted according to a particular format or standard readable by the map system. In an embodiment, the style data file is formatted according to the JSON format standard. The user may thus change the look of the objects and shapes rendered in the map interface of the map system by changing the style data file. The style data file may further define the looks for object and terrain (among other items and data) at various zoom levels.
In an embodiment, objects, notes, metadata, and/or other types of data may be added to the map system by the user through the user interface. In an embodiment, user added information may be shared between multiple users of the map system. In an embodiment, a user of the map system may add annotations and shapes to the map interface that may be saved and shared with other users. In an embodiment, a user of the map system may share a selection of objects with one or more other users.
In an embodiment, the user interface of the map system may include a timeline window. The timeline window may enable the user to view objects and layers specific to particular moments in time and/or time periods. In an embodiment, the user may view tolerance ellipses overlaid on the map interface indicating the likely position of an object across a particular time period.
In an embodiment, the map system may include elevation profiling. Elevation profiling may allow a user of the system to determine the elevation along a path on the map interface, to perform a viewshed analysis (determine objects and/or terrain viewable from a particular location), to perform a reverse-viewshed analysis (for a particular location, determine objects and/or terrain that may view the location), among others.
In an embodiment, vector data, object data, metadata, and/or other types of data may be prepared before it is entered into or accessed by the map system. For example, the data may be converted from one format to another, may be crawled for common items of metadata, and/or may be prepared for application of a style file or style information, among other action. In an embodiment, a layer ontology may be automatically generated based on a group of data. In an embodiment, the map system may access common data sources available on the Internet, for example, road data available from openstreetmap.org.
In an embodiment, roads shown in the map interface are labeled with their names, and buildings are rendered in faux-3D to indicate the building heights. In an embodiment, Blue Force Tracking may be integrated into the map system as a layer with the characteristics of both a static vector layer and a dynamic selection layer. A Blue Force layer may enable the use of the map system for live operational analysis. In an embodiment, the map system may quickly render detailed chloropleths or heatmaps with minimal data transfer. For example, the system may render a chloropleth with a property value on the individual shapes of the properties themselves, rather than aggregating this information on a county or zip code level.
Advantageously, the map system displays many items of data, objects, features, and/or layers in a single map interface. A user may easily interact with things on the map and gather information by hovering over or selecting features, even though those features may not be labeled. The user may select features, may “drill down” on a particular type of feature (for example, roads), may view features through histograms, may use histograms to determine common characteristics (for example, determine the most common speed limit), and/or may determine correlations among features (for example, see that slower speed limit areas are centered around schools). Further, the map system may be useful in many different situations. For example, the system may be useful to operational planners and/or disaster relief personnel.
Additionally, the map system accomplishes at least three core ideas: providing a robust and fast back-end (server-side) renderer, keeping data on the back-end, and only transferring the data necessary to have interactivity. In one embodiment, the primary function of the server-side components is rendering map tiles. The server is capable of drawing very detailed maps with a variety of styles that can be based on vector metadata. Rendered map tiles for a vector layer are cached, and several of these layer tiles are drawn on top of one another to produce the final tile that is sent to the client-side browser. Map tile rendering is fast enough for displaying dynamic tiles for selection and highlight to the user. Server-side operations allow for dynamic selections of very large numbers of features, calculation of the histogram, determining the number of items shown and/or selected, and drawing the selection, for example. Further, the heatmap may include large numbers of points without incurring the cost of transferring those points to the client-side browser. Additionally, transferring only as much data as necessary to have interactivity enables quick server rendering of dynamic selections and vector layers. On the other hand, highlighting hovered-over features may be performed client-side nearly instantaneously, and provides useful feedback that enhances the interactivity of the map system. In an embodiment, to avoid transferring too much geometric data, the geometries of objects (in the map tiles and UTF grid) are down-sampled depending on how zoomed in the user is to the map interface. Thus, map tiles may be rendered and presented to a user of the map system in a dynamic and useable manner.
Object Centric Data Model
To provide a framework for the following discussion of specific systems and methods described above and below, an example database system 1210 using an ontology 1205 will now be described. This description is provided for the purpose of providing an example and is not intended to limit the techniques to the example data model, the example database system, or the example database system's use of an ontology to represent information.
In one embodiment, a body of data is conceptually structured according to an object-centric data model represented by ontology 1205. The conceptual data model is independent of any particular database used for durably storing one or more database(s) 1209 based on the ontology 1205. For example, each object of the conceptual data model may correspond to one or more rows in a relational database or an entry in Lightweight Directory Access Protocol (LDAP) database, or any combination of one or more databases.
Different types of data objects may have different property types. For example, a “Person” data object might have an “Eye Color” property type and an “Event” data object might have a “Date” property type. Each property 1203 as represented by data in the database system 1210 may have a property type defined by the ontology 1205 used by the database 1205.
Objects may be instantiated in the database 1209 in accordance with the corresponding object definition for the particular object in the ontology 1205. For example, a specific monetary payment (e.g., an object of type “event”) of US$30.00 (e.g., a property of type “currency”) taking place on Mar. 27, 2009 (e.g., a property of type “date”) may be stored in the database 1209 as an event object with associated currency and date properties as defined within the ontology 1205.
The data objects defined in the ontology 1205 may support property multiplicity. In particular, a data object 1201 may be allowed to have more than one property 1203 of the same property type. For example, a “Person” data object might have multiple “Address” properties or multiple “Name” properties.
Each link 1202 represents a connection between two data objects 1201. In one embodiment, the connection is either through a relationship, an event, or through matching properties. A relationship connection may be asymmetrical or symmetrical. For example, “Person” data object A may be connected to “Person” data object B by a “Child Of” relationship (where “Person” data object B has an asymmetric “Parent Of” relationship to “Person” data object A), a “Kin Of” symmetric relationship to “Person” data object C, and an asymmetric “Member Of” relationship to “Organization” data object X. The type of relationship between two data objects may vary depending on the types of the data objects. For example, “Person” data object A may have an “Appears In” relationship with “Document” data object Y or have a “Participate In” relationship with “Event” data object E. As an example of an event connection, two “Person” data objects may be connected by an “Airline Flight” data object representing a particular airline flight if they traveled together on that flight, or by a “Meeting” data object representing a particular meeting if they both attended that meeting. In one embodiment, when two data objects are connected by an event, they are also connected by relationships, in which each data object has a specific relationship to the event, such as, for example, an “Appears In” relationship.
As an example of a matching properties connection, two “Person” data objects representing a brother and a sister, may both have an “Address” property that indicates where they live. If the brother and the sister live in the same home, then their “Address” properties likely contain similar, if not identical property values. In one embodiment, a link between two data objects may be established based on similar or matching properties (e.g., property types and/or property values) of the data objects. These are just some examples of the types of connections that may be represented by a link and other types of connections may be represented; embodiments are not limited to any particular types of connections between data objects. For example, a document might contain references to two different objects. For example, a document may contain a reference to a payment (one object), and a person (a second object). A link between these two objects may represent a connection between these two entities through their co-occurrence within the same document.
Each data object 1201 can have multiple links with another data object 1201 to form a link set 1204. For example, two “Person” data objects representing a husband and a wife could be linked through a “Spouse Of” relationship, a matching “Address” property, and one or more matching “Event” properties (e.g., a wedding). Each link 1202 as represented by data in a database may have a link type defined by the database ontology used by the database.
In accordance with the discussion above, the example ontology 1205 comprises stored information providing the data model of data stored in database 1209, and the ontology is defined by one or more object types 1310, one or more property types 1316, and one or more link types 1330. Based on information determined by the parser 1302 or other mapping of source input information to object type, one or more data objects 1201 may be instantiated in the database 209 based on respective determined object types 1310, and each of the objects 1201 has one or more properties 1203 that are instantiated based on property types 1316. Two data objects 1201 may be connected by one or more links 1202 that may be instantiated based on link types 1330. The property types 1316 each may comprise one or more data types 1318, such as a string, number, etc. Property types 1316 may be instantiated based on a base property type 1320. For example, a base property type 1320 may be “Locations” and a property type 1316 may be “Home.”
In an embodiment, a user of the system uses an object type editor 1324 to create and/or modify the object types 1310 and define attributes of the object types. In an embodiment, a user of the system uses a property type editor 1326 to create and/or modify the property types 1316 and define attributes of the property types. In an embodiment, a user of the system uses link type editor 1328 to create the link types 1330. Alternatively, other programs, processes, or programmatic controls may be used to create link types and property types and define attributes, and using editors is not required.
In an embodiment, creating a property type 1316 using the property type editor 1326 involves defining at least one parser definition using a parser editor 1322. A parser definition comprises metadata that informs parser 1302 how to parse input data 1300 to determine whether values in the input data can be assigned to the property type 1316 that is associated with the parser definition. In an embodiment, each parser definition may comprise a regular expression parser 1304A or a code module parser 1304B. In other embodiments, other kinds of parser definitions may be provided using scripts or other programmatic elements. Once defined, both a regular expression parser 1304A and a code module parser 1304B can provide input to parser 1302 to control parsing of input data 1300.
Using the data types defined in the ontology, input data 1300 may be parsed by the parser 1302 determine which object type 1310 should receive data from a record created from the input data, and which property types 1316 should be assigned to data from individual field values in the input data. Based on the object-property mapping 1301, the parser 1302 selects one of the parser definitions that is associated with a property type in the input data. The parser parses an input data field using the selected parser definition, resulting in creating new or modified data 1303. The new or modified data 1303 is added to the database 1209 according to ontology 205 by storing values of the new or modified data in a property of the specified property type. As a result, input data 1300 having varying format or syntax can be created in database 1209. The ontology 1205 may be modified at any time using object type editor 1324, property type editor 1326, and link type editor 1328, or under program control without human use of an editor. Parser editor 1322 enables creating multiple parser definitions that can successfully parse input data 1300 having varying format or syntax and determine which property types should be used to transform input data 300 into new or modified input data 1303.
The properties, objects, and links (e.g. relationships) between the objects can be visualized using a graphical user interface (GUI). For example,
For example, in
Relationships between data objects may be stored as links, or in some embodiments, as properties, where a relationship may be detected between the properties. In some cases, as stated above, the links may be directional. For example, a payment link may have a direction associated with the payment, where one person object is a receiver of a payment, and another person object is the payer of payment.
In various embodiments, data objects may further include geographical metadata and/or links. Such geographical metadata may be accessed by the interactive data object map system for displaying objects and features on the map interface (as described above).
In addition to visually showing relationships between the data objects, the user interface may allow various other manipulations. For example, the objects within database 1108 may be searched using a search interface 1450 (e.g., text string matching of object properties), inspected (e.g., properties and associated data viewed), filtered (e.g., narrowing the universe of objects into sets and subsets by properties or relationships), and statistically aggregated (e.g., numerically summarized based on summarization criteria), among other operations and visualizations. Additionally, as described above, objects within database 1108 may be searched, accessed, and implemented in the map interface of the interactive data object map system via, for example, a geosearch and/or radius search.
Implementation Mechanisms
According to an embodiment, the interactive data object map system and other methods and techniques described herein are implemented by one or more special-purpose computing devices. The special-purpose computing devices may be hard-wired to perform the techniques, or may include digital electronic devices such as one or more application-specific integrated circuits (ASICs) or field programmable gate arrays (FPGAs) that are persistently programmed to perform the techniques, or may include one or more general purpose hardware processors programmed to perform the techniques pursuant to program instructions in firmware, memory, other storage, or a combination. Such special-purpose computing devices may also combine custom hard-wired logic, ASICs, or FPGAs with custom programming to accomplish the techniques. The special-purpose computing devices may be desktop computer systems, server computer systems, portable computer systems, handheld devices, networking devices or any other device or combination of devices that incorporate hard-wired and/or program logic to implement the techniques.
Computing device(s) are generally controlled and coordinated by operating system software, such as iOS, Android, Chrome OS, Windows XP, Windows Vista, Windows 7, Windows 8, Windows Server, Windows CE, Unix, Linux, SunOS, Solaris, iOS, Blackberry OS, VxWorks, or other compatible operating systems. In other embodiments, the computing device may be controlled by a proprietary operating system. Conventional operating systems control and schedule computer processes for execution, perform memory management, provide file system, networking, I/O services, and provide a user interface functionality, such as a graphical user interface (“GUI”), among other things.
For example,
Computer system 800 also includes a main memory 806, such as a random access memory (RAM), cache and/or other dynamic storage devices, coupled to bus 802 for storing information and instructions to be executed by processor 804. Main memory 806 also may be used for storing temporary variables or other intermediate information during execution of instructions to be executed by processor 804. Such instructions, when stored in storage media accessible to processor 804, render computer system 800 into a special-purpose machine that is customized to perform the operations specified in the instructions.
Computer system 800 further includes a read only memory (ROM) 808 or other static storage device coupled to bus 802 for storing static information and instructions for processor 804. A storage device 810, such as a magnetic disk, optical disk, or USB thumb drive (Flash drive), etc., is provided and coupled to bus 802 for storing information and instructions.
Computer system 800 may be coupled via bus 802 to a display 812, such as a cathode ray tube (CRT), LCD display, or touch screen display, for displaying information to a computer user and/or receiving input from the user. An input device 814, including alphanumeric and other keys, is coupled to bus 802 for communicating information and command selections to processor 804. Another type of user input device is cursor control 816, such as a mouse, a trackball, or cursor direction keys for communicating direction information and command selections to processor 804 and for controlling cursor movement on display 812. This input device typically has two degrees of freedom in two axes, a first axis (e.g., x) and a second axis (e.g., y), that allows the device to specify positions in a plane. In some embodiments, the same direction information and command selections as cursor control may be implemented via receiving touches on a touch screen without a cursor.
Computing system 800 may include a user interface module, and/or various other types of modules to implement a GUI, a map interface, and the various other aspects of the interactive data object map system. The modules may be stored in a mass storage device as executable software codes that are executed by the computing device(s). This and other modules may include, by way of example, components, such as software components, object-oriented software components, class components and task components, processes, functions, attributes, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuitry, data, databases, data structures, tables, arrays, and variables.
In general, the word “module,” as used herein, refers to logic embodied in hardware or firmware, or to a collection of software instructions, possibly having entry and exit points, written in a programming language, such as, for example, Java, Lua, C or C++. A software module may be compiled and linked into an executable program, installed in a dynamic link library, or may be written in an interpreted programming language such as, for example, BASIC, Perl, or Python. It will be appreciated that software modules may be callable from other modules or from themselves, and/or may be invoked in response to detected events or interrupts. Software modules configured for execution on computing devices may be provided on a computer readable medium, such as a compact disc, digital video disc, flash drive, magnetic disc, or any other tangible medium, or as a digital download (and may be originally stored in a compressed or installable format that requires installation, decompression or decryption prior to execution). Such software code may be stored, partially or fully, on a memory device of the executing computing device, for execution by the computing device. Software instructions may be embedded in firmware, such as an EPROM. It will be further appreciated that hardware modules may be comprised of connected logic units, such as gates and flip-flops, and/or may be comprised of programmable units, such as programmable gate arrays or processors. The modules or computing device functionality described herein are preferably implemented as software modules, but may be represented in hardware or firmware. Generally, the modules described herein refer to logical modules that may be combined with other modules or divided into sub-modules despite their physical organization or storage
Computer system 800 may implement the techniques described herein using customized hard-wired logic, one or more ASICs or FPGAs, firmware and/or program logic which in combination with the computer system causes or programs computer system 800 to be a special-purpose machine. According to one embodiment, the techniques herein are performed by computer system 800 in response to processor(s) 804 executing one or more sequences of one or more modules and/or instructions contained in main memory 806. Such instructions may be read into main memory 806 from another storage medium, such as storage device 810. Execution of the sequences of instructions contained in main memory 806 causes processor(s) 804 to perform the process steps described herein. In alternative embodiments, hard-wired circuitry may be used in place of or in combination with software instructions.
The term “non-transitory media,” and similar terms, as used herein refers to any media that store data and/or instructions that cause a machine to operate in a specific fashion. Such non-transitory media may comprise non-volatile media and/or volatile media. Non-volatile media includes, for example, optical or magnetic disks, such as storage device 810. Volatile media includes dynamic memory, such as main memory 806. Common forms of non-transitory media include, for example, a floppy disk, a flexible disk, hard disk, solid state drive, magnetic tape, or any other magnetic data storage medium, a CD-ROM, any other optical data storage medium, any physical medium with patterns of holes, a RAM, a PROM, and EPROM, a FLASH-EPROM, NVRAM, any other memory chip or cartridge, and networked versions of the same.
Non-transitory media is distinct from but may be used in conjunction with transmission media. Transmission media participates in transferring information between nontransitory media. For example, transmission media includes coaxial cables, copper wire and fiber optics, including the wires that comprise bus 802. Transmission media can also take the form of acoustic or light waves, such as those generated during radio-wave and infra-red data communications.
Various forms of media may be involved in carrying one or more sequences of one or more instructions to processor 804 for execution. For example, the instructions may initially be carried on a magnetic disk or solid state drive of a remote computer. The remote computer can load the instructions and/or modules into its dynamic memory and send the instructions over a telephone line using a modem. A modem local to computer system 800 can receive the data on the telephone line and use an infra-red transmitter to convert the data to an infra-red signal. An infra-red detector can receive the data carried in the infra-red signal and appropriate circuitry can place the data on bus 802. Bus 802 carries the data to main memory 806, from which processor 804 retrieves and executes the instructions. The instructions received by main memory 806 may optionally be stored on storage device 810 either before or after execution by processor 804.
Computer system 800 also includes a communication interface 818 coupled to bus 802. Communication interface 818 provides a two-way data communication coupling to a network link 820 that is connected to a local network 822. For example, communication interface 818 may be an integrated services digital network (ISDN) card, cable modem, satellite modem, or a modem to provide a data communication connection to a corresponding type of telephone line. As another example, communication interface 818 may be a local area network (LAN) card to provide a data communication connection to a compatible LAN (or WAN component to communicated with a WAN). Wireless links may also be implemented. In any such implementation, communication interface 818 sends and receives electrical, electromagnetic or optical signals that carry digital data streams representing various types of information.
Network link 820 typically provides data communication through one or more networks to other data devices. For example, network link 820 may provide a connection through local network 822 to a host computer 824 or to data equipment operated by an Internet Service Provider (ISP) 826. ISP 826 in turn provides data communication services through the world wide packet data communication network now commonly referred to as the “Internet” 828. Local network 822 and Internet 828 both use electrical, electromagnetic or optical signals that carry digital data streams. The signals through the various networks and the signals on network link 820 and through communication interface 818, which carry the digital data to and from computer system 800, are example forms of transmission media.
Computer system 800 can send messages and receive data, including program code, through the network(s), network link 820 and communication interface 818. In the Internet example, a server 830 might transmit a requested code for an application program through Internet 828, ISP 826, local network 822 and communication interface 818. Server-side components of the interactive data object map system described above (for example, with reference to
The computer system 800, on the other hand, may implement the client-side components of the map system as described above (for example, with reference to
In an embodiment, the map system may be accessible by the user through a web-based viewer, such as a web browser. In this embodiment, the map interface may be generated by the server 830 and/or the computer system 800 and transmitted to the web browser of the user. The user may then interact with the map interface through the web-browser. In an embodiment, the computer system 800 may comprise a mobile electronic device, such as a cell phone, smartphone, and/or tablet. The map system may be accessible by the user through such a mobile electronic device, among other types of electronic devices.
Each of the processes, methods, and algorithms described in the preceding sections may be embodied in, and fully or partially automated by, code modules executed by one or more computer systems or computer processors comprising computer hardware. The processes and algorithms may be implemented partially or wholly in application-specific circuitry.
The various features and processes described above may be used independently of one another, or may be combined in various ways. All possible combinations and subcombinations are intended to fall within the scope of this disclosure. In addition, certain method or process blocks may be omitted in some implementations. The methods and processes described herein are also not limited to any particular sequence, and the blocks or states relating thereto can be performed in other sequences that are appropriate. For example, described blocks or states may be performed in an order other than that specifically disclosed, or multiple blocks or states may be combined in a single block or state. The example blocks or states may be performed in serial, in parallel, or in some other manner. Blocks or states may be added to or removed from the disclosed example embodiments. The example systems and components described herein may be configured differently than described. For example, elements may be added to, removed from, or rearranged compared to the disclosed example embodiments.
Conditional language, such as, among others, “can,” “could,” “might,” or “may,” unless specifically stated otherwise, or otherwise understood within the context as used, is generally intended to convey that certain embodiments include, while other embodiments do not include, certain features, elements and/or steps. Thus, such conditional language is not generally intended to imply that features, elements and/or steps are in any way required for one or more embodiments or that one or more embodiments necessarily include logic for deciding, with or without user input or prompting, whether these features, elements and/or steps are included or are to be performed in any particular embodiment.
Any process descriptions, elements, or blocks in the flow diagrams described herein and/or depicted in the attached Figures should be understood as potentially representing modules, segments, or portions of code which include one or more executable instructions for implementing specific logical functions or steps in the process. Alternate implementations are included within the scope of the embodiments described herein in which elements or functions may be deleted, executed out of order from that shown or discussed, including substantially concurrently or in reverse order, depending on the functionality involved, as would be understood by those skilled in the art.
It should be emphasized that many variations and modifications may be made to the above-described embodiments, the elements of which are to be understood as being among other acceptable examples. All such modifications and variations are intended to be included herein within the scope of this disclosure. The foregoing description details certain embodiments of the invention. It will be appreciated, however, that no matter how detailed the foregoing appears in text, the invention can be practiced in many ways. As is also stated above, it should be noted that the use of particular terminology when describing certain features or aspects of the invention should not be taken to imply that the terminology is being re-defined herein to be restricted to including any specific characteristics of the features or aspects of the invention with which that terminology is associated. The scope of the invention should therefore be construed in accordance with the appended claims and any equivalents thereof.
This application claims a priority benefit under 35 U.S.C. §119 to U.S. Provisional Patent Application No. 61/820,608, filed on May 7, 2013, and titled “INTERACTIVE DATA OBJECT MAP,” which is hereby incorporated by reference herein in its entirety.
| Number | Name | Date | Kind |
|---|---|---|---|
| 4899161 | Morin, Jr. et al. | Feb 1990 | A |
| 4958305 | Piazza | Sep 1990 | A |
| 5329108 | Lamoure | Jul 1994 | A |
| 5754182 | Kobayashi | May 1998 | A |
| 5781195 | Marvin | Jul 1998 | A |
| 5781704 | Rossmo | Jul 1998 | A |
| 6157747 | Szeliski et al. | Dec 2000 | A |
| 6161098 | Wallman | Dec 2000 | A |
| 6219053 | Tachibana et al. | Apr 2001 | B1 |
| 6232971 | Haynes | May 2001 | B1 |
| 6247019 | Davies | Jun 2001 | B1 |
| 6279018 | Kudrolli et al. | Aug 2001 | B1 |
| 6341310 | Leshem et al. | Jan 2002 | B1 |
| 6369835 | Lin | Apr 2002 | B1 |
| 6389289 | Voce et al. | May 2002 | B1 |
| 6414683 | Gueziec | Jul 2002 | B1 |
| 6483509 | Rabenhorst | Nov 2002 | B1 |
| 6529900 | Patterson et al. | Mar 2003 | B1 |
| 6549944 | Weinberg et al. | Apr 2003 | B1 |
| 6631496 | Li et al. | Oct 2003 | B1 |
| 6662103 | Skolnick et al. | Dec 2003 | B1 |
| 6714936 | Nevin, III | Mar 2004 | B1 |
| 6757445 | Knopp | Jun 2004 | B1 |
| 6839745 | Dingari et al. | Jan 2005 | B1 |
| 6985950 | Hanson et al. | Jan 2006 | B1 |
| 7036085 | Barros | Apr 2006 | B2 |
| 7139800 | Bellotti et al. | Nov 2006 | B2 |
| 7158878 | Rasmussen et al. | Jan 2007 | B2 |
| 7171427 | Witkowski et al. | Jan 2007 | B2 |
| 7278105 | Kitts | Oct 2007 | B1 |
| 7375732 | Arcas | May 2008 | B2 |
| 7379811 | Rasmussen et al. | May 2008 | B2 |
| 7379903 | Caballero et al. | May 2008 | B2 |
| 7426654 | Adams et al. | Sep 2008 | B2 |
| 7454466 | Bellotti et al. | Nov 2008 | B2 |
| 7457706 | Malero et al. | Nov 2008 | B2 |
| 7467375 | Tondreau et al. | Dec 2008 | B2 |
| 7502786 | Liu et al. | Mar 2009 | B2 |
| 7519470 | Brasche et al. | Apr 2009 | B2 |
| 7525422 | Bishop et al. | Apr 2009 | B2 |
| 7529195 | Gorman | May 2009 | B2 |
| 7539666 | Ashworth et al. | May 2009 | B2 |
| 7558677 | Jones | Jul 2009 | B2 |
| 7574428 | Leiserowitz et al. | Aug 2009 | B2 |
| 7617232 | Gabbert et al. | Nov 2009 | B2 |
| 7620628 | Kapur et al. | Nov 2009 | B2 |
| 7627812 | Chamberlain et al. | Dec 2009 | B2 |
| 7634717 | Chamberlain et al. | Dec 2009 | B2 |
| 7663621 | Allen et al. | Feb 2010 | B1 |
| 7703021 | Flam | Apr 2010 | B1 |
| 7716077 | Mikurak | May 2010 | B1 |
| 7770100 | Chamberlain et al. | Aug 2010 | B2 |
| 7791616 | Ioup et al. | Sep 2010 | B2 |
| 7809703 | Balabhadrapatruni et al. | Oct 2010 | B2 |
| 7818658 | Chen | Oct 2010 | B2 |
| 7872647 | Mayer et al. | Jan 2011 | B2 |
| 7894984 | Rasmussen et al. | Feb 2011 | B2 |
| 7920963 | Jouline et al. | Apr 2011 | B2 |
| 7945852 | Pilskains | May 2011 | B1 |
| 7962281 | Rasmussen et al. | Jun 2011 | B2 |
| 7962848 | Bertram | Jun 2011 | B2 |
| 8001465 | Kudrolli et al. | Aug 2011 | B2 |
| 8001482 | Bhattiprolu et al. | Aug 2011 | B2 |
| 8010545 | Stefik et al. | Aug 2011 | B2 |
| 8015487 | Roy et al. | Sep 2011 | B2 |
| 8065080 | Koch | Nov 2011 | B2 |
| 8085268 | Carrino et al. | Dec 2011 | B2 |
| 8145703 | Frishert et al. | Mar 2012 | B2 |
| 8214361 | Sandler et al. | Jul 2012 | B1 |
| 8214764 | Gemmell et al. | Jul 2012 | B2 |
| 8225201 | Michael | Jul 2012 | B2 |
| 8229947 | Fujinaga | Jul 2012 | B2 |
| 8230333 | Decherd et al. | Jul 2012 | B2 |
| 8290942 | Jones et al. | Oct 2012 | B2 |
| 8325178 | Doyle, Jr. | Dec 2012 | B1 |
| 8368695 | Howell et al. | Feb 2013 | B2 |
| 8397171 | Klassen et al. | Mar 2013 | B2 |
| 8400448 | Doyle, Jr. | Mar 2013 | B1 |
| 8412707 | Mianji | Apr 2013 | B1 |
| 8422825 | Neophytou et al. | Apr 2013 | B1 |
| 8447722 | Ahuja et al. | May 2013 | B1 |
| 8452790 | Mianji | May 2013 | B1 |
| 8463036 | Ramesh et al. | Jun 2013 | B1 |
| 8489331 | Kopf et al. | Jul 2013 | B2 |
| 8489641 | Seefeld et al. | Jul 2013 | B1 |
| 8498984 | Hwang et al. | Jul 2013 | B1 |
| 8514082 | Cova et al. | Aug 2013 | B2 |
| 8515207 | Chau | Aug 2013 | B2 |
| 8554579 | Tribble et al. | Oct 2013 | B2 |
| 8577911 | Stepinski et al. | Nov 2013 | B1 |
| 8620641 | Farnsworth et al. | Dec 2013 | B2 |
| 8689108 | Duffield et al. | Apr 2014 | B1 |
| 20010021936 | Bertram | Sep 2001 | A1 |
| 20020003539 | Abe | Jan 2002 | A1 |
| 20020116120 | Ruiz et al. | Aug 2002 | A1 |
| 20020130867 | Yang et al. | Sep 2002 | A1 |
| 20020130907 | Chi et al. | Sep 2002 | A1 |
| 20020174201 | Ramer et al. | Nov 2002 | A1 |
| 20030052896 | Higgins et al. | Mar 2003 | A1 |
| 20030103049 | Kindratenko et al. | Jun 2003 | A1 |
| 20030200217 | Ackerman | Oct 2003 | A1 |
| 20030225755 | Iwayama et al. | Dec 2003 | A1 |
| 20040030492 | Fox et al. | Feb 2004 | A1 |
| 20040039498 | Ollis et al. | Feb 2004 | A1 |
| 20040098236 | Mayer et al. | May 2004 | A1 |
| 20040181554 | Heckerman et al. | Sep 2004 | A1 |
| 20050028094 | Allyn | Feb 2005 | A1 |
| 20050031197 | Knopp | Feb 2005 | A1 |
| 20050034062 | Bufkin et al. | Feb 2005 | A1 |
| 20050080769 | Gemmell et al. | Apr 2005 | A1 |
| 20050125715 | Franco et al. | Jun 2005 | A1 |
| 20050180330 | Shapiro | Aug 2005 | A1 |
| 20050182502 | Iyengar | Aug 2005 | A1 |
| 20050182793 | Keenan et al. | Aug 2005 | A1 |
| 20060026170 | Kreitler et al. | Feb 2006 | A1 |
| 20060045470 | Poslinski et al. | Mar 2006 | A1 |
| 20060074866 | Chamberlain et al. | Apr 2006 | A1 |
| 20060080619 | Carlson et al. | Apr 2006 | A1 |
| 20060129746 | Porter | Jun 2006 | A1 |
| 20060139375 | Rasmussen et al. | Jun 2006 | A1 |
| 20060146050 | Yamauchi | Jul 2006 | A1 |
| 20060251307 | Florin et al. | Nov 2006 | A1 |
| 20060271277 | Hu et al. | Nov 2006 | A1 |
| 20070011150 | Frank | Jan 2007 | A1 |
| 20070016363 | Huang et al. | Jan 2007 | A1 |
| 20070024620 | Muller-Fischer et al. | Feb 2007 | A1 |
| 20070078832 | Ott et al. | Apr 2007 | A1 |
| 20070188516 | Loup et al. | Aug 2007 | A1 |
| 20070258642 | Thota | Nov 2007 | A1 |
| 20070266336 | Nojima et al. | Nov 2007 | A1 |
| 20070294643 | Kyle | Dec 2007 | A1 |
| 20080010605 | Frank | Jan 2008 | A1 |
| 20080040684 | Crump | Feb 2008 | A1 |
| 20080077597 | Butler | Mar 2008 | A1 |
| 20080077642 | Carbone et al. | Mar 2008 | A1 |
| 20080082578 | Hogue et al. | Apr 2008 | A1 |
| 20080098085 | Krane et al. | Apr 2008 | A1 |
| 20080104019 | Nath | May 2008 | A1 |
| 20080163073 | Becker et al. | Jul 2008 | A1 |
| 20080192053 | Howell et al. | Aug 2008 | A1 |
| 20080223834 | Griffiths et al. | Sep 2008 | A1 |
| 20080263468 | Cappione et al. | Oct 2008 | A1 |
| 20080270468 | Mao | Oct 2008 | A1 |
| 20080278311 | Grange et al. | Nov 2008 | A1 |
| 20080294678 | Gorman et al. | Nov 2008 | A1 |
| 20080301643 | Appleton et al. | Dec 2008 | A1 |
| 20090027418 | Maru et al. | Jan 2009 | A1 |
| 20090076845 | Bellin et al. | Mar 2009 | A1 |
| 20090100018 | Roberts | Apr 2009 | A1 |
| 20090115786 | Shimasaki et al. | May 2009 | A1 |
| 20090132953 | Reed et al. | May 2009 | A1 |
| 20090144262 | White et al. | Jun 2009 | A1 |
| 20090158185 | Lacevic et al. | Jun 2009 | A1 |
| 20090164934 | Bhattiprolu et al. | Jun 2009 | A1 |
| 20090171939 | Athsani et al. | Jul 2009 | A1 |
| 20090222400 | Kupershmidt et al. | Sep 2009 | A1 |
| 20090281839 | Lynn et al. | Nov 2009 | A1 |
| 20090287470 | Farnsworth et al. | Nov 2009 | A1 |
| 20090292626 | Oxford | Nov 2009 | A1 |
| 20100057716 | Stefik et al. | Mar 2010 | A1 |
| 20100070523 | Delgo et al. | Mar 2010 | A1 |
| 20100070897 | Aymeloglu et al. | Mar 2010 | A1 |
| 20100076968 | Boyns et al. | Mar 2010 | A1 |
| 20100106420 | Mattikalli et al. | Apr 2010 | A1 |
| 20100122152 | Chamberlain et al. | May 2010 | A1 |
| 20100198684 | Eraker et al. | Aug 2010 | A1 |
| 20100199225 | Coleman et al. | Aug 2010 | A1 |
| 20100293174 | Bennett et al. | Nov 2010 | A1 |
| 20100321399 | Ellren et al. | Dec 2010 | A1 |
| 20100325581 | Finkelstein et al. | Dec 2010 | A1 |
| 20110047159 | Baid et al. | Feb 2011 | A1 |
| 20110060753 | Shaked et al. | Mar 2011 | A1 |
| 20110167105 | Ramakrishnan et al. | Jul 2011 | A1 |
| 20110170799 | Carrino et al. | Jul 2011 | A1 |
| 20110208724 | Jones et al. | Aug 2011 | A1 |
| 20120066296 | Appleton et al. | Mar 2012 | A1 |
| 20120144335 | Abeln et al. | Jun 2012 | A1 |
| 20120206469 | Hulubei et al. | Aug 2012 | A1 |
| 20120208636 | Feige | Aug 2012 | A1 |
| 20120221580 | Barney | Aug 2012 | A1 |
| 20120246148 | Dror | Sep 2012 | A1 |
| 20120323888 | Osann, Jr. | Dec 2012 | A1 |
| 20120330973 | Ghuneim et al. | Dec 2012 | A1 |
| 20130021445 | Cossette-Pacheco et al. | Jan 2013 | A1 |
| 20130046842 | Muntz et al. | Feb 2013 | A1 |
| 20130073377 | Heath | Mar 2013 | A1 |
| 20130076732 | Cervelli et al. | Mar 2013 | A1 |
| 20130097482 | Marantz et al. | Apr 2013 | A1 |
| 20130100134 | Cervelli et al. | Apr 2013 | A1 |
| 20130176321 | Mitchell et al. | Jul 2013 | A1 |
| 20130179420 | Park et al. | Jul 2013 | A1 |
| 20130262527 | Hunter et al. | Oct 2013 | A1 |
| 20130268520 | Fisher et al. | Oct 2013 | A1 |
| 20130290011 | Lynn et al. | Oct 2013 | A1 |
| 20130290825 | Arndt et al. | Oct 2013 | A1 |
| 20140019936 | Cohanoff | Jan 2014 | A1 |
| 20140032506 | Hoey et al. | Jan 2014 | A1 |
| 20140033010 | Richardt et al. | Jan 2014 | A1 |
| Number | Date | Country |
|---|---|---|
| 0 763 201 | Mar 1997 | EP |
| 2 575 107 | Apr 2013 | EP |
| WO 2005013200 | Feb 2005 | WO |
| WO 2010030913 | Mar 2010 | WO |
| Entry |
|---|
| H. Chen and S. T. Dumais. “Bringing order to the web: Automatically categorizing search results”. In Proc. of CHI'00, pp. 145-152, Aug. 2000. |
| GIS-NET 3 Public—Department of Regional Planning. Planning & Zoning Information for Unincorporated LA County. Retrieved Oct. 2, 2013 from <gis.planning.lacounty.gov/GIS-NET3—Public/Viewer.html>. |
| Map of San Jose, CA. Retrieved Oct. 2, 2013 from <maps.google.com>. |
| Map of San Jose, CA. Retrieved Oct. 2, 2013 from <maps.bing.com>. |
| Map of San Jose, CA. Retrieved Oct. 2, 2013 from <maps.yahoo.com>. |
| Ananiev et al., “The New Modality API,” http://web.archive.org/web/20061211011958/http://java.sun.com/developer/technicalArticles/J2SE/Desktop/javase6/modality/ Jan. 2006, pp. 8. |
| Ghosh, P., “A Solution of Polygon Containment, Spatial Planning, and Other Related Problems Using Minkowski Operations,” Computer Vision, Graphics, and Image Processing, 1990, vol. 49, pp. 1-35. |
| Haralick et al., “Image Analysis Using Mathematical Morphology,” Pattern Analysis and Machine Intelligence, IEEE Transactions, Jul. 1987, vol. PAMI-9, No. 4, pp. 532-550. |
| Ipbucker, C., “Inverse Transformation for Several Pseudo-cylindrical Map Projections Using Jacobian Matrix,” ICCSA 2009, Part 1 LNCS 5592, pp. 553-564. |
| Levine, N., “Crime Mapping and the Crimestat Program,” Geographical Analysis, 2006, vol. 38, pp. 41-56. |
| Mandagere, Nagapramod, “Buffer Operations in GIS,” http://www-users.cs.umn.edu/˜npramod/enc—pdf.pdf printed Jan. 28, 2010, pp. 7. |
| Manske, “File Saving Dialogs,” http://www mozilla.org/editor/ui—specs/FileSaveDialogs. html, Jan. 20, 1999, pp. 7. |
| Map Builder, “Rapid Mashup Development Tool for Google and Yahoo Maps!” http://web.archive.org/web/20090626224734/http://www.mapbuilder.net/ printed Jul. 20, 2012 in 2 pages. |
| Murray, C., Oracle Spatial Developer's Guide-6 Coordinate Systems (Spatial Reference Systems), http://docs.oracle.com/cd/B28359—01/appdev.111/b28400.pdf, Jun. 2009. |
| Microsoft Office—Visio, “About connecting shapes,” http://office.microsoft.com/en-us/visio-help/about-connecting-shapes-HP085050369.aspx printed Aug. 4, 2011 in 6 pages. |
| Microsoft Office—Visio, “Add and glue connectors with the Connector tool,” http://office.microsoft.com/en-us/visio-help/add-and-glue-connectors-with-the-connector-tool-HA010048532.aspx?CTT=1 printed Aug. 4, 2011 in 1 page. |
| Open Street Map, “Amm's Diary:Unconnected ways and other data quality issues,” http://www.openstreetmap.org/user/amm/diary printed Jul. 23, 2012 in 3 pages. |
| POI Editor, “How To: Create Your Own Points of Interest,” http://www.poieditor.com/articles/how—to—create—your—own—points—of—interest/ printed Jul. 22, 2012 in 4 pages. |
| Pozzi et al., “Vegetation and Population Density in Urban and Suburban Areas in the U.S.A.” Third International Symposium of Remote Sensing of Urban Areas Istanbul, Turkey, Jun. 2002, pp. 8. |
| Reddy et al., “Under the hood of GeoVRML 1.0,” SRI International, Proceedings of the fifth symposium on Vurtual Reality Modeling Language (Web3D-VRML), New York, NY, Feb. 2000, pp. 23-28. http://pdf.aminer.org/000/648/038/under—the—hood—of—geovrml.pdf. |
| Reibel et al., “Areal Interpolation of Population Counts Using Pre-classified Land Cover Data,” Population Research and Policy Review, 2007, vol. 26, pp. 619-633. |
| Reibel, M., “Geographic Information Systems and Spatial Data Processing in Demography: a Review,” Population Research and Policy Review, 2007, vol. 26, pp. 601-618. |
| Rizzardi et al., “Interfacing U.S. Census Map Files with Statistical Graphics Software: Application and Use in Epidemiology,” Statistics in Medicine, Oct. 1993, vol. 12, No. 19-20, pp. 1953-1964. |
| Snyder, “Map Projections—A Working Manual,” U.S. Geological Survey Professional paper 1395, United States Government Printing Office, Washington: 1987, pp. 11-21 and 60-70. |
| Sonris, “Using the Area of Interest Tools,” http://web.archive.org/web/20061001053327/http://sonris-www.dnr.state.la.us/gis/instruct—files/tutslide12 printed Jan. 3, 2013 in 1 page. |
| Tangelder et al., “Freeform Shape Matching Using Minkowski Operations,” The Netherlands, Jun. 1996, pp. 12. |
| VB Forums, “Buffer a Polygon,” Internet Citation, http://www.vbforums.com/showthread.php?198436-Buffer-a-Polygon, Specifically Thread #1, #5 & #11 retrieved on May 2, 2013, pp. 8. |
| Vivid Solutions, “JTS Topology Suite: Technical Specifications,” http://www.vividsolutions.com/jts/bin/JTS%20Technical%20Specs.pdf Version 1.4, 2003, pp. 36. |
| Wikipedia, “Ramer-Douglas-Peucker Algorithm,” http://en.wikipedia.org/wiki/Ramer%E2/%80%93Douglas%E2%80%93Peucker—algorithm printed Jul. 2011, pp. 3. |
| Wikipedia, “Douglas-Peucker-Algorithms,” http://de.wikipedia.org/w/index.php?title=Douglas-Peucker-Algorithmus&oldid=91846042 printed Jul. 2011, pp. 2. |
| Woodbridge, Stephen, “[geos-devel] Polygon simplification,” http://lists.osgeo.org/pipermail/geos-devel/2011-May/005210.html dated May 8, 2011, pp. 3. |
| International Search Report and Written Opinion in Application No. PCT/US2009/056703, dated Mar. 15, 2010. |
| Official Communication in Australian Application No. AU2010227081, dated Mar. 18, 2011. |
| Official Communication in Australian Application No. AU2010257305, dated Apr. 12, 2011. |
| Official Communication in Australian Application No. AU2010257305, dated Sep. 22, 2011. |
| European Search Report in European Application No. EP10195798.3, dated May 17, 2011. |
| European Search Report in European Application No. EP12186236.1, dated May 17, 2013. |
| “A First Look: Predicting Market Demand for Food Retail using a Huff Analysis,” TRF Policy Solutions, Jul. 2012, pp. 30. |
| Acklen, Laura, “Absolute Beginner's Guide to Microsoft Word 2003,” Dec. 24, 2003, pp. 15-18, 34-41, 308-316. |
| “Andy Turner's GISRUK 2012 Notes” https://docs.google.com/document/d/1cTmxg7mVx5gd89lqblCYvCEnHA4QAivH4I4WpyPsqE4/edit?pli=1 printed Sep. 16, 2013 in 15 pages. |
| Barnes et al., “Viewshed Analysis”, GIS-ARC/INFO 2001, www.evsc.virginia.edu/˜jhp7e/evsc466/student—pres/Rounds.pdf. |
| Bugzilla@Mozilla, “Bug 18726—[feature] Long-click means of invoking contextual menus not supported,” http://bugzilla.mozilla.org/show—bug.cgi?id=18726 printed Jun. 13, 2013 in 11 pages. |
| Carver et al., “Real-Time Visibility Analysis and Rapid Viewshed Calculation Using a Voxel-Based Modelling Approach,” GISRUK 2012 Conference, Apr. 11-13, Lancaster UK, Apr. 13, 2012, pp. 6. |
| Dramowicz, Ela, “Retail Trade Area Analysis Using the Huff Model,” Directions Magazine, Jul. 2, 2005 in 10 pages, http://www.directionsmag.com/articles/retail-trade-area-analysis-using-the-huff-model/123411. |
| Griffith, Daniel A., “A Generalized Huff Model,” Geographical Analysis, Apr. 1982, vol. 14, No. 2, pp. 135-144. |
| Hibbert et al., “Prediction of Shopping Behavior Using a Huff Model Within a GIS Framework,” Healthy Eating in Context Mar. 18, 2011, pp. 16. |
| Huff et al., “Calibrating the Huff Model Using ArcGIS Business Analyst,” ESRI, Sep. 2008, pp. 33. |
| Huff, David L., “Parameter Estimation in the Huff Model,” ESRI, ArcUser, Oct.-Dec. 2003, pp. 34-36. |
| Liu, Tianshun, “Combining GIS and the Huff Model to Analyze Suitable Locations for a New Asian Supermarket in the Minneapolis and St. Paul, Minnesota USA,” Papers in Resource Analysis, 2012, vol. 14, pp. 8. |
| Microsoft—Developer Network, “Getting Started with VBA in Word 2010,” Apr. 2010, http://msdn.microsoft.com/en-us/library/ff604039%28v=office.14%29.aspx as printed Apr. 4, 2014 in 17 pages. |
| Official Communication in New Zealand Application No. 616167 dated Oct. 10, 2013. |
| Qiu, Fang, “3d Analysis and Surface Modeling”, http://web.archive.org/web/20091202221925/http://www.utsa.edu/lrsg/Teaching/EES6513/08-3D.pdf printed Sep. 16, 2013 in 26 pages. |
| Number | Date | Country | |
|---|---|---|---|
| 61820608 | May 2013 | US |
