Data sets used in scientific visualization often require preprocessing. The complexity of this preprocessing and the large size of the data sets add to the overall difficulty of the analysis. For example, the nonstandard digital orthophoto quadrangle (DOQ) file used in this project required approximately 8 megabytes of storage and can be considered a large earth-science data set. In addition, a standard DOQ having a 1-m resolution can be as large as 50 megabytes. The software used to prepare and visualize these large spatial data sets typically has to simultaneously manipulate several large working data sets. In addition to keeping costs down, the capability to handle many large spatial data sets was one of the project's reasons for selecting ARC/INFO, Khoros, and Surveyor.
The Khoros visual programming environment is an image-processing system that can distribute
its processing over a local-area network or a wide-area network. The JPL Surveyor system
is used to generate terrain flybys. In this project, data management (for example, data
importing) and some data manipulation (for example, data set gridding and regridding)
were performed by an off-the-shelf commercial geographic information system (GIS) software,
ARC/INFO. After the DOQ, digital elevation model (DEM), and digital line graph (DLG) images
were preprocessed in ARC/INFO, Khoros was used to merge the ARC/INFO DLG (that is, roads
and streams) rasterized images with the DOQ image and produce red, green, and blue (RGB)
images. In turn, these preprocessed Khoros RGB images were used to construct flight paths
and create animation frames in Surveyor. This process flow is illustrated in
figure 1.
The user specifies the Khoros input files and the Surveyor pyramid database levels. Alternatively, the input files may be specified by connecting the glyphs symbolically. A second glyph was also constructed as part of the software integration effort. This glyph, arc2viff, converted ARC/INFO raster files to Khoros VIFF-formatted files. In addition to taking the ARC/INFO raster file name as input, this second glyph required the ARC/INFO header file name associated with the ARC/INFO raster file. The header file provides the number of rows, the number of columns, and the data type of the raster file. The output file name also had to be specified. Figure 3 illustrates the open arc2viff glyph.
Return to Bulletin 2103 Contents