Supporting multiple different applications having different data needs using a voxel database

• US 8,190,585 B2
• Filed: 02/17/2010
• Issued: 05/29/2012
• Est. Priority Date: 02/17/2010
• Status: Active Grant

• Current Assignee: Lockheed Martin Corporation (Martin Marietta Corporation)
• Original Assignee: Lockheed Martin Corporation (Martin Marietta Corporation)
• Inventors: Salemann, Leo
• Primary Examiner(s): Alam, Shahid
• Assistant Examiner(s): PANDYA, JAGDISH J
• Application Number:
  US12/707,231
• Publication Number:
  US 20110202510A1
• Time in Patent Office: 832 Days
• Field of Search: 707/693, 707/723, 707/769, 707/802, 345/424
• US Class Current: 707/693
• CPC Class Codes: G06F 16/29 Geographical information databases
• CPC Class Codes: G06T 17/05 Geographic models

Abstract

A system can include a voxel database and the set of applications. The voxel database can include a set of voxel indexed records, wherein the voxel database manages a volumetric storage space corresponding to a real-world volumetric space, where units of real-world volumetric space and data specific to these units map to voxels and attributes of voxel indexed records. Each of the applications can include a user interface that renders a volumetric simulation space that corresponds to the volumetric storage space. Geospatial data for the simulation space can include visual attributes used to render a graphical user interface representation of the simulation space, where these visual attributes are acquired from the voxel database. The applications can have different geospatial formatting and content needs from each other, yet the content needs of each of the applications can be supported by the voxel database.

Claims

1. A method for providing geospatial data to a plurality of applications comprising:

populating a voxel database with geospatial information specific to a real-world volumetric space, the voxel database representing a volumetric storage space comprising a set of unique volumetric storage units called voxels, wherein data elements are stored to specific ones of the voxels, wherein a spatial position of the data elements within the volumetric storage space is defined at least in part by which of the voxels the data elements are stored;

receiving information requests having different formats for different applications;

for each information request;

identifying a volumetric sub-region of the volumetric storage space for the information request;

receiving a set of data elements from the voxel database for the volumetric sub-region, where the set of data elements satisfy the information request;

detecting a set of objects contained in the volumetric sub-region and detailed in raster format within the data elements, wherein the set of objects are not specifically delineated as discrete objects within the voxel database, wherein a spatial position of each of the set of objects is determined based at least in part upon spatial information of applicable ones of the voxels; and

producing a response data set comprising the set of objects and the spatial position of each object in the set of objects, wherein the response data set is produced in the one of the different formats appropriate for the one of the different applications for which the information request was issued, wherein the response data set comprises geospatially correlated information needed by one of the different applications to represent a simulation space within a user interface of that one of the different applications, wherein the simulation space corresponds to a volume of the real-world volumetric space that is associated with the volumetric sub-region of the volumetric storage space.

2. The method of claim 1, wherein one of the plurality of different applications is a live simulation application, wherein another of the different applications is a virtual simulation application, and wherein another of the different applications is a constructive simulation application.

3. The method of claim 1, wherein at least one of the different applications is a voxel-based application where the response data set received by the voxel-based application is in a voxel format, wherein according to the voxel format, content is indexed against uniquely identified volumetric units and where a visual interface of the voxel-based application is rendered by a voxel graphics engine, and wherein at least one of the different applications is a vector-based application where the converted data set received by the vector-based application is in vector format, wherein according to the vector format, content is indexed against discrete and uniquely identified objects having a set of points, each of which is defined by a three-dimension coordinate and where a visual interface of the vector-based application is rendered by a polygon graphics engine.

4. The method of claim 1, wherein one of the different applications is a semi-autonomous force (SAF) simulation application, wherein one of the different applications is a tactical engagement system (TES) simulation application, and wherein one of the different applications is an immersion simulation application.

5. The method of claim 1, wherein for one of the different applications the response data set is used by an application that is a stand-alone product that lacks runtime connectivity to the voxel database.

6. The method of claim 1, wherein for one of the different application, a plurality of different ones of the response data set is periodically provided to the application at runtime, where each response data set of the plurality that is provided to and used by the application represents a specific and non-overlapping geospatial region of simulator space.

7. The method of claim 1, wherein for one of the different applications the response data set is continuously provided as a stream of data conveyed between the application and the voxel database in real-time, where the stream of data is used at least in part to dynamically generate terrain for a user interface of the application.

8. The method of claim 1, wherein the populating of the voxel database further comprises:

storing and combining geospatial information captured from real-world sensors in the voxel database, such that each voxel in the voxel database represents a combination of volumetrically stored geospatial information available for that volume of volumetric storage space.

9. The method of claim 8, wherein the geospatial information that is stored and combined into the voxel database comprise point cloud data, imagery and video data, and elevation data, wherein the point cloud data is encoded in a light detecting and ranging (LiDAR) information format, wherein the elevation data is encoded in a digital elevation model (DEM) or digital surface model (DSM) format.

10. The method of claim 1, further comprising:

a plurality of sensors capturing raw data that geospatially corresponds to a real world volumetric space, wherein the raw data comprises point cloud data encoded in a light detecting and ranging (LiDAR) information format, comprises imagery and video data, and comprises elevation data encoded in a digital elevation model (DEM) or digital surface model (DSM) format;

storing and combining the raw data in the voxel database such that each voxel in the voxel database represents a combination of volumetrically stored data for all source products that includes products providing point cloud data, imagery and video data, and elevation data;

the voxel database receiving the information requests from a plurality of different applications;

for each of the different applications associated with one of the information requests request;

determining an application specific plug-in;

executing the application specific plug-in to convert the voxel database data into an application specific format; and

providing the voxel database data to the application from which the request was issued.

11. A computer program product for providing geospatial data to a plurality of applications, the computer program product comprising:

a tangible non-transitory computer readable storage medium having computer usable program code embodied therewith, the computer usable program code comprising;

computer usable program code operable to populate a voxel database with geospatial information specific to a real-world volumetric space, the voxel database representing a volumetric storage space comprising a set of unique volumetric storage units called voxels, wherein data elements are stored to specific ones of the voxels, wherein a spatial position of the data elements within the volumetric storage space is defined at least in part by which of the voxels the data elements are stored;

computer usable program code operable to receive information requests having different formats for different applications;

computer usable program code operable to, for each information request;

identify a volumetric sub-region of the volumetric storage space for the information request;

receive a set of data elements from the voxel database for the volumetric sub-region, where the set of data elements satisfy the information request;

detect a set of objects contained in the volumetric sub-region and detailed in raster format within the data elements, wherein the set of objects are not specifically delineated as discrete objects within the voxel database, wherein a spatial position of each of the set of objects is determined based at least in part upon spatial information of applicable ones of the voxels; and

produce a response data set comprising the set of objects and the spatial position of each object in the set of objects, wherein the response data set is produced in the one of the different formats appropriate for the one of the different applications for which the information request was issued, wherein the response data set comprises geospatially correlated information needed by one of the different applications to represent a simulation space within a user interface of that one of the different applications, wherein the simulation space corresponds to a volume of the real-world volumetric space that is associated with the volumetric sub-region of the volumetric storage space.

12. A system for managing geospatial data used by a plurality of applications comprising:

populating a voxel database with geospatial information specific to a real-world volumetric space, the voxel database representing a volumetric storage space comprising a set of unique volumetric storage units called voxels, wherein data elements are stored to specific ones of the voxels, wherein a spatial position of the data elements within the volumetric storage space is defined at least in part by which of the voxels the data elements are stored;

receiving information requests having different formats for different applications;

for each information request;

identifying a volumetric sub-region of the volumetric storage space for the information request;

receiving a set of data elements from the voxel database for the volumetric sub-region, where the set of data elements satisfy the information request;

detecting a set of objects contained in the volumetric sub-region and detailed in raster format within the data elements, wherein the set of objects are not specifically delineated as discrete objects within the voxel database, wherein a spatial position of each of the set of objects is determined based at least in part upon spatial information of applicable ones of the voxels; and

producing a response data set comprising the set of objects and the spatial position of each object in the set of objects, wherein the response data set is produced in the one of the different formats appropriate for the one of the different applications for which the information request was issued, wherein the response data set comprises geospatially correlated information needed by one of the different applications to represent a simulation space within a user interface of that one of the different applications, wherein the simulation space corresponds to a volume of the real-world volumetric space that is associated with the volumetric sub-region of the volumetric storage space.

13. The system of claim 12, wherein one of the plurality of applications is a live simulator application, wherein another of the different applications is a virtual simulator application, and wherein another of the applications is a constructive simulator application.

14. The system of claim 12, wherein one of the applications is a semi-autonomous force (SAF) simulator application, wherein one of the different applications is a tactical engagement system (TES) simulator application, and wherein one of the different applications is an immersion simulator application.

15. The system of claim 12, wherein at least one of the applications is a voxel-based application where the converted data set received by the voxel-based application is in voxel format, where content is indexed against uniquely identified volumetric units and where a visual interface of the voxel-based application is rendered by a voxel graphics engine, and wherein at least one of the different applications is a vector-based application where the converted data set received by the vector-based application is in vector format, where content is indexed against discrete and uniquely identified objects having a set of points, each of which is defined by a three-dimension coordinate and where a visual interface of the vector-based application is rendered by a polygon graphics engine.

16. The system of claim 12, wherein one of the application receives a live stream of terrain data from the voxel database in real time, wherein another one of the applications receives iterative updates from the voxel database as needed where each update is for a non-overlapping geospatial region of simulation space that corresponds to a real-world geospatial region, and wherein one of the application is a stand-alone product that lacks runtime connectivity to the voxel database.

17. The system of claim 12, wherein each voxel of the voxel database comprises data combined from a plurality of different discrete products such that each voxel in the voxel database represents a combination of volumetrically stored data for all of the different discrete products, said different discrete products comprising point cloud products comprising point cloud data encoded in a light detecting and ranging (LiDAR) information format, imagery products comprising imagery and video data, and comprising elevation products comprising elevation data encoded in a digital elevation model (DEM) or digital surface model (DSM) format.

18. The system of claim 12, wherein the voxel database stores high fidelity content of terrain having a six inch or smaller ground separation distance between datum points, wherein the density of data in the voxel database has reached a cross-over point, where it is more efficient to store equivalent data within the voxel database than it is to store equivalent data in a non-voxel geospatial database.

19. The system of claim 12, wherein the voxel database comprises a heterogeneous database for internal storing of different semantic content in different manners, which are transparent to external entities that view the voxel database as a single unified database having a consistent externally facing interface.

20. The system of claim 12, further comprising:

a voxel server for managing data of the voxel database and for supporting the plurality of application from the data encoded in the voxel database; and

a plurality of application plug-ins each for a specific one of the applications, wherein said voxel server using said application plug-ins is operable to provide related ones of the applications with real-time streaming of terrain models based on voxel database encoded geospatial content.

21. The system of claim 20, wherein said voxel server further comprises:

a terrain manager for providing a unified external interface for receiving and responding to information requests; and

a compression engine for compressing voxel database stored data comprising semantic content from elevation products, imagery products, and point cloud products; and

a voxel query engine for providing a unified and consistent way to accept and respond to structured queries.

22. The system of claim 12, wherein said voxel database comprises:

a plurality of voxel records in a voxel table, where each of the records has a unique voxel identifier, wherein said voxel table is stored in a tangible storage medium; and

a plurality of feature records in a plurality of feature tables, wherein each of the feature records comprises a unique feature identifier, a feature type, and a plurality of feature attributes, wherein a feature corresponds to a real world object, wherein different feature tables are tables specific to different types of real world objects, and wherein the feature attributes of the feature tables are specific attributes for the real world objects, which vary from feature table to feature table; and

a plurality of shape records in a shape table, wherein each of the shape records comprises a unique shape identifier, a shape type, a plurality of shape attributes, and a foreign key to a feature identifier, wherein types of shapes are primitive shapes that comprise a box, a cylinder, a sphere, and a cone, wherein a one-to-many relationship exists between features and shapes, wherein each record of the voxel table comprises a foreign key to a shape identifier, wherein a one-to-many relationship exists between voxels and primitive shapes.