R Development Page
Contributed R Packages
Below is a list of all packages provided by project spatio-temporal data in R.
Important note for package binaries: R-Forge provides these binaries only for the most recent version of R, but not for older versions. In order to successfully install the packages provided on R-Forge, you have to switch to the most recent version of R or, alternatively, install from the package sources (.tar.gz).
classes and methods for spatio-temporal data
|Classes and methods for spatio-temporal data, including space-time regular lattices, sparse lattices, irregular data, and simple trajectories; utility functions for plotting data as map sequences (lattice or animation) or multiple time series; methods for spatial and temporal selection and subsetting, as well as for spatial/temporal/spatio-temporal combining or aggregating, retrieving coordinates, print, summary, etc.|
|Version: 1.0-10 | Last change: 2013-09-23 10:29:24+02 | Rev.: 111|
|Download: (.tar.gz) | (.zip) | Build status: Failed to build | Stable Release: Get spacetime 1.2-2 from CRAN|
R install command:
classes and methods for trajectory data
|Classes and methods for trajectory data|
|Version: 0.0-1 | Last change: 2013-09-23 09:52:05+02 | Rev.: 110|
|Download: (.tar.gz) | (.zip) | Build status: Current | Stable Release: Get trajectories 0.2-1 from CRAN|
R install command:
Build status codes
0 - Current: the package is available for download. The corresponding package passed checks on the Linux and Windows platform without ERRORs.
1 - Scheduled for build: the package has been recognized by the build system and provided in the staging area.
2 - Building: the package has been sent to the build machines. It will be built and checked using the latest patched version of R. Note that it is included in a batch of several packages. Thus, this process will take some time to finish.
3 - Failed to build: the package failed to build or did not pass the checks on the Linux and/or Windows platform. It is not made available since it does not meet the policies.
4 - Conflicts: two or more packages of the same name exist. None of them will be built. Maintainers are asked to negotiate further actions.
5 - Offline: the package is not available. The build system may be offline or the package maintainer did not trigger a rebuild (done e.g., via committing to the package repository).
If your package is not shown on this page or not building, then check the build system status report.