5 Table I/O

Most of the tools in this package either read one or more tables as input, or write one or more tables as output, or both. This section explains what kind of tables the tools can read and write, and how you tell them where to find the tables to operate on.

In most cases input and output table specifications are given by parameters with the following names (or similar ones):

in

Location of the input table; usually a filename or URL, but maybe some other source of data (see Section 5.2) or a scheme specification (see Section 5.3)

ifmt

Format of the input table, as listed in Section 5.1.1, or blank for automatic format detection based on input content or name (but ignored for scheme specifications)

out

Destination of the output table; usually a filename or "-"/blank for standard output

ofmt

Format of the output table as listed in Section 5.1.2, or blank for automatic format detection based on output filename

• 5.1 Table Formats
• 5.1.1 Input Formats
• 5.1.1.1 fits
• 5.1.1.2 colfits
• 5.1.1.3 votable
• 5.1.1.4 cdf
• 5.1.1.5 csv
• 5.1.1.6 ecsv
• 5.1.1.7 ascii
• 5.1.1.8 ipac
• 5.1.1.9 pds4
• 5.1.1.10 mrt
• 5.1.1.11 parquet
• 5.1.1.12 hapi
• 5.1.1.13 feather
• 5.1.1.14 gbin
• 5.1.1.15 tst
• 5.1.1.16 wdc
• 5.1.2 Output Formats
• 5.1.2.1 fits
• 5.1.2.2 colfits
• 5.1.2.3 votable
• 5.1.2.4 csv
• 5.1.2.5 ecsv
• 5.1.2.6 ascii
• 5.1.2.7 ipac
• 5.1.2.8 parquet
• 5.1.2.9 feather
• 5.1.2.10 text
• 5.1.2.11 html
• 5.1.2.12 latex
• 5.1.2.13 tst
• 5.1.2.14 mirage
• 5.2 Input Locations
• 5.3 Input Schemes
• 5.3.1 skysim
• 5.3.2 attractor
• 5.3.3 jdbc
• 5.3.4 loop
• 5.3.5 test
• 5.3.6 class
• 5.3.7 hapi
• 5.4 Authentication