• Antelope Release 5.5 Mac OS X 10.8.5 2015-04-21

 

NAME

exportgrid - ascii output of GCLgrid objects

SYNOPSIS

exportgrid db|fname gridname [-fin -f fieldname -3d -vector n -o outfile -dir outdir]

SUPPORT


Contributed code: NO BRTT support.
THIS PIECE OF SOFTWARE WAS CONTRIBUTED BY THE ANTELOPE USER COMMUNITY. BRTT DISCLAIMS ALL OWNERSHIP, LIABILITY, AND SUPPORT FOR THIS PIECE OF SOFTWARE.

FOR HELP WITH THIS PIECE OF SOFTWARE, PLEASE CONTACT THE CONTRIBUTING AUTHOR.

DESCRIPTION

This is a relatively crude program to output the contents of various GCLgrid related objects as simple ascii data. This implementation supports three data type: GCLgrid, GCLgrid3d, GCLscalarfield, GCLscalarfield3d, GCLvectorfield, and GCLvectorfield3d. In all cases the object's contents are dumped to stdout. The type of object to dump is implied from combinations of the arguments passed to the program. See the following section for a description of how this works. The default requires two arguments. The first is one of two things depending on whether or not the flag -fin is used. If -fin does not appear (the default) db is assumed to be an Antelope database name containing at least a gclgdisk table and gclfield table if a field object is to being referenced. If the -fin flag appears argument 1 is assumed to a base file name where the data are stored. Argument 2, gridname, is also required. It defines a unique name assigned to a particular grid referenced in the gclgdisk table. Although it is required it is ignored for file input mode.

OPTIONS

The -f, -3d, and -vector options work together to define the type of object the program tries to load. If -f is not used the assumption is only grid geometry is to be written to output. The -3d option is a switch between the class of 2d and 3d GCLgrid/field objects. Finally, the -vector argument is required if a field being referenced is a vector field.

FILES

At this time the output format is very different for field objects and grid objects. The format for grid object is simpler and is just a series of blank separated fields defining (in order): latitude (degrees), longitude (degrees), and depth (km).

For field data this program is little more than a front end for the C++ operator << for these objects. The format is:

Line 1: is a blank separated list of two or three integers; two for 2d and three for 3d data. These define the number of node points in x1, x2, and x3 directions respectively.

The remainder of the file is a series of lines with a count equal to the product of the integers printed on line 1. Each line of these lines is a blank separated list of attributes in the following order: x1, x2, x3, latitude, longitude, radius, val(1), ..., val(nv) where x1,x2, and x3 are the location of this grid point in the Cartesian system used internally by the GCLgrid library; latitude, longitude, and radius are Earth coordinates, and val(1) to val(nv) are the nv data values associated with this grid point. For scalar fields nv is 1 so there is only one val.

SEE ALSO

http://www.indiana.edu/~pavlab/software/gclgrid/html/index.html

BUGS AND CAVEATS

AUTHOR

Gary L. Pavlis
Indiana University
pavlis@indiana.edu

Antelope User Group Contributed Software
Printer icon