The location of tables for input and output are usually given using
the in
and out
parameters respectively.
These are often, but not always, filenames. The possibilities are these:
http:
ftp:
file:
jar:
myspace:
myspace:/survey/iras_psc.xml
",
and can access files in the myspace are that the user is currently
logged into.
These URLs can be used for both input and output of tables.
To use them you must have an AstroGrid account and the AstroGrid
WorkBench or similar must be running; if you're not currently
logged in a dialogue will pop up to ask you for name and
password.ivo:
ivo://uk.ac.le.star/filemanager#node-2583
".
These URLs can be used for both input and output of tables.
To use them you must have an AstroGrid account and the AstroGrid
WorkBench or similar must be running; if you're not currently
logged in a dialogue will pop up to ask you for name and
password.jdbc:
-
")
<
syscmd" or
"syscmd|
)
<
" character
or ends with a "|
" character,
the rest of the string is taken as a command line to be executed
by the system shell.
For instance a location like
"<cat header.txt data.txt
"
(or equivalently
"cat header.txt data.txt|
")
could be used to prepend a header line to an ASCII data file
before it is passed to the STILTS ASCII-format input handler.
Note this syntax will probably only work on Unix-like systems.
In any of these cases, for input locations compression is taken care
of automatically. That means that you can give the filename or URL
of a file which is compressed using gzip
, bzip2
or Unix compress
and the program will uncompress it on the fly.