PROJ/test/unit, branch 6.2

normalizeForVisualization() and other methods applying on a ProjectedCRS: do not mess the derivingConversion object of the original object (fixes #1736)

2019-11-25T12:14:35+00:00

normalizeForVisualization(), promoteTo3D(), demoteTo2D(), alterGeodeticCRS(),
alterCSLinearUnit() and alterParametersLinearUnit() all used the object
returned by derivingConversionRef() to create a new ProjectedCRS. While doing
so, this caused the derivingConversion of the original object to have its
targetCRS set to the object returned by normalizeForVisualization() and similar.
If that object died, then the weak pointer would be reset, and the original
ProjectedCRS() has now its derivingConversionRef()->targetCRS() nullptr

So bottom line is use derivingConversion() for anything that is not pure
reading !!!

This is confirmed to be the fix for the QGIS scenario in
https://github.com/qgis/QGIS/issues/30569#issuecomment-540060919

In QGIS use case, the issue arised when using a projected CRS with a non-GIS
friendly axis (that is where normalizeForVisualization() created a new projectedCRS)

createOperations(): in some circumstances we wrongly promoted a Helmert geog2D transformation to a geog3D

2019-11-03T14:33:55+00:00

Fixes for example EPSG:4979 to EPSG:2189, as raised in
https://github.com/OSGeo/gdal/issues/1972#issuecomment-548814354

createFromWkt(): be tolerant to missing scale_factor parameter (fixes #1700)

2019-10-30T16:49:39+00:00

This is invalid WKT, but GDAL 2.4 used to accept it and make a reasonable
use of it...

Currently we default it to 0 which is non sensical. Better use 1 as GDAL 2.4
did, and emit a warning.

Other fix: proj_create_from_wkt() was documented to operate by default in
non-strict validation mode, but it was actually in strict mode. So do as
documented.

importFromWkt(): fix axis orientation for non-standard ESRI WKT (fixes #1690)

2019-10-25T09:04:16+00:00

createOperations(): fix double vertical unit conversion from CompoundCRS to other CRS when the horizontal part of the projected CRS uses non-metre unit

2019-10-18T19:55:22+00:00

Fix issue reported on https://lists.osgeo.org/pipermail/proj/2019-October/008939.html

Merge pull request #1636 from OSGeo/backport-1633-to-6.2

2019-09-28T08:19:50+00:00

Backport #1633 to 6.2

Database: update to EPSG 9.8.2

2019-09-27T23:47:40+00:00

With limitation of https://github.com/OSGeo/PROJ/issues/1632 regarding
concatenated operations with more than 3 steps.

proj_create_crs_to_crs(): fix when there are only transformations with ballpark steps

2019-09-26T11:28:54+00:00

Currently we would discard all operations, resulting in a PJ object with
zero candidates. Better use those operations if nothing better is available.

Was seen on transforming from ETRS89 / UTM zone 31N + EGM96 height to WGS 84 (G1762).
The horizontal transformation from ETRS89 to WGS 84 (G1762) is a ballpark one.

[6.2 backport] cs2cs: autopromote CRS to 3D when there's a mix… (#1615)

2019-09-16T07:23:00+00:00

[6.2 backport] cs2cs: autopromote CRS to 3D when there's a mix of 2D and 3D (fixes #1563)

API: add CRS::promoteTo3D(), proj_crs_promote_to_3D() and proj_crs_create_projected_3D_crs_from_2D() (fixes #1587)

2019-09-15T16:39:07+00:00

(projinfo changes adding --3d from master removed)