% Generated by roxygen2: do not edit by hand
% Please edit documentation in R/raster.R
\name{vec_read_pixel_series}
\alias{vec_read_pixel_series}
\title{Read the full time series at a single pixel from a .vec time cube}
\usage{
vec_read_pixel_series(
  r,
  x = NULL,
  y = NULL,
  col = NULL,
  row = NULL,
  band = 1L,
  level = 0L
)
}
\arguments{
\item{r}{A \code{vectra_raster} from \code{vec_open_raster()}.}

\item{x, y}{Pixel coordinates. Either both \code{x} and \code{y} (CRS units; the
geotransform is used to map to col/row) or both \code{col} and \code{row}
(1-based pixel indices).}

\item{col, row}{1-based pixel coordinates (alternative to x/y).}

\item{band}{Band index (1-based).}

\item{level}{Overview level. Default 0.}
}
\value{
A numeric vector of length \code{n_time}. NA marks pixels outside
the raster or matching nodata. The corresponding time stamps can
be obtained from \code{vec_raster_times(r, band, level)}.
}
\description{
Returns a numeric vector of length \code{n_time} — one value per time step
recorded in the file, in ascending time-stamp order.
}
\details{
For pixel-major files (written with
\code{vec_write_time_cube(layout = "pixel")}) this is the optimal access
pattern: a single tile decode yields all time values for the pixel.
For image-major files the reader scans the index for distinct time
stamps, decodes one spatial tile per stamp, and extracts the pixel
from each — correct but \code{n_time} slower than the optimal layout.
}
