NAME
db2kml_py - pretty-print station and/or origin data as KML or KMZ
SYNOPSIS
db2kml_py [-vxt] [-p pf_file] dbname
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.
SUPPORT
Contributed: NO BRTT support -- please contact author.
DESCRIPTION
This text is grabbed pretty much verbatim from the db2kml manpage
with a few changes when needed.
db2kml_py prints a file of placemarks in kml
(Keyhole Markup Language) suitable for Google Earth and a growing
number of other programs. The placemarks can be for origin or site
information extracted from the specified database.
In GE, each event will display its magnitude and date when moused
over. Selecting the event will bring up a menu with more detailed
information. Each point is also tagged with a kml <TimeStamp> tag.
In recent versions of Google Earth (> v4.0) it is possible to "play"
the events in time using the time slider bar. The time slider bar
can also be used to adjust the start and end dates of the events
being displayed. There is no limit on the number of sites or events
that can be processed, however at present GE bogs down on more than
a few thousand aplacemarks.
The icons for the placemarks and the depth-magnitude scale must
reside in a web accessible location. A provisional location is
included in the parameter file though users are encouraged to modify
this for any heavy use. Please read the note about servers below.
OPTIONS
-
-v
verbose output
-
-x
debug aka very verbose output
-
-t
file type to output - not currently implemented
-
-p pf_file
use pf_file instead of the default pf file.
PARAMETER FILE
The parameter file contains many more variables than currently
available in db2kml. These various parameters allow the user
to customize the metadata and output for their institution.
The user can also define complex Datascope expressions for
getting just the view they want. You can also choose to output
a kmz file (compressed kml) rather than kml if desired, and define
a network link if the kml source will update automatically and
you want users of your file to have their content auto-update over
the network.
RETURN VALUES
db2kml_py exits with 0 upon success, nonzero upon error.
NOTES
Code updated to include the snetsta table for stations. This will
allow you to subset by network.
NOTE ABOUT SERVERS
The icons and the magnitude/depth legend must be sourced from a
web-accessible location. Especially if your KML files are served
to a wide audience, it is important to provide a robust archive for
these images that you have control over.
SEE ALSO
db2kml(1), db2xml(1), dbexpressions(5)
BUGS AND CAVEATS
You must have the Antelope Interface to Python compiled
against your installed version of Antelope and Python. See
pythondb for more information.
AUTHOR
Rob Newman
- based on the original db2kml written by -
Michael West
Geophysical Institute
Alaska Volcano Observatory
University of Alaska Fairbanks
- UPDATED BY -
Juan Reyes <reyes@ucsd.edu>
Antelope User Group Contributed Software