PROJ/test/unit, branch docker-build-updates

identify(): take into account the authority passed in (fixes #1465)

2019-05-13T14:42:38+00:00

When identifying an object that has already a code with authority A
but the authority of interest passed was B, then it was not checking
that A != B, and did not try to search in the objects of B.

Fix identification of GeodeticCRS expressed by PROJ string for EPSG authority

2019-05-12T07:03:48+00:00

proj_normalize_for_visualization(): fix when there are coordinate operation alternatives

2019-05-08T10:00:08+00:00

createOperations(): for 'Amersfoort / RD New + NAP height' (EPSG:7415) to ETRS89 (EPSG:4937), make sure that the vgridshift is applied first (ie on Amersfoort datum) before the hgridshift

2019-05-06T18:21:27+00:00

createOperations(): fix case of ETRS89 3D to proj string with nadgrids and geoidgrids

2019-05-06T10:43:04+00:00

Fixes https://lists.osgeo.org/pipermail/proj/2019-May/008519.html

Reduce database size (#1438)

2019-05-01T16:40:04+00:00

Reduce database size

WKT importer: accepts PROJ-based COORDINATEOPERATION

2019-04-30T15:25:38+00:00

createOperations(): in SourceTargetCRSExtentUse::INTERSECTION mode, early return if the intersection of the areas is empty

2019-04-30T12:56:32+00:00

Propagate ballpark transformation flag to inverse coordinate operations

2019-04-30T12:31:56+00:00

proj_create(): add support for compoundCRS and concatenatedOperation named from their components

2019-04-22T18:05:36+00:00

Support following syntaxes:
- OGC URN combining references for compoundCRS:
  e.g. "urn:ogc:def:crs,crs:EPSG::2393,crs:EPSG::5717"
- its GDAL shortcut: e.g. "EPSG:2393+5717"
- OGC URN combining references for concatenated operations:
  e.g. "urn:ogc:def:coordinateOperation,coordinateOperation:EPSG::3895,coordinateOperation:EPSG::1618"