R Development Page

Contributed R Packages

Below is a list of all packages provided by project R interface to GDAL, OGR and PROJ.4.

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).



Bindings for the Geospatial Data Abstraction Library

  Provides bindings to the Geospatial Data Abstraction Library (GDAL) (>= 1.11.4) and access to projection/transformation operations from the PROJ library. Please note that rgdal will be retired by the end of 2023, plan transition to sf/stars/terra functions using GDAL and PROJ at your earliest convenience. Use is made of classes defined in the sp package. Raster and vector map data can be imported into R, and raster and vector sp objects exported. The GDAL and PROJ libraries are external to the package, and, when installing the package from source, must be correctly installed first; it is important that GDAL < 3 be matched with PROJ < 6. From rgdal 1.5-8, installed with to GDAL >=3, PROJ >=6 and sp >= 1.4, coordinate reference systems use WKT2_2019 strings, not PROJ strings. Windows and macOS binaries (including GDAL, PROJ and their dependencies) are provided on CRAN.
  Version: 1.5-32 | Last change: 2022-05-09 18:42:30+02 | Rev.: 1176
  Download: linux(.tar.gz) | windows(.zip) | Build status: Current | Stable Release: Get rgdal 1.5-32 from CRAN
  R install command: install.packages("rgdal", repos="")
Package build: Source package (Linux x86_64) Windows binary (x86_64/i386)
Package check: Linux x86_64 (patched) | Linux x86_64 (devel) Windows (patched) | Windows (devel)


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.

Thanks to:
Vienna University of Economics and Business Powered By FusionForge