DESCRIPTION

       Segysql  creates SQLite databases from the file and trace header infor-
       mation in SEGY seismic data files.

       If your file is not fully SEGY Rev 1 compliant, you  must  specify  the
       appropriate driver for vender modifications.

       Specify as many SEGY files on the command line as you would like.

       usage: segysql.py [options] segyfile1 segyfile2 ... segyfileN

   options:
       --version
              show program's version number and exit

       -h, --help
              show this help message and exit

       -n, --no-create
              do  NOT  create  the tables.  Assume that they have already been
              created.  Use this to append data.

       -d DRV, --driver=DRV
              specify  which   driver   to   parse   data   file.    [default:
              segy_drv_rev1]

       -D, --delete
              delete previous db if it exists  [default: False]

       -f DBFILENAME, --file=DBFILENAME
              file for the sqlite database  [default: segy.db]

       -s, --shortList
              use short list for keys to use [default: False]

       -t, --test
              only put the first few traces of each segy file in the database

       -w, --warn-only
              Allow  processing  to  continue  in  certain  error  conditions.
              [default: False]

       -v, --verbose
              how  much  information  to  give.   Specify  multiple  times  to
              increase verbosity

       --verbosity=VERBOSITY
              Specify verbosity.  Should be in the range of 0...4 (None...Bom-
              bastic)

       --noisy
              Go for the max verbosity [8]

          sqlite segy.db "select * from segyTrace" | less

       To print the trace locations for a dataset that is all in  "Seconds  of
       Arc" format:

          sqlite xstar.db 'select x/3600.0,y/3600.0 from segyTrace'

LIMITATIONS

       It  is  currently  limited  to  working  with  one  SEGY  data type per
       database.  For example, mixing inserts into one database file from SEGY
       Rev  1  (rev1) and EdgeTech XStar (xstar) formats is likely to generate
       SQL errors about missing table columns.

DIAGNOSTICS

       If you pass in a SEGY file that is malformed, specify a bad driver,  or
       pass  a  group of files that are not all the same SEGY format, the pro-
       gram will throw an exception and leave you with a python  stack  trace.
       You may have to look at the code to figure out what it is wrong.

ENVIRONMENT

       PYTHONPATH  Add additional drivers in you python path to make them
                   available

SEE ALSO

       segydump(1), segy-py, grep(1)

       The homepage for the segy-py package can be found here on the web:

         http://schwehr.org/software/segy-py/

       For information on sqlite:

         sqlite -help
           or
         http://www.sqlite.org/

       For information on pysqlite:  http://www.sqlite.org/



Schwehr                          October 2005                    SEGYSQL.PY(1)