The following page describes the basic IPAC Table Format, which can
be used with IRSA Services that support multi-object searches.
http://irsa.ipac.caltech.edu/applications/DDGEN/Doc/ipac_tbl.html
Please pay particular attention to the "DBMS Cons...

You cannot input a list of object names directly into the Catalog
Search Tool. However, you can feed your list (with no header) into the
IPAC Table Reformat and Validation Service:
http://irsa.ipac.caltech.edu/applications/TblCheck/ [1]
If you cl...

This usually means that the table you uploaded is in a binary file
format, such as .doc, .rtf or .xls.
In order for a table to be read by IRSA's services, it must be in a
plain text ASCII file. If you are using Microsoft Word, be aware
documents may ap...

This error indicates that the table you uploaded contains too many
data columns and too few column names.
If you are using IPAC ASCII Column-Aligned, or tab- or
comma-delimited formats, the number of cells containing data must not
exceed the number of ...

This error message means that the column names in your table do not
sufficiently describe an object name, or the locations on the sky
using ra, dec, glon, glat, etc.
Clean up the column names so they are recognizable by IRSA services.
See Supported ...

Three common conditions may result in this error message.
REASON #1: When using IPAC Table Format, data are located beneath the
vertical bars in the header.
SOLUTION: Align the data with the columns in the header. (See IPAC
Table Format [1])
R...

REASON: The table is using IPAC ASCII Column-Aligned format, and the
columns are misaligned.
SOLUTION: Make sure the table data are contained within the
boundaries set by the vertical lines in the column header rows.

In IPAC Table Format, column names can be the combination of
characters, numbers, or underscores ("_"). Blanks, white spaces, tabs,
dashes ("-"), or any other special characters are not allowed as part
of column names. In this case, the parentheses mus...

Here are some tips for making your large catalog search return
faster:
1. If you suspect that your query might return results larger than 2
Gb, you will need to break it up into smaller queries. It can be
difficult to predict the size of the returne...