Patent Grant
11599706
This disclosure relates to approaches for providing views of geospatial information.
Under conventional approaches, information relating to a location may be collected for analysis and viewing from a variety of data sources. In general, it may be difficult for users to effectively analyze and utilize such information in a comprehensive manner and/or to understand the context of such information.
Various embodiments of the present disclosure may include systems, methods, and non-transitory computer readable media configured to provide views of geospatial information. A user's selection of a location may be obtained. Characteristic information describing characteristics of the location may be obtained. Activities information describing activities of the location and surrounding area may be obtained. An interface (e.g., user interface, API) enabling presentation of a geospatial view of the activities of the location and surrounding area with respect to the characteristics of the location may be provided.
In some embodiments, the characteristics of the location may include physical objects of the location, and the activities of the location may include events or reports of the location and surrounding area. The interface may further enable presentation of formatted views of narratives for the events or the reports of the location. The formatted views of the narratives may include separation of the narratives into multiple sections.
In some embodiments, the interface may further enable tagging of a given text of a given narrative.
In some embodiments, one or more media files of the location may be obtained. The media file(s) may be associated with a position within the location. The interface may further enable presentation of a geospatial view of the media file(s) at the position within the location.
In some embodiments, the media file(s) of the location and surrounding area may be obtained through a decorator operation. The decorator operation may find and provide the media file(s) of the location. In some embodiments, the decorator operation may find the media file(s) using a federated search. The federated search may include a search of one or more external data sources.
These and other features of the systems, methods, and non-transitory computer readable media disclosed herein, as well as the methods of operation and functions of the related elements of structure and the combination of parts and economies of manufacture, will become more apparent upon consideration of the following description and the appended claims with reference to the accompanying drawings, all of which form a part of this specification, wherein like reference numerals designate corresponding parts in the various figures. It is to be expressly understood, however, that the drawings are for purposes of illustration and description only and are not intended as a definition of the limits of the invention.
Certain features of various embodiments of the present technology are set forth with particularity in the appended claims. A better understanding of the features and advantages of the technology will be obtained by reference to the following detailed description that sets forth illustrative embodiments, in which the principles of the invention are utilized, and the accompanying drawings of which:
A claimed solution rooted in computer technology overcomes problems specifically arising in the realm of computer technology. In various implementations, a computing system may obtain a user's selection of a location. For example, the computing system may obtain a user's selection of a particular location (e.g., defined by particular longitude and latitude, or a particular address), a user's selection of a map for the particular location, a user's selection of an object located at/relating to a particular location, and/or other selection of a particular location. The computing system may obtain characteristic information describing characteristics of the location and activities information describing activities of the location and surrounding area. The characteristics of the location may include physical objects (e.g., persons, vehicles, buildings) of the location and the activities of the location and surrounding area may include events or reports (e.g., activity report) of the location and surrounding area.
The computing system may provide an interface that enables presentation of a geospatial view of the activities of the location with respect to the characteristics of the location. For example, the computing system may provide an interface that provides a map of a location augmented with characteristics of the location, with activities of the location and surrounding area marked at their corresponding positions within the map.
In some embodiments, the interface may further enable presentation of formatted views of narratives for the events or the reports of the location. The formatted views of the narratives may include separation of the narratives into multiple sections. For example, the interface may enable presentation of a formatted view of a narrative for an activity report where the narrative is broken into different sections. Other types of formatting (e.g., ALL-CAPS to sentence caps, line/paragraph adjustments) may be used. The interface may also enable tagging of a given text of a given narrative. The tagged text may be converted into a property, a link, and/or other fields associated with the event/report/location. The interface may further suggest one or more text of a given narrative to be tagged/converted.
In some embodiments, the computing system may obtain one or more media files of the location. The media file(s) may be associated with a position within the location, and the interface may further enable presentation of a geospatial view of the media file(s) at the position within the location. For example, based on a user's selection of a particular media file(s), the location at which the media file(s) was captured/the location with which the media file(s) is related may be indicated on a map.
In some embodiments, the one or more media files of the location may be obtained through a decorator operation. The decorator operation may find and provide (e.g., load) the one or more media files of the location. The decorator operation may find the one or more media files using a federated search, which may include a search of one or more external data sources.
The approach disclosed herein enables customized views of information. Objects having geospatial properties may be displayed within their corresponding positions in a location to provide geospatial context of the objects. Narratives of events/reports may be formatted to facilitate users' use or analysis of the narratives.
In various embodiments, the computing system 102 may include a datastore 112, a location engine 114, a characteristics engine 116, an activities engine 118, a media engine 120, and an interface engine 122. The datastore 112 may include structured and/or unstructured sets of data that can be divided/extracted for provisioning when needed by one or more components of the environment 100. The datastore 112 may include one or more databases. The datastore 112 may include different data analysis/processing modules that facilitate different data analysis/processing tasks, and/or other information to be used in the environment 100. While the computing system 102 is shown in
In various embodiments, the location engine 114 may be configured to obtain a user's selection of a location. A location may refer to a particular place or an area. A user's selection of a location may include the user's selection of a particular location or a user's selection of an object associated with a particular location or a position within a particular location. For example, the location engine 114 may obtain a user's selection of a location based on a user's selection of a particular location defined by particular longitude and latitude or a particular address, a user's selection of a map for the particular location, a user's selection of an object located at/relating to a particular location, and/or other selection of a particular location. In some embodiments, the location engine 114 may obtain a user's selection of a location based on a user's interaction with a user interface/application. For example, a user interface/application may provide option(s) for a user to enter a particular location for selection via key entry or choose a particular location for selection via interaction with a map. Other selections of locations are contemplated.
In various embodiments, the characteristics engine 116 may be configured to obtain characteristic information describing characteristics of the location selected by the user. In some embodiments, the characteristic information may further include information describing an area (or region) surrounding the location selected by the user or information describing one or more portions of the surrounding area. Obtaining characteristic information may include accessing, acquiring, analyzing, determining, examining, loading, locating, opening, receiving, retrieving, reviewing, storing, and/or otherwise obtaining the characteristic information. For example, the characteristics engine 116 may, based on the location selected by the user, search for and/or obtain characteristic information describing characteristics of the location. Characteristic information may be obtained from one or more storage locations. A storage location may refer to electronic storage located within the computing system 102 (e.g., integral and/or removable memory of the computing system 102), electronic storage coupled to the computing system 102, and/or electronic storage located remotely from the computing system 102 (e.g., electronic storage accessible to the computing system 102 through a network). Characteristic information may be obtained from one or more databases (e.g., the datastore 112). Characteristic information may be stored within a single file or across multiple files. For example, characteristic information for a location may have been ingested into a database (e.g., the datastore 112) as one or more objects, and the characteristics engine 116 may retrieve the object(s) to obtain the characteristics information.
Characteristics of a location may refer to features and/or qualities of a location. For example, characteristics of a location may include physical features and/or physical qualities of a location, such as physical objects (e.g., persons, vehicles, buildings) of a location. Characteristics of a location may include permanent features and qualities and/or temporary features and qualities. For example, characteristics of a location of a may include different persons and/or vehicle at different times. Characteristics of a location may include same physical traits (e.g., altitude) at different times. Other types of characteristics of a location are contemplated.
In some embodiments, the characteristics engine 116 may obtain characteristic information describing characteristics of interest of a location. For example, the characteristics engine 116 may obtain, for a location, characteristics that are of interest to one or more users and/or one or more projects. That is, the characteristics engine 116 may obtain characteristic information describing different characteristics of a location for different users/projects. The characteristics engine 116 may obtain characteristic information describing characteristics of a location that are of interest to a user/project.
In various embodiments, the activities engine 118 may be configured to obtain activities information describing activities of the location selected by the user. In some embodiments, the activities information may further describe activities in an area (or region) surrounding the location selected by the user or activities in one or more portions of the surrounding area. Obtaining activities information may include accessing, acquiring, analyzing, determining, examining, loading, locating, opening, receiving, retrieving, reviewing, storing, and/or otherwise obtaining the activities information. For example, the activities engine 118 may, based on the location selected by the user, search for and/or obtain activities information describing activities of the location. Activities information may be obtained from one or more storage locations. Activities information may be obtained from one or more databases (e.g., the datastore 112). Activities information may be stored within a single file or across multiple files. For example, activities information for a location may have been ingested into a database (e.g., the datastore 112) as one or more objects, and the activities engine 118 may retrieve the object(s) to obtain the activities information.
Activities of a location (and surrounding area) may refer to occurrences of conditions or things within a location (and surrounding area), and/or information relating to occurrences of conditions or things within a location (and surrounding area). For example, activities of a location and surrounding area may include events or reports of events within a location and area surrounding the location. Activities of a location may include ongoing activities, periodic activities, recurring activities, singular activates, and/or other activities. Activities of a location may include activities that have occurred, activities that are occurring, and/or activities that will occur in the future. For example, activities of a location may include a future event that is scheduled to occur at the location and/or a report (e.g., activity report) regarding a past event at the location. Events/reports of events of a location may be described using one or more narratives. In some embodiment, a narrative of an event/report may lack formatting. In some embodiments, a narrative of an event/report may be formatted and/or separated into different sections for presentation. Other types of activities of a location are contemplated.
In some embodiments, the activities engine 118 may obtain activities information describing activities of interest for a location. The activities information may further describes activities of interest in the surrounding area. For example, the activities engine 118 may obtain, for a location, activities that are of interest to one or more users and/or one or more projects. That is, the activities engine 116 may obtain activities information describing different activities of a location (and surrounding area) for different users/projects. The activities engine 118 may obtain activities information describing activities for a location (and surrounding area) that are of interest to a user/project.
In various embodiments, the media engine 120 may be configured to obtain one or more media files of a location. Obtaining a media file may include accessing, acquiring, analyzing, determining, examining, loading, locating, opening, receiving, retrieving, reviewing, storing, and/or otherwise obtaining the media file. A media file may be obtained from one or more storage locations. For example, the media engine 120 may, based on the location selected by the user, search for and/or obtain media files of the location. A media file may be obtained from one or more databases (e.g., the datastore 112). For example, a media file for a location may have been ingested into a database (e.g., the datastore 112) as one or more objects, and the media engine 120 may retrieve the object(s) to obtain the media file.
A media file may refer to an electronic file defining one or more media, such as an image file, an audio file, a video file, a document file, a presentation file, and/or other files. A media file may be associated with one or more positions within the location. That is, a media file may be associated with position(s) where the media file was captured, position(s) in which a subject of the media file is located, position(s) with which the media file has been tagged, and/or other positions.
In some embodiments, the media engine 120 may obtain media file(s) of interest for a location. For example, the media engine 120 may obtain, for a location, media files that are of interest to one or more users and/or one or more projects. That is, the media engine 120 may obtain different media files of a location for different users/projects. The media engine 120 may obtain particular media/media type for a location that are of interest to a user/project.
In some embodiments, a media file of a location may be obtained through one or more decorator operations. A decorator operation may refer to an operation that finds information for an object and provides the information for the object. For example, an object corresponding to a building may have address information for the building but may lack longitude and latitude information for the building. A decorator operation may use the address information of the building object to determine/retrieve the longitude and latitude information for the building object, and provide the longitude and latitude information for the building object. For example, the longitude and latitude information for the building object may be obtained and displayed for the building object when the building object is loaded into a map. Decorating objects with particular information may be expensive. For example, decorating all building objects with longitude and latitude information may require consumption of large amounts of processing, time, and/or memory resources. Rather than decorate all building objects with longitude and latitude information, a decorator operation may be used to obtain and provide longitude and latitude information for a particular building object when the particular building object is loaded for view (e.g., in a map). Such approaches may provide for resource savings in decorating objects with information.
A decorator operation may find and provide (e.g., load) media file(s) corresponding to a location. For example, the decorator operation may use one or more properties of a location, such as geo-location and/or identifier, to find related media files and provide them for presentation. In some embodiments, a decorator operation may find the media files using a federated search. A federated search may include search of multiple searchable resources. A search request for media files may be distributed to multiple search engines, databases, and/or other searchable resources and the results of the searches may be aggregated for presentation. A federated search may include a search of one or more external data sources. That is, a federated search may search data sources external to the computing system 102 for media files.
The use of federated searching may provide for identification and provision of external media items (e.g., media items not stored in the datastore 112). Media files may be large and local storage of media files for different locations may consume large amounts of resources. Importing media files into different projects for different locations may also consume large amounts of resources. Rather than locally storing/importing media files, the media files may be identified and loaded from external data sources when needed. Such provision of external media files may reduce resource consumption by the computing system 102.
In various embodiments, the interface engine 122 may be configured to provide one or more interfaces. The interface(s) may include application program interface(s) and/or user interface(s). The interface(s) may enable presentation of a geospatial view of the activities of the location and surrounding area with respect to the characteristics of the location. The interface engine 122 may provide one or more APIs that may be used by users/computing systems to view (or access) positions of activities with respect to positions of different characteristics of a location. For example, the interface engine 122 may provide an interface that provides a map of a location augmented with characteristics of the location and/or with activities of the location and surrounding area marked at their corresponding positions within the map. Visuals, such as icons or other visual representation, representing activities and/or characteristics may appear on a map based on the geo-locations of the activities/characteristics.
Providing a geospatial view of the activities of the location and surrounding area with respect to the characteristics of the location may enable users to review the activities based on their corresponding positions and analyze information based on the respective positions among activities/characteristics. For example, visuals representing activities/events/reports may be presented on a map of a location and surrounding area based on the positions of the activities/events/reports within the location and surrounding area. Such presentation of visuals may enable users to review the activities/events/reports based on their positions with respect to characteristics (e.g., buildings, objects, terrain) of the location and surrounding area and/or other activities/events/reports of the location and surrounding area.
In some embodiments, the interface(s) provided by the interface engine 122 may enable presentation of a geospatial view of media file(s) at corresponding position(s) within the location. A media file may be associated with one or more positions within the location. For example, a media file may be associated with position(s) where the media file was captured, position(s) in which a subject of the media file is located, position(s) with which the media file has been tagged, and/or other locations. Based on a user's selection of a particular media file, the associated position of the particular media file may be indicated in the visual presentation of the location (e.g., on a map). For example, the position at which the particular media file was captured/the position with which the particular media file is related may be indicated on a map of the location. Selection of a particular media file by the user may include the user clicking on the particular media file through a user interface, the user clicking on an option for the particular media file through a user interface, the user hovering over the particular media file in a user interface, and/or other selection of the particular media file. Indication of the associated position on a map may include display of a visual indicator (e.g., icon, shape) at the associated position. In some embodiments, indications of the associated positions on a map may be configured differently. For example, the indications may have different sizes and/or shapes to represent different extents/areas of the associated positions.
In some embodiments, the interface(s) may enable presentation of formatted views of narratives for the events or the reports of the location. That is, a narrative of an event/report of the location may not be formatted and the interface(s) may provide for views of a formatted narrative. A narrative may include text, properties, and/or other information relating to an event/report and the interface(s) may provide a formatted view of the narrative separated into multiple sections, such as a header section, a source section, a comment section, an administrative section, a contact section, and/or other sections. For example, the interface(s) may enable presentation of a formatted view of a narrative for an activity report where the narrative is broken into different sections. In some embodiments, texts of the narrative may be collapsed inside the different sections and users may view the corresponding text by expanding the individual sections.
In some embodiments, a formatted view of a narrative may include formatting of text contained within the narrative. Formatting of text contained within the narrative may provide a user-friendly view of the narrative. For example, the narrative may include unformatted text, such as blob of text, text provided as lower-case/ALLCAPS text, text not utilizing different typography to highlight certain information within the narrative, and/or text without spacing that allows users to easily distinguish groupings/sets of information conveyed by the text. The text of the narrative may be formatted by changes in capitalization, typography, and/or the spacing of the text.
In some embodiments, changing the capitalization may include changing lower-case/ALLCAPS text to sentence case format—capitalizing the first letter of each sentence rather than every letter. In some embodiments, using sentence case format may include capitalizing certain terms which are normally capitalized (e.g., first letters in names, letters in acronyms). Other changes in capitalization of the narrative are contemplated.
In some embodiments, changing the typography may include changing one or more of color, font, size, italics, bold, underline, and/or other typography of letters/words/terms within the narrative. For example, particular terms of importance/potential importance in the narrative may be called out for view by users by changing color, font, size, italics, bold, underline, and/or other typography of the terms. In some embodiments, the typography of different letters/words/terms may be changed differently. For example, letters/words/terms conveying different information/types of information (e.g., currency amounts, dates, physical/email addresses, phone numbers) may be changed differently (e.g., different color, different font, different size). Other changes in typography of the narrative are contemplated.
In some embodiments, changing the spacing may including adding/removing/modifying spacing within the narrative. For example, a narrative relating to an event may separate different types of information using different spacing (e.g., double spacing, triple spacing). The different types of spacing may be changed to indicate separation of information/types of information. For example, quadruple spacing between groupings of texts may be replaced with Tabs while triple spacing between groupings of texts may be replaced with paragraph breaks. As another example, particular spacing may be changed within the narrative based on a particular letter/word/term within the unstructured information (e.g., adding a paragraph break following/preceding a particular term). Particular spacing may be changed within the narrative based on a particular combination of letters/words/terms within the unstructured information (e.g., adding a Tab following/preceding a particular combination of words, adding a Tab between particular terms). Other changes in spacing within the narrative are contemplated.
In some embodiments, formatting of the narrative may be changed/determined based on user input. For example, different formatting options (e.g., capitalization, typography, spacing) for the narrative may be provided to users (e.g., via user interface, API) and the users may select the particular formatting desired for the narrative. The narrative may be formatted in accordance with the formatting option(s) selected by the users. In some embodiments, the type of formatting performed on a narrative may be selected using on one or more machine learning techniques. Other types of formatting of narratives are contemplated.
In some embodiments, letters/words/terms may be formatted based on tagging of the letters/words/terms. For example, certain letters/words/terms may be tagged as a key term, tagged with certain properties associated with formatting, and/or otherwise tagged. Such letters/words/terms may be formatted (e.g., highlighted) to distinguish them from other text of the narrative. In some embodiments, the interface(s) may provide a view of a list of tagged text. Users may interact with the list of tagged text to see additional information about the tagged text. For example, users may click on a tagged text or hover over a tagged text to see the properties of the tagged text.
In some embodiments, the interface(s) may enable tagging of one or more texts of a narrative. The tagged text may be converted into a property, a link, and/or other fields associated with the event, the report, and/or the location. The interface(s) may enable users to select one or more text of a narrative and provide options for users to tag the selected text. For example, users may use the interface(s) to highlight a given text, right click on the highlight to see options for tagging the text, and add parameters associated with the selected tagging option. For instance, users may use the options to tag a text as a property (e.g., of the narrative, of an object) and the interface(s) may provide options for the users to input the parameters of the property.
In some embodiments, the interface(s) may suggest one or more text of a given narrative to be tagged/converted. Particular texts may be suggested for tagging based on historical tagging of terms, machine learning, and/or other algorithms. For example, distinctive text that represents a value of interest (e.g., geolocation using military grid reference system) may be suggested for tagging. Such text may be difficult to see and highlighting may enable users to more easily locate the text.
Referring to
A viewing section 208 may provide a visual view of a location. For example, the viewing section 208 may provide a map of a location. The viewing section 208 may provide a geospatial view of the activities of a location with respect to the characteristics of the location. Such a view may include a map of a location augmented with characteristics of the location, with activities of the location marked at their corresponding positions within the map. For example, icons 218 may represent different activities and/or characteristics, and the icons 218 may be displayed in the viewing section based on their corresponding positions within the map. Such a view of activities and characteristics of a location may enable users to understand their context. For example, users may use the display of icons 218 to understand where an event occurred with respect to objects (e.g., persons, vehicles, building) in a location. In some embodiments, the viewing section 208 may provide a visual view of one or more portions of area surrounding the location.
The viewing section 208 may include zoom options 214 to change the extent of the map displayed within the viewing section 208. The viewing section 208 may include an information section 210 that provides detailed information regarding a location. For example, the information section 210 may provide information relating to particular properties of the location, nearby activities, nearby characteristics, and/or other information. The information displayed within the information section 210 may change based on changes in the zoom of the map and/or based on user's selection of a boundary for which information is to be displayed. For example, users may mark a boundary 218 within the viewing section 208 and the information displayed in the information section 210 may be restricted to information relating to objects within the boundary 218. In some embodiments, presentations of particular activities and/or characteristics of the location within the viewing section may similarly be restricted to the boundary 218. Other shapes and sizes of such boundaries are contemplated.
The viewing section 208 may include a size option 220. The size option 220 may enable users to determine the extent of a location displayed within the viewing section 208. For example, users may use the size option 220 to change the extent of a location displayed within the viewing section 208 from 500 meters to 50 meters. The size option 220 may be used in conjunction with or in place of the zoom options 214.
The viewing section 208 may include a duration option 222. The duration option 222 may enable users to determine the duration of time for which information regarding a location is displayed on the user interface 200. For example, users may use the duration option 222 to change the duration of time for which information regarding a location is displayed from the last 30 days to the last 5 days, to the present day, or other times, and/or to include information regarding events that are set to occur within the next 30 days. In some embodiments, the viewing section 208 may include a dynamic presentation of information where the positions of characteristics and/or activities of the location changes with time and allows users to play the changes in the characteristics and/or activities of the location.
The user interface 200 may include an associated information section 212. The associated information section may display information associated with a location, information associated with a characteristics of a location, information associated with an activities of a location, and/or other information about a location. The associated information section 212 may identify applications/application assets which uses the location being displayed within the viewing section 208. For example, the associated information section 212 may identify files of a mapping application that includes the location displayed within the viewing section 208. The associated information section 212 may display other information associated with a location, such as a listing of media files of the location.
Referring to
The user interface 300 may include a media files section 306. The media files section 306 may provide a view of media files 308 of the location. Users may interact with the media files section 306 to view the media files 308 and/or to see information about the media files 308. For example, users may select a particular media file within the media files section 306 and the selection of the particular media file may be shown via an indicator 310. The media files 308 may be associated with one or more positions within the location. That is, media files 308 may be associated with position(s) where the respective media file was captured, position(s) in which subject of the media files 308 is located, position(s) with which the media files 308 has been tagged, and/or other positions. Based on users' selection of a particular media file, the associated position of the particular media file may be shown via an indicator 312. In some embodiment, a preview of the particular media file may be shown within the indicator 312. In some embodiment, the particular media file may be played within the indicator 312. In some embodiments, the particular media file may be played within a separate application, such as a media player and/or users may be directed to a provider of the particular media file to view the particular media file. For example, users may be directed to a media player and/or a media browser hosted by the provider of the particular media file. In some embodiments, users may select multiple media items within the media files section 306 and the viewing section 304 may include multiple indicators for the selected media items displayed at their corresponding positions.
The user interface 300 may include an open option 314. The open option 314 may enable users to open the location viewed within the viewing section 304 in another application. For example, users may use the open option 314 to open the location viewed within the viewing section 304 in a mapping application. In some embodiments, the mapping application may create a new file for the location based on users' use of the open option 314. In some embodiments, the mapping application may open an existing file for the location based on users' use of the open option 314. If multiple files exist for the location, the mapping application may prompt users to choose one of the existing files.
Referring to
Users may interact with the list section 404 to view the events and/or report, and/or see other information about the events and/or report. For example, users may select two particular events/reports within the list section 404 and the selections of the particular events/reports may be shown via indicators 408. Responsive to users' selection, the user interface 400 may display information blocks 410. Individual information blocks 410 may correspond to individual events/reports selected by users. Information blocks 410 may display information about the selected events/reports, such as narratives of the selected events/reports and/or maps of corresponding locations/positions. In some embodiments, the maps displayed within the information blocks 410 may be interactive. That is, users may interact with the map to see additional/different information. In some embodiments, the information displayed within the information blocks 410 may be formatted.
Referring to
For example, the document section 504 may present a formatted view of a narrative for an activity report where the narrative is broken into four different sections (Sections A, B, C, D). The texts of the narrative may be collapsed inside different sections and users may view the corresponding text by expanding the individual sections. For example, a user may have selected the Section C for expansion and the text of the narrative corresponding to the Section C may be displayed within the document section under Section C.
The user interface 500 may include an overview section 506. The overview section 506 may display properties of accessed information, such as properties of an activity report. The overview section 506 may display other related information, such as a map view of a location corresponding to the activity report.
The user interface 500 may include a tag section 508. The tag section 508 may list letters/words/terms which have been tagged. For example, the tag section 508 may list letters/words/terms which have been tagged as a key term, tagged with certain properties, and/or otherwise tagged. Users may interact with the tag section 508 to view information relating to tags, such as properties of different tags or to highlight text corresponding to the tags within the document section 504. Users may interact with the tag section 508 to change one or more tags, such as by adding a tag, removing a tag, and/or modifying a tag.
At block 602, a user's election of a location may be obtained. At block 604, characteristic information describing characteristics of the location may be obtained. At block 606, activities information describing activities of the location may obtained. At block 608, an interface may be provided. The interface may enable presentation of a geospatial view of the activities of the location with respect to the characteristics of the location.
Hardware Implementation
The 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 circuitry or 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 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.
The computer system 700 also includes a main memory 706, such as a random access memory (RAM), cache and/or other dynamic storage devices, coupled to bus 702 for storing information and instructions to be executed by processor 704. Main memory 706 also may be used for storing temporary variables or other intermediate information during execution of instructions to be executed by processor 704. Such instructions, when stored in storage media accessible to processor 704, render computer system 700 into a special-purpose machine that is customized to perform the operations specified in the instructions.
The computer system 700 further includes a read only memory (ROM) 708 or other static storage device coupled to bus 702 for storing static information and instructions for processor 704. A storage device 710, such as a magnetic disk, optical disk, or USB thumb drive (Flash drive), etc., is provided and coupled to bus 702 for storing information and instructions.
The computer system 700 may be coupled via bus 702 to a display 712, such as a cathode ray tube (CRT) or LCD display (or touch screen), for displaying information to a computer user. An input device 714, including alphanumeric and other keys, is coupled to bus 702 for communicating information and command selections to processor 704. Another type of user input device is cursor control 716, such as a mouse, a trackball, or cursor direction keys for communicating direction information and command selections to processor 704 and for controlling cursor movement on display 712. 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.
The computing system 700 may include a user interface module to implement a GUI that 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, 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.
The computer system 700 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 700 to be a special-purpose machine. According to one embodiment, the techniques herein are performed by computer system 700 in response to processor(s) 704 executing one or more sequences of one or more instructions contained in main memory 706. Such instructions may be read into main memory 706 from another storage medium, such as storage device 710. Execution of the sequences of instructions contained in main memory 706 causes processor(s) 704 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 710. Volatile media includes dynamic memory, such as main memory 706. 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 non-transitory media. For example, transmission media includes coaxial cables, copper wire and fiber optics, including the wires that comprise bus 702. 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 704 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 into its dynamic memory and send the instructions over a telephone line using a modem. A modem local to computer system 700 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 702. Bus 702 carries the data to main memory 706, from which processor 704 retrieves and executes the instructions. The instructions received by main memory 706 may retrieves and executes the instructions. The instructions received by main memory 706 may optionally be stored on storage device 710 either before or after execution by processor 704.
The computer system 700 also includes a communication interface 718 coupled to bus 702. Communication interface 718 provides a two-way data communication coupling to one or more network links that are connected to one or more local networks. For example, communication interface 718 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 718 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 718 sends and receives electrical, electromagnetic or optical signals that carry digital data streams representing various types of information.
A network link typically provides data communication through one or more networks to other data devices. For example, a network link may provide a connection through local network to a host computer or to data equipment operated by an Internet Service Provider (ISP). The ISP in turn provides data communication services through the world wide packet data communication network now commonly referred to as the “Internet”. Local network and Internet both use electrical, electromagnetic or optical signals that carry digital data streams. The signals through the various networks and the signals on network link and through communication interface 718, which carry the digital data to and from computer system 700, are example forms of transmission media.
The computer system 700 can send messages and receive data, including program code, through the network(s), network link and communication interface 718. In the Internet example, a server might transmit a requested code for an application program through the Internet, the ISP, the local network and the communication interface 718.
The received code may be executed by processor 704 as it is received, and/or stored in storage device 710, or other non-volatile storage for later execution.
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 sub-combinations are intended to fall within the scope of this disclosure. In addition, certain method or process blocks may be omitted in some embodiments. 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.
Certain embodiments are described herein as including logic or a number of components, engines, or mechanisms. Engines may constitute either software engines (e.g., code embodied on a machine-readable medium) or hardware engines. A “hardware engine” is a tangible unit capable of performing certain operations and may be configured or arranged in a certain physical manner. In various example embodiments, one or more computer systems (e.g., a standalone computer system, a client computer system, or a server computer system) or one or more hardware engines of a computer system (e.g., a processor or a group of processors) may be configured by software (e.g., an application or application portion) as a hardware engine that operates to perform certain operations as described herein.
In some embodiments, a hardware engine may be implemented mechanically, electronically, or any suitable combination thereof. For example, a hardware engine may include dedicated circuitry or logic that is permanently configured to perform certain operations. For example, a hardware engine may be a special-purpose processor, such as a Field-Programmable Gate Array (FPGA) or an Application Specific Integrated Circuit (ASIC). A hardware engine may also include programmable logic or circuitry that is temporarily configured by software to perform certain operations. For example, a hardware engine may include software executed by a general-purpose processor or other programmable processor. Once configured by such software, hardware engines become specific machines (or specific components of a machine) uniquely tailored to perform the configured functions and are no longer general-purpose processors. It will be appreciated that the decision to implement a hardware engine mechanically, in dedicated and permanently configured circuitry, or in temporarily configured circuitry (e.g., configured by software) may be driven by cost and time considerations.
Accordingly, the phrase “hardware engine” should be understood to encompass a tangible entity, be that an entity that is physically constructed, permanently configured (e.g., hardwired), or temporarily configured (e.g., programmed) to operate in a certain manner or to perform certain operations described herein. As used herein, “hardware-implemented engine” refers to a hardware engine. Considering embodiments in which hardware engines are temporarily configured (e.g., programmed), each of the hardware engines need not be configured or instantiated at any one instance in time. For example, where a hardware engine comprises a general-purpose processor configured by software to become a special-purpose processor, the general-purpose processor may be configured as respectively different special-purpose processors (e.g., comprising different hardware engines) at different times. Software accordingly configures a particular processor or processors, for example, to constitute a particular hardware engine at one instance of time and to constitute a different hardware engine at a different instance of time.
Hardware engines can provide information to, and receive information from, other hardware engines. Accordingly, the described hardware engines may be regarded as being communicatively coupled. Where multiple hardware engines exist contemporaneously, communications may be achieved through signal transmission (e.g., over appropriate circuits and buses) between or among two or more of the hardware engines. In embodiments in which multiple hardware engines are configured or instantiated at different times, communications between such hardware engines may be achieved, for example, through the storage and retrieval of information in memory structures to which the multiple hardware engines have access. For example, one hardware engine may perform an operation and store the output of that operation in a memory device to which it is communicatively coupled. A further hardware engine may then, at a later time, access the memory device to retrieve and process the stored output. Hardware engines may also initiate communications with input or output devices, and can operate on a resource (e.g., a collection of information).
The various operations of example methods described herein may be performed, at least partially, by one or more processors that are temporarily configured (e.g., by software) or permanently configured to perform the relevant operations. Whether temporarily or permanently configured, such processors may constitute processor-implemented engines that operate to perform one or more operations or functions described herein. As used herein, “processor-implemented engine” refers to a hardware engine implemented using one or more processors.
Similarly, the methods described herein may be at least partially processor-implemented, with a particular processor or processors being an example of hardware. For example, at least some of the operations of a method may be performed by one or more processors or processor-implemented engines. Moreover, the one or more processors may also operate to support performance of the relevant operations in a “cloud computing” environment or as a “software as a service” (SaaS). For example, at least some of the operations may be performed by a group of computers (as examples of machines including processors), with these operations being accessible via a network (e.g., the Internet) and via one or more appropriate interfaces (e.g., an Application Program Interface (API)).
The performance of certain of the operations may be distributed among the processors, not only residing within a single machine, but deployed across a number of machines. In some example embodiments, the processors or processor-implemented engines may be located in a single geographic location (e.g., within a home environment, an office environment, or a server farm). In other example embodiments, the processors or processor-implemented engines may be distributed across a number of geographic locations.
Throughout this specification, plural instances may implement components, operations, or structures described as a single instance. Although individual operations of one or more methods are illustrated and described as separate operations, one or more of the individual operations may be performed concurrently, and nothing requires that the operations be performed in the order illustrated. Structures and functionality presented as separate components in example configurations may be implemented as a combined structure or component. Similarly, structures and functionality presented as a single component may be implemented as separate components. These and other variations, modifications, additions, and improvements fall within the scope of the subject matter herein.
Although an overview of the subject matter has been described with reference to specific example embodiments, various modifications and changes may be made to these embodiments without departing from the broader scope of embodiments of the present disclosure. Such embodiments of the subject matter may be referred to herein, individually or collectively, by the term “invention” merely for convenience and without intending to voluntarily limit the scope of this application to any single disclosure or concept if more than one is, in fact, disclosed.
The embodiments illustrated herein are described in sufficient detail to enable those skilled in the art to practice the teachings disclosed. Other embodiments may be used and derived therefrom, such that structural and logical substitutions and changes may be made without departing from the scope of this disclosure. The Detailed Description, therefore, is not to be taken in a limiting sense, and the scope of various embodiments is defined only by the appended claims, along with the full range of equivalents to which such claims are entitled.
It will be appreciated that an “engine,” “system,” “data store,” and/or “database” may comprise software, hardware, firmware, and/or circuitry. In one example, one or more software programs comprising instructions capable of being executable by a processor may perform one or more of the functions of the engines, data stores, databases, or systems described herein. In another example, circuitry may perform the same or similar functions. Alternative embodiments may comprise more, less, or functionally equivalent engines, systems, data stores, or databases, and still be within the scope of present embodiments. For example, the functionality of the various systems, engines, data stores, and/or databases may be combined or divided differently.
“Open source” software is defined herein to be source code that allows distribution as source code as well as compiled form, with a well-publicized and indexed means of obtaining the source, optionally with a license that allows modifications and derived works.
The data stores described herein may be any suitable structure (e.g., an active database, a relational database, a self-referential database, a table, a matrix, an array, a flat file, a documented-oriented storage system, a non-relational No-SQL system, and the like), and may be cloud-based or otherwise.
As used herein, the term “or” may be construed in either an inclusive or exclusive sense. Moreover, plural instances may be provided for resources, operations, or structures described herein as a single instance. Additionally, boundaries between various resources, operations, engines, engines, and data stores are somewhat arbitrary, and particular operations are illustrated in a context of specific illustrative configurations. Other allocations of functionality are envisioned and may fall within a scope of various embodiments of the present disclosure. In general, structures and functionality presented as separate resources in the example configurations may be implemented as a combined structure or resource. Similarly, structures and functionality presented as a single resource may be implemented as separate resources. These and other variations, modifications, additions, and improvements fall within a scope of embodiments of the present disclosure as represented by the appended claims. The specification and drawings are, accordingly, to be regarded in an illustrative rather than a restrictive sense.
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.
Although the invention has been described in detail for the purpose of illustration based on what is currently considered to be the most practical and preferred implementations, it is to be understood that such detail is solely for that purpose and that the invention is not limited to the disclosed implementations, but, on the contrary, is intended to cover modifications and equivalent arrangements that are within the spirit and scope of the appended claims. For example, it is to be understood that the present invention contemplates that, to the extent possible, one or more features of any embodiment can be combined with one or more features of any other embodiment.
This application claims the benefit under 35 U.S.C. § 119(e) of U.S. Provisional Application Ser. No. 62/595,421, filed Dec. 6, 2017, the content of which is incorporated by reference in its entirety into the present disclosure.
| Number | Name | Date | Kind |
|---|---|---|---|
| 3747757 | Freis et al. | Jul 1973 | A |
| 4778219 | Wilczynski et al. | Oct 1988 | A |
| 4899161 | Morin 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 |
| 6091956 | Hollenberg | Jul 2000 | A |
| 6157747 | Szeliski et al. | Dec 2000 | A |
| 6169552 | Endo et al. | Jan 2001 | B1 |
| 6173067 | Payton et al. | Jan 2001 | B1 |
| 6178432 | Cook et al. | Jan 2001 | B1 |
| 6247019 | Davies | Jun 2001 | 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 |
| 6631496 | Li et al. | Oct 2003 | B1 |
| 6662103 | Skolnick et al. | Dec 2003 | B1 |
| 6757445 | Knopp | Jun 2004 | B1 |
| 6828920 | Owen et al. | Dec 2004 | B2 |
| 6983203 | Wako | Jan 2006 | B1 |
| 6985950 | Hanson et al. | Jan 2006 | B1 |
| 7036085 | Barros | Apr 2006 | B2 |
| 7158878 | Rasmussen et al. | Jan 2007 | B2 |
| 7375732 | Arcas | May 2008 | B2 |
| 7379811 | Rasmussen et al. | May 2008 | B2 |
| 7457706 | Malero et al. | Nov 2008 | B2 |
| 7502786 | Liu et al. | Mar 2009 | B2 |
| 7519470 | Brasche 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 |
| 7579965 | Bucholz | Aug 2009 | B2 |
| 7617314 | Bansod et al. | Nov 2009 | B1 |
| 7620628 | Kapur et al. | Nov 2009 | B2 |
| 7663621 | Allen et al. | Feb 2010 | B1 |
| 7791616 | Ioup et al. | Sep 2010 | B2 |
| 7805457 | Viola et al. | Sep 2010 | B1 |
| 7809703 | Balabhadrapatruni et al. | Oct 2010 | B2 |
| 7872647 | Mayer et al. | Jan 2011 | B2 |
| 7894984 | Rasmussen et al. | Feb 2011 | B2 |
| 7899611 | Downs et al. | Mar 2011 | B2 |
| 7920963 | Jouline et al. | Apr 2011 | B2 |
| 7945852 | Pilskains | May 2011 | B1 |
| 7962281 | Rasmussen et al. | Jun 2011 | B2 |
| 7970240 | Chao et al. | Jun 2011 | B1 |
| 8010545 | Stefik et al. | Aug 2011 | B2 |
| 8036632 | Cona et al. | Oct 2011 | B1 |
| 8065080 | Koch | Nov 2011 | B2 |
| 8085268 | Carrino et al. | Dec 2011 | B2 |
| 8134457 | Velipasalar et al. | Mar 2012 | B2 |
| 8145703 | Frishert et al. | Mar 2012 | B2 |
| 8200676 | Frank | Jun 2012 | B2 |
| 8214361 | Sandler et al. | Jul 2012 | B1 |
| 8214764 | Gemmell et al. | Jul 2012 | B2 |
| 8229947 | Fujinaga | Jul 2012 | B2 |
| 8230333 | Decherd et al. | Jul 2012 | B2 |
| 8290942 | Jones et al. | Oct 2012 | B2 |
| 8290943 | Carbone et al. | Oct 2012 | B2 |
| 8301464 | Cave et al. | Oct 2012 | B1 |
| 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 |
| 8407180 | Ramesh et al. | Mar 2013 | B1 |
| 8412234 | Gatmir-Motahari et al. | Apr 2013 | B1 |
| 8412707 | Mianji | Apr 2013 | B1 |
| 8422825 | Neophytou et al. | Apr 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 |
| 8508533 | Cervelli et al. | Aug 2013 | B2 |
| 8514229 | Cervelli et al. | Aug 2013 | B2 |
| 8515207 | Chau | Aug 2013 | B2 |
| 8564596 | Carrino et al. | Oct 2013 | B2 |
| 8700620 | Lieberman | Apr 2014 | B1 |
| 8742934 | Sarpy et al. | Jun 2014 | B1 |
| 8781169 | Jackson et al. | Jul 2014 | B2 |
| 8799799 | Cervelli et al. | Aug 2014 | B1 |
| 8830322 | Nerayoff et al. | Sep 2014 | B2 |
| 8938686 | Erenrich et al. | Jan 2015 | B1 |
| 8949164 | Mohler | Feb 2015 | B1 |
| 8983494 | Onnen et al. | Mar 2015 | B1 |
| 9009177 | Zheng et al. | Apr 2015 | B2 |
| 9021384 | Beard et al. | Apr 2015 | B1 |
| 9104293 | Kornfeld et al. | Aug 2015 | B1 |
| 9104695 | Cervelli et al. | Aug 2015 | B1 |
| 9111380 | Piemonte et al. | Aug 2015 | B2 |
| 9129219 | Robertson et al. | Sep 2015 | B1 |
| 9146125 | Vulcano et al. | Sep 2015 | B2 |
| 9280618 | Bruce et al. | Mar 2016 | B1 |
| 9348880 | Kramer et al. | May 2016 | B1 |
| 9424545 | Lee | Aug 2016 | B1 |
| 9514205 | Yazicioglu et al. | Dec 2016 | B1 |
| 9514414 | Rosswog et al. | Dec 2016 | B1 |
| 9612723 | Elliot et al. | Apr 2017 | B1 |
| 9760606 | Wilczynski et al. | Sep 2017 | B1 |
| 20020003539 | Abe | Jan 2002 | A1 |
| 20020033848 | Sciammarella et al. | Mar 2002 | A1 |
| 20020116120 | Ruiz et al. | Aug 2002 | A1 |
| 20020130867 | Yang et al. | Sep 2002 | A1 |
| 20020130906 | Miyaki | Sep 2002 | A1 |
| 20030052896 | Higgins et al. | Mar 2003 | A1 |
| 20030103049 | Kindratenko et al. | Jun 2003 | A1 |
| 20030144868 | MacIntyre et al. | Jul 2003 | A1 |
| 20030163352 | Surpin et al. | Aug 2003 | A1 |
| 20030225755 | Iwayama et al. | Dec 2003 | A1 |
| 20040030492 | Fox et al. | Feb 2004 | A1 |
| 20040039498 | Ollis et al. | Feb 2004 | A1 |
| 20040093344 | Berger et al. | May 2004 | A1 |
| 20040098236 | Mayer et al. | May 2004 | A1 |
| 20050031197 | Knopp | Feb 2005 | A1 |
| 20050034062 | Bufkin et al. | Feb 2005 | A1 |
| 20050080769 | Gemmell | Apr 2005 | A1 |
| 20050143602 | Yada et al. | Jun 2005 | A1 |
| 20050162523 | Darrell et al. | Jul 2005 | A1 |
| 20050182502 | Iyengar | Aug 2005 | A1 |
| 20050182793 | Keenan et al. | Aug 2005 | A1 |
| 20050223044 | Ashworth et al. | Oct 2005 | A1 |
| 20050267652 | Allstadt et al. | Dec 2005 | A1 |
| 20060026170 | Kreitler et al. | Feb 2006 | A1 |
| 20060139375 | Rasmussen et al. | Jun 2006 | A1 |
| 20060146050 | Yamauchi | Jul 2006 | A1 |
| 20060149596 | Surpin et al. | Jul 2006 | A1 |
| 20060200384 | Arutunian et al. | Sep 2006 | A1 |
| 20060251307 | Florin et al. | Nov 2006 | A1 |
| 20060259527 | Devarakonda et al. | Nov 2006 | A1 |
| 20060271277 | Hu et al. | Nov 2006 | A1 |
| 20060279630 | Aggarwal et al. | Dec 2006 | A1 |
| 20070011150 | Frank | Jan 2007 | A1 |
| 20070016363 | Huang et al. | Jan 2007 | A1 |
| 20070024620 | Muller-Fischer et al. | Feb 2007 | A1 |
| 20070057966 | Ohno et al. | Mar 2007 | A1 |
| 20070078832 | Ott et al. | Apr 2007 | A1 |
| 20070115373 | Gallagher et al. | May 2007 | A1 |
| 20070132767 | Wright | Jun 2007 | A1 |
| 20070188516 | Loup et al. | Aug 2007 | A1 |
| 20070208497 | Downs et al. | Sep 2007 | A1 |
| 20070208498 | Barker et al. | Sep 2007 | A1 |
| 20070258642 | Thota | Nov 2007 | A1 |
| 20070294643 | Kyle | Dec 2007 | A1 |
| 20080010605 | Frank | Jan 2008 | A1 |
| 20080040684 | Crump | Feb 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 |
| 20080133579 | Lim | Jun 2008 | A1 |
| 20080163073 | Becker et al. | Jul 2008 | A1 |
| 20080192053 | Howell et al. | Aug 2008 | A1 |
| 20080195417 | Surpin et al. | Aug 2008 | A1 |
| 20080223834 | Griffiths et al. | Sep 2008 | A1 |
| 20080229056 | Agarwal et al. | Sep 2008 | A1 |
| 20080263468 | Cappione et al. | Oct 2008 | A1 |
| 20080267107 | Rosenberg | Oct 2008 | A1 |
| 20080270468 | Mao | Oct 2008 | A1 |
| 20080278311 | Grange et al. | Nov 2008 | A1 |
| 20080288306 | MacIntyre 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 |
| 20090088964 | Schaaf et al. | Apr 2009 | A1 |
| 20090100018 | Roberts | Apr 2009 | A1 |
| 20090115786 | Shmiasaki et al. | May 2009 | A1 |
| 20090132921 | Hwangbo 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 |
| 20090171939 | Athsani et al. | Jul 2009 | A1 |
| 20090172511 | Decherd et al. | Jul 2009 | A1 |
| 20090179892 | Tsuda et al. | Jul 2009 | A1 |
| 20090187447 | Cheng et al. | Jul 2009 | A1 |
| 20090187464 | Bai et al. | Jul 2009 | A1 |
| 20090222400 | Kupershmidt et al. | Sep 2009 | A1 |
| 20090292626 | Oxford | Nov 2009 | A1 |
| 20100057716 | Stefik et al. | Mar 2010 | A1 |
| 20100063961 | Guiheneuf et al. | Mar 2010 | A1 |
| 20100070523 | Delgo et al. | Mar 2010 | A1 |
| 20100076968 | Boyns et al. | Mar 2010 | A1 |
| 20100106420 | Mattikalli et al. | Apr 2010 | A1 |
| 20100162176 | Dunton | Jun 2010 | A1 |
| 20100185692 | Zhang et al. | Jul 2010 | A1 |
| 20100198684 | Eraker et al. | Aug 2010 | A1 |
| 20100199225 | Coleman et al. | Aug 2010 | A1 |
| 20100277611 | Holt et al. | Nov 2010 | A1 |
| 20100293174 | Bennett et al. | Nov 2010 | A1 |
| 20100321399 | Ellren et al. | Dec 2010 | A1 |
| 20110022312 | McDonough et al. | Jan 2011 | A1 |
| 20110090254 | Carrino et al. | Apr 2011 | A1 |
| 20110117878 | Barash et al. | May 2011 | A1 |
| 20110119295 | Zaengle | May 2011 | A1 |
| 20110137766 | Rasmussen et al. | Jun 2011 | A1 |
| 20110153368 | Pierre et al. | Jun 2011 | A1 |
| 20110161096 | Buehler et al. | Jun 2011 | A1 |
| 20110170799 | Carrino et al. | Jul 2011 | A1 |
| 20110208724 | Jones et al. | Aug 2011 | A1 |
| 20110218934 | Elser | Sep 2011 | A1 |
| 20110225198 | Edwards et al. | Sep 2011 | A1 |
| 20110238690 | Arrasvuori et al. | Sep 2011 | A1 |
| 20110270705 | Parker | Nov 2011 | A1 |
| 20120066296 | Appleton et al. | Mar 2012 | A1 |
| 20120084118 | Bai et al. | Apr 2012 | A1 |
| 20120106801 | Jackson | May 2012 | A1 |
| 20120144335 | Abeln et al. | Jun 2012 | A1 |
| 20120158527 | Cannelongo et al. | Jun 2012 | A1 |
| 20120159363 | DeBacker et al. | Jun 2012 | A1 |
| 20120173985 | Peppel | Jul 2012 | A1 |
| 20120206469 | Hulubei et al. | Aug 2012 | A1 |
| 20120208636 | Feige | Aug 2012 | A1 |
| 20120221580 | Barney | Aug 2012 | A1 |
| 20120323888 | Osann, Jr. | Dec 2012 | A1 |
| 20130006725 | Simanek et al. | Jan 2013 | A1 |
| 20130021445 | Cossette-Pacheco et al. | Jan 2013 | A1 |
| 20130057551 | Ebert et al. | Mar 2013 | A1 |
| 20130060786 | Serrano et al. | Mar 2013 | A1 |
| 20130073377 | Heath | Mar 2013 | A1 |
| 20130076732 | Cervelli et al. | Mar 2013 | A1 |
| 20130100134 | Cervelli et al. | Apr 2013 | A1 |
| 20130101159 | Chao et al. | Apr 2013 | A1 |
| 20130132398 | Pfiefle | May 2013 | A1 |
| 20130150004 | Rosen | Jun 2013 | A1 |
| 20130176321 | Mitchell et al. | Jul 2013 | A1 |
| 20130179420 | Park et al. | Jul 2013 | A1 |
| 20130254900 | Sathish et al. | Sep 2013 | A1 |
| 20130268520 | Fisher et al. | Oct 2013 | A1 |
| 20130279757 | Kephart | Oct 2013 | A1 |
| 20130282723 | Petersen et al. | Oct 2013 | A1 |
| 20130330055 | Zimmermann | Dec 2013 | A1 |
| 20130339891 | Blumenberg et al. | Dec 2013 | A1 |
| 20140176606 | Narayan et al. | Jun 2014 | A1 |
| 20140218400 | O'Toole et al. | Aug 2014 | A1 |
| 20140333651 | Cervelli et al. | Nov 2014 | A1 |
| 20140337772 | Cervelli et al. | Nov 2014 | A1 |
| 20140361899 | Layson | Dec 2014 | A1 |
| 20150029176 | Baxter et al. | Jan 2015 | A1 |
| 20150100907 | Erenrich et al. | Apr 2015 | A1 |
| 20150106170 | Bonica | Apr 2015 | A1 |
| 20150186821 | Wang et al. | Jul 2015 | A1 |
| 20150187036 | Wang et al. | Jul 2015 | A1 |
| 20150187100 | Berry et al. | Jul 2015 | A1 |
| 20150227972 | Tang | Aug 2015 | A1 |
| 20150312323 | Peterson | Oct 2015 | A1 |
| 20150338233 | Cervelli | Nov 2015 | A1 |
| 20150379413 | Robertson et al. | Dec 2015 | A1 |
| 20160188557 | Spanu | Jun 2016 | A1 |
| 20160334974 | Gray et al. | Nov 2016 | A1 |
| 20170154109 | Lynch | Jun 2017 | A1 |
| Number | Date | Country |
|---|---|---|
| 2012216622 | May 2015 | AU |
| 102013222023 | Jan 2015 | DE |
| 0 763 201 | Mar 1997 | EP |
| 2 575 107 | Apr 2013 | EP |
| 2858014 | Apr 2015 | EP |
| 2963595 | Jan 2016 | EP |
| 2516155 | Jan 2015 | GB |
| 2012778 | Nov 2014 | NL |
| 624557 | Dec 2014 | NZ |
| WO 95032424 | Nov 1995 | WO |
| WO 2000009529 | Feb 2000 | WO |
| WO 2001098925 | Dec 2001 | WO |
| WO 2004057268 | Jul 2004 | WO |
| WO 2005013200 | Feb 2005 | WO |
| WO 2008064207 | May 2008 | WO |
| WO 2009061501 | May 2009 | WO |
| WO 2009123975 | Oct 2009 | WO |
| WO 2011058507 | May 2011 | WO |
| Entry |
|---|
| “A First Look: Predicting Market Demand for Food Retail using a Huff Analysis,” TRF Policy Solutions, Jul. 2012, pp. 30. |
| “Andy Turner's GISRUK 2012 Notes” <https://docs.google.com/document/d/1cTmxg7mVx5gd89lqblCYvCEnHA4QAivH4l4WpyPsqE4/edit?pli=1> printed Sep. 16, 2013 in 15 pages. |
| “HunchLab: Heat Map and Kernel Density Calculation for Crime Analysis,” Azavea Journal, printed from www.azavea.com/blogs/newsletter/v4i4/kernel-density-capabilities-added-to-hunchlab/ on Sep. 9, 2014, 2 pages. |
| Barnes et al., “Viewshed Analysis”, GIS-ARC/INFO 2001, <www.evsc.virginia.edu/˜jhp7e/evsc466/student_pres/Rounds.pdf>. |
| 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. |
| Chen et al., “Bringing Order to the Web: Automatically Categorizing Search Results,” CHI 2000, Proceedings of the SIGCHI conference on Human Factors in Computing Systems, Apr. 1-6, 2000, The Hague, The Netherlands, pp. 145-152. |
| Chen et al., “Context-Aware Mashup for Smart Mobile Devices,” 2012 IEEE Asia-Pacific Services Computing Conference Year: 2012, pp. 179-186. |
| Definition “Identify”, downloaded Jan. 22, 2015, 1 page. |
| Definition “Overlay”, downloaded Jan. 22, 2015, 1 page. |
| 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. |
| Garcia et al., “A Matchmaking Algorithm for Resource Discovery in Multi-user Settings,” 2014 IEEE/WIC/ACM International Joint Conferences on Web Intelligence (WI) and Intelligent Agent Technologies (IAT) Year: 2014, vol. 3, pp. 352-359. |
| 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. |
| GIS-NET 3 Public _ Department of Regional Planning. Planning & Zoning Information for Unincorporated La County. Retrieved Oct. 2, 2013 from http://gis.planning.lacounty.gov/GIS-NET3_Public/Viewer.html. |
| Gorr et al., “Crime Hot Spot Forecasting: Modeling and Comparative Evaluation”, Grant 98-IJ-CX-K005, May 6, 2002, 37 pages. |
| Griffith, Daniel A., “A Generalized Huff Model,” Geographical Analysis, Apr. 1982, vol. 14, No. 2, pp. 135-144. |
| 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. |
| Hibbert et al., “Prediction of Shopping Behavior Using a Huff Model Within a GIS Framework,” Healthy Eating in Context, Mar. 18, 2011, pp. 16. |
| Huang et al., “Systematic and Integrative Analysis of Large Gene Lists Using DAVID Bioinformatics Resources,” Nature Protocols, 4.1, 2008, 44-57. |
| 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. |
| 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. |
| Lin et al., “PRADA: Prioritized Random Access with Dynamic Access Barring for MTC in 3GPP LTE-A Networks,” IEEE Transactions on Vehicular Technology Year: 2014, vol. 63, Issue 5, pp. 2467-2472. |
| 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. |
| Mandagere, Nagapramod, “Buffer Operations in GIS,” <http://www-users.cs.umn.edu/˜npramod/enc_pdf.pdf> retrieved Jan. 28, 2010, 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. |
| Map of San Jose, CA. Retrieved Oct. 2, 2013 from http://maps.yahoo.com. |
| Map of San Jose, CA. Retrieved Oct. 2, 2013 from http://maps.bing.com. |
| Map of San Jose, CA. Retrieved Oct. 2, 2013 from http://maps.google.com. |
| 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. |
| Na et al., “Design of Location-based Directory Facilitator in Context-Aware Environment,” 2008 10th International Conference on Advanced Communication Technology Year: 2008, vol. 3, pp. 2107-2110. |
| 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_you_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. |
| Qiu, Fang, “3d Analysis and Surface Modeling”, <http://web.archive.org/web/20091202221925/http://www.utsa.edu/Irsg/Teaching/EES6513/08-3D.pdf> printed Sep. 16, 2013 in 26 pages. |
| 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-classi_ed 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. |
| Thompson, Mick, “Getting Started with GEO,” Getting Started with GEO, Jul. 26, 2011. |
| Valentini et al., “Ensembles of Learning Machines”, M. Marinaro and R. Tagliaferri (Eds.): WIRN VIETRI 2002, LNCS 2486, pp. 3-20. |
| 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, “Douglas_Peucker-Algorithms,” <http://de.wikipedia.org/w/index.php?title=Douglas-Peucker-Algorithmus&oldid=91846042> printed Jul. 2011, pp. 2. |
| Wikipedia, “Ramer_Douglas_Peucker Algorithm,” <http://en.wikipedia.org/wiki/Ramer%E2%80%93Douglas%E2%80%93Peucker_algorithm> printed Jul. 2011, pp. 3. |
| Wongsuphasawat et al., “Visual Analytics for Transportation Incident Data Sets,” Transportation Research Record 2138, 2009, pp. 135-145. |
| Woodbridge, Stephen, “[geos-devel] Polygon simplification,” <http://lists.osgeo.org/pipermail/geos-devel/2011-May/005210.html> dated May 8, 2011, pp. 3. |
| Number | Date | Country | |
|---|---|---|---|
| 62595421 | Dec 2017 | US |
