Version 1.5-25 (development, rev. 1122-1140) Unreleased

Version 1.5-23 (2021-02-03, rev. 1120-1121) 2021-02-03

  • Further fallout after removing valgrind issues.

Version 1.5-22 (2021-02-02, rev. 1106-1119) 2021-02-02

  • Attempt to remove further valgrind leak in proj6.cpp: PROJcopyEPSG() and in ogr_proj.cpp, both wrongly placed object destructors.

  • Modified roundtripping all declared projections in ?project examples because some listed projections for PROJ >= 5 provoke valgrind leakages by returning very large out-of-scope values for input coordinates (0, 0); inversion of these is not attempted; some listed projections are not projections.

Version 1.5-21 (2021-01-27, rev. 1093-1105) 2021-01-27

  • Suggest rgeos to write pre-SFS multipolygon objects to avoid unpleasant workaround.

  • Try to eliminate current valgrind leaks, starting from (

  • Try to increase robustness to installation with early PROJ 6 versions, which often lack functionality found necessary later (for example visualization order); the code had assumed that this function always was available and behaved as it now does. There are now graceful failures when not available.

Version 1.5-19 (2021-01-05, rev. 1083-1092) 2021-01-05

Version 1.5-18 (2020-10-13, rev. 1071-1082) 2020-10-13

  • condition tests/test_enforce_xy.R on PROJ >= 6 and GDAL >= 3 (email BDR, I forgot to re-check with PROJ-5.2.0/GDAL-2.2.4).

  • Adaptation to EPSG 10 database format started (from PROJ 7.2); choose DB columns by name not number in vignette.

Version 1.5-17 (2020-10-08, rev. 1051-1070) 2020-10-08

  • "CRS" instantiation now prefers PROJ: use rgdal::set_prefer_proj(FALSE) to return to earlier behaviour. It seems that access from C/C++ code to mechanisms in PROJ offers more depth than going through GDAL to PROJ. This "CRS" instantiation in sp and raster; Proj4 and WKT2 strings may differ depending on whether instantiation is straight from PROJ or goes via GDAL. Confirmed with multiple reverse dependency checks over almost 900 CRAN packages.

  • By default use PROJ function to extract the source CRS from a "BOUNDCRS". When +towgs84= is given, PROJ and GDAL see the apparent source Proj4 string as implicitly implying a coordinate operation transforming to target WGS84, leading to the WKT2 representation being a "BOUNDCRS", not a "PROJCRS" or "GEOGCRS", and thus causing misunderstandings later in searching for the most accurate coordinate operation for a transformation. May be controlled by setting the get_source_if_boundcrs= in sp::CRS() from sp 1.4-4 (2020-10-07). Confirmed with multiple reverse dependency checks over almost 900 CRAN packages.

  • Add support for instantiating from "OGC:CRS84" to provide a guaranteed GIS/visualization axis order WGS84 instantiator (preferred to "EPSG:4326").

  • Permit empty string in SRS_string= argument to sp::CRS() and functions called by it.

  • Use GDAL ORSIsProjected() instead of simply looking for "+proj=longlat" in the Proj4 string representation where possible.

Version 1.5-16 (2020-08-07, rev. 1047-1050) 2020-08-07

  • Typo in C code; use try() around Area-of-Interest calculation for coordinate operations (email BDR, I forgot to re-check with PROJ-5.2.0/GDAL-2.2.4).

Version 1.5-15 (2020-08-04, rev. 1020-1046) 2020-08-04

Version 1.5-12 (2020-06-26, rev. 1007-1019) 2020-06-26

  • Further corrections to for older PROJ/GDAL versions

Version 1.5-10 (2020-06-09, rev. 991-1006) 2020-06-09

  • Corrections to for older PROJ/GDAL versions

Version 1.5-8 (2020-05-28, rev. 846-990) 2020-05-28

Versions 1.4-7 and 1.4-8 2019-10-28

  • Fixed configure issue for R 4.0.0

  • Fixed length of class() errors for matrices becoming arrays in R 4.0.0

Version 1.4-6 (Final pre-WKT2 release) 2019-10-01