\HeaderA{read.table}{Data Input}{read.table}
\aliasA{read.csv}{read.table}{read.csv}
\aliasA{read.csv2}{read.table}{read.csv2}
\aliasA{read.delim}{read.table}{read.delim}
\aliasA{read.delim2}{read.table}{read.delim2}
\keyword{file}{read.table}
\keyword{connection}{read.table}
\begin{Description}\relax
Reads a file in table format and creates a data frame from it, with
cases corresponding to lines and variables to fields in the file.
\end{Description}
\begin{Usage}
\begin{verbatim}
read.table(file, header = FALSE, sep = "", quote = "\"'",
           dec = ".", row.names, col.names,
           as.is = !stringsAsFactors,
           na.strings = "NA", colClasses = NA, nrows = -1,
           skip = 0, check.names = TRUE, fill = !blank.lines.skip,
           strip.white = FALSE, blank.lines.skip = TRUE,
           comment.char = "#",
           allowEscapes = FALSE, flush = FALSE,
           stringsAsFactors = default.stringsAsFactors(),
           encoding = "unknown")

read.csv(file, header = TRUE, sep = ",", quote="\"", dec=".",
         fill = TRUE, comment.char="", ...)

read.csv2(file, header = TRUE, sep = ";", quote="\"", dec=",",
          fill = TRUE, comment.char="", ...)

read.delim(file, header = TRUE, sep = "\t", quote="\"", dec=".",
           fill = TRUE, comment.char="", ...)

read.delim2(file, header = TRUE, sep = "\t", quote="\"", dec=",",
            fill = TRUE, comment.char="", ...)
\end{verbatim}
\end{Usage}
\begin{Arguments}
\begin{ldescription}
\item[\code{file}] the name of the file which the data are to be read from.
Each row of the table appears as one line of the file.  If it does
not contain an \emph{absolute} path, the file name is
\emph{relative} to the current working directory,
\code{\LinkA{getwd}{getwd}()}. Tilde-expansion is performed where supported.

Alternatively, \code{file} can be a readable
\code{\LinkA{connection}{connection}} (which will be opened for reading if
necessary, and if so \code{\LinkA{close}{close}}d (and hence destroyed) at
the end of the function call).  (If \code{\LinkA{stdin}{stdin}()} is used,
the prompts for lines may be somewhat confusing.  Terminate input
with a blank line or an EOF signal, \code{Ctrl-D} on Unix and
\code{Ctrl-Z} on Windows.  Any pushback on \code{stdin()} will be
cleared before return.)

\code{file} can also be a complete URL.

To read a data file not in the current encoding (for example a
Latin-1 file in a UTF-8 locale or conversely) use a
\code{\LinkA{file}{file}} connection setting the \code{encoding} argument.

\item[\code{header}] a logical value indicating whether the file contains the
names of the variables as its first line.  If missing, the value is
determined from the file format: \code{header} is set to \code{TRUE}
if and only if the first row contains one fewer field than the
number of columns.
\item[\code{sep}] the field separator character.  Values on each line of the
file are separated by this character.  If \code{sep = ""} (the
default for \code{read.table}) the separator is \sQuote{white space},
that is one or more spaces, tabs, newlines or carriage returns.
\item[\code{quote}] the set of quoting characters. To disable quoting
altogether, use \code{quote = ""}.  See \code{\LinkA{scan}{scan}} for the
behaviour on quotes embedded in quotes.  Quoting is only considered
for columns read as character, which is all of them unless
\code{colClasses} is specified.
\item[\code{dec}] the character used in the file for decimal points.
\item[\code{row.names}] a vector of row names.  This can be a vector giving
the actual row names, or a single number giving the column of the
table which contains the row names, or character string giving the
name of the table column containing the row names.

If there is a header and the first row contains one fewer field than
the number of columns, the first column in the input is used for the
row names.  Otherwise if \code{row.names} is missing, the rows are
numbered.

Using \code{row.names = NULL} forces row numbering. Missing or
\code{NULL} \code{row.names} generate row names that are considered
to be \sQuote{automatic} (and not preserved by \code{\LinkA{as.matrix}{as.matrix}}).

\item[\code{col.names}] a vector of optional names for the variables.
The default is to use \code{"V"} followed by the column number.
\item[\code{as.is}] the default behavior of \code{read.table} is to convert
character variables (which are not converted to logical, numeric or
complex) to factors.  The variable \code{as.is} controls the
conversion of columns not otherwise specified by \code{colClasses}.
Its value is either a vector of logicals (values are recycled if
necessary), or a vector of numeric or character indices which
specify which columns should not be converted to factors.

Note: to suppress all conversions including those of numeric
columns, set \code{colClasses = "character"}.

Note that \code{as.is} is specified per column (not per
variable) and so includes the column of row names (if any) and any
columns to be skipped.

\item[\code{na.strings}] a character vector of strings which are to be
interpreted as \code{\LinkA{NA}{NA}} values.  Blank fields are also
considered to be missing values in logical, integer, numeric and
complex fields.
\item[\code{colClasses}] character.  A vector of classes to be assumed for
the columns.  Recycled as necessary, or if the character vector is
named, unspecified values are taken to be \code{NA}.

Possible values are \code{NA} (when \code{\LinkA{type.convert}{type.convert}} is
used), \code{"NULL"} (when the column is skipped), one of the atomic
vector classes (logical, integer, numeric, complex, character, raw),
or \code{"factor"}, \code{"Date"} or \code{"POSIXct"}.  Otherwise
there needs to be an \code{as} method (from package \pkg{methods})
for conversion from \code{"character"} to the specified formal
class.

Note that \code{colClasses} is specified per column (not per
variable) and so includes the column of row names (if any).

\item[\code{nrows}] integer: the maximum number of rows to read in.  Negative
and other invalid values are ignored.
\item[\code{skip}] integer: the number of lines of the data file to skip before
beginning to read data.
\item[\code{check.names}] logical.  If \code{TRUE} then the names of the
variables in the data frame are checked to ensure that they are
syntactically valid variable names.  If necessary they are adjusted
(by \code{\LinkA{make.names}{make.names}}) so that they are, and also to ensure
that there are no duplicates.
\item[\code{fill}] logical. If \code{TRUE} then in case the rows have unequal
length, blank fields are implicitly added.  See \sQuote{Details}.
\item[\code{strip.white}] logical. Used only when \code{sep} has
been specified, and allows the stripping of leading and trailing
white space from \code{character} fields (\code{numeric} fields
are always stripped).  See \code{\LinkA{scan}{scan}} for further details,
remembering that the columns may include the row names.
\item[\code{blank.lines.skip}] logical: if \code{TRUE} blank lines in the
input are ignored.
\item[\code{comment.char}] character: a character vector of length one
containing a single character or an empty string.  Use \code{""} to
turn off the interpretation of comments altogether.
\item[\code{allowEscapes}] logical.  Should C-style escapes such as
\code{\bsl{}n} be processed or read verbatim (the default)?   Note that if
not within quotes these could be interpreted as a delimiter (but not
as a comment character).  For more details see \code{\LinkA{scan}{scan}}.
\item[\code{flush}] logical: if \code{TRUE}, \code{scan} will flush to the
end of the line after reading the last of the fields requested.
This allows putting comments after the last field.
\item[\code{stringsAsFactors}] logical: should character vectors be converted
to factors?
\item[\code{encoding}] encoding to be assumed for input strings.  It is
used to mark character strings as known to be in
Latin-1 or UTF-8: it is not used to re-encode the input.  For an
example of how to do so, see the examples under \code{\LinkA{file}{file}}.

\item[\code{...}] Further arguments to be passed to \code{read.table}.
\end{ldescription}
\end{Arguments}
\begin{Details}\relax
This function is the principal means of reading tabular data into \R.

A field or line is \sQuote{blank} if it contains nothing (except
whitespace if no separator is specified) before a comment character or
the end of the field or line.

If \code{row.names} is not specified and the header line has one less
entry than the number of columns, the first column is taken to be the
row names.  This allows data frames to be read in from the format in
which they are printed.  If \code{row.names} is specified and does
not refer to the first column, that column is discarded from such files.

The number of data columns is determined by looking at the first five lines
of input (or the whole file if it has less than five lines), or from
the length of \code{col.names} if it is specified and
is longer.  This could conceivably be wrong if \code{fill} or
\code{blank.lines.skip} are true, so specify \code{col.names} if necessary.

\code{read.csv} and \code{read.csv2} are identical to
\code{read.table} except for the defaults.  They are intended for
reading \sQuote{comma separated value} files (\file{.csv}) or
(\code{read.csv2}) the variant
used in countries that use a comma as decimal point and a semicolon
as field separator.  Similarly, \code{read.delim} and
\code{read.delim2} are for reading delimited files, defaulting to the
TAB character for the delimiter.  Notice that \code{header = TRUE} and
\code{fill = TRUE} in these variants, and that the comment character
is disabled.

The rest of the line after a comment character is skipped; quotes
are not processed in comments.  Complete comment lines are allowed
provided \code{blank.lines.skip = TRUE}; however, comment lines prior
to the header must have the comment character in the first non-blank
column.

Quoted fields with embedded newlines are supported except after a
comment character.

Note that unless \code{colClasses} is specified, all columns are read
as character columns and then converted.  This means that quotes are
interpreted in all fields and that a column of values like \code{"42"}
will result in an integer column.
\end{Details}
\begin{Value}
A data frame (\code{\LinkA{data.frame}{data.frame}}) containing a representation of
the data in the file.

Empty input is an error unless \code{col.names} is specified, when a
0-row data frame is returned: similarly giving just a header line if
\code{header = TRUE} results in a 0-row data frame.  Note that
in either case tthe columns will logical unless \code{colClasses} was
supplied.

Character strings in the result (including factor levels) will have a
declared encoding if \code{encoding} is \code{"latin1"} or
\code{"UTF-8"}.
\end{Value}
\begin{Note}\relax
The columns referred to in \code{as.is} and \code{colClasses} include
the column of row names (if any).

Less memory will be used if \code{colClasses} is specified as one of
the six \LinkA{atomic}{atomic} vector classes.  This can be particularly so when
reading a column that takes many distinct numeric values, as storing
each distinct value as a character string can take up to 14 times as
much memory as storing it as an integer.

Using \code{nrows}, even as a mild over-estimate, will help memory
usage.

Using \code{comment.char = ""} will be appreciably faster than the
\code{read.table} default.

\code{read.table} is not the right tool for reading large matrices,
especially those with many columns: it is designed to read
\emph{data frames} which may have columns of very different classes.
Use \code{\LinkA{scan}{scan}} instead.
\end{Note}
\begin{References}\relax
Chambers, J. M. (1992)
\emph{Data for models.}
Chapter 3 of \emph{Statistical Models in S}
eds J. M. Chambers and T. J. Hastie, Wadsworth \& Brooks/Cole.
\end{References}
\begin{SeeAlso}\relax
The \emph{R Data Import/Export} manual.

\code{\LinkA{scan}{scan}}, \code{\LinkA{type.convert}{type.convert}},
\code{\LinkA{read.fwf}{read.fwf}} for reading \emph{f}ixed \emph{w}idth
\emph{f}ormatted input;
\code{\LinkA{write.table}{write.table}};
\code{\LinkA{data.frame}{data.frame}}.

\code{\LinkA{count.fields}{count.fields}} can be useful to determine problems with
reading files which result in reports of incorrect record lengths.
\end{SeeAlso}

