As has been explained in https://CRAN.R-project.org/package=rgdal/vignettes/CRS_projections_transformations.html, coordinate reference systems are represented differently when PROJ < 6 and PROJ >= 6.
To alert interactive users to the possibility that their workflows
might be degraded unless they take the representational changes into
account, the sp
issues warnings if a
"CRS" object does not have an
WKT2 2019 representation (stored in a
comment attached to the
"CRS" object). This is
proj4string() only returns the PROJ 4
representation, not the accompanying
representation if any, so may constitute a loss of information. See also
for further discussion.
In general, it is good practice to replace all use in packages of
slot(, "proj4string") and
its assignment form by the assignment form of
sp::proj4string() is not called, many of the warnings are
On attaching rgdal:
## Loading required package: sp
## Please note that rgdal will be retired during 2023, ## plan transition to sf/stars/terra functions using GDAL and PROJ ## at your earliest convenience. ## See https://r-spatial.org/r/2022/04/12/evolution.html and https://github.com/r-spatial/evolution ## rgdal: version: 1.6-3, (SVN revision 1187) ## Geospatial Data Abstraction Library extensions to R successfully loaded ## Loaded GDAL runtime: GDAL 3.6.2, released 2023/01/02 ## Path to GDAL shared files: /usr/share/gdal ## GDAL does not use iconv for recoding strings. ## GDAL binary built with GEOS: TRUE ## Loaded PROJ runtime: Rel. 9.1.1, December 1st, 2022, [PJ_VERSION: 911] ## Path to PROJ shared files: /home/edzer/.local/share/proj:/usr/share/proj ## PROJ CDN enabled: FALSE ## Linking to sp version:1.5-1 ## To mute warnings of possible GDAL/OSR exportToProj4() degradation, ## use options("rgdal_show_exportToProj4_warnings"="none") before loading sp or rgdal.
a package startup message is displayed if PROJ >= 6 and GDAL >= 3, including the important information that:
To mute warnings of possible GDAL/OSR exportToProj4() degradation, use options(“rgdal_show_exportToProj4_warnings”=“none”) before loading rgdal.
In sp 1.4 and rgdal 1.5, the
default option value is
"all", in sp >=
1.5 and rgdal >= 1.6, the default will be flipped to
Both CRAN checks and use of checks by end users may trigger spurious
errors, if the versions of PROJ and GDAL differ from those on the
development platform. Since the
WKT2 2019 representation is
only generated on systems with PROJ >= 6 (and GDAL >= 3), warnings
should not be expected when the same code is run on platforms with older
versions of PROJ and GDAL. There are many such platforms, including RHEL
and CentOS systems, as well as Ubuntu 18 and others. Think of a large
lab with a cluster runnning such a system version, and that those
installing software may wish to run
R CMD check or just
your test suite to confirm that things are as they should be. They will
be dismayed to find that tests fail, but will not be able to find out
whether this matters for them.
Consequently, it is best either not to check warnings that perform differently when run under different versions of upstream external software (PROJ and GDAL), or to condition on the software versions with different expectations depending on the version.
To mute warnings in all settings, add the option above early in any relevant test file.
Fine-grained control may be obtained using
## GDAL GDAL_with_GEOS PROJ sp EPSG ## "3.6.2" "TRUE" "9.1.1" "1.5-1" "v10.076"
and its shorter version, testing only PROJ >= 6 (and GDAL >= 3):
##  TRUE
Using this test, a warning might be expected if recent PROJ and GDAL are used, and before the warning default is flipped in sp > 1.4 and rgdal > 1.5.
In sf, use
determine versions if necessary.