PROJ/test/cli, branch gdalbarn

proj_create_crs_to_crs(): defer selection of actual coordinate operation until proj_trans() is called (fixes #1229)

2019-01-21T23:10:23+00:00

Add support for spaces in grid name parameters (fixes #1152)

2019-01-19T17:04:49+00:00

test/cli/Makefile.am: fix to make testdatumfile run again

2019-01-19T16:48:43+00:00

import/export PROJ strings from ISO19111 code: require/output +type=crs for CRS objects (refs #1214)

2019-01-17T09:40:12+00:00

projinfo: output WKT2_2018 by default (fixes #1187)

2019-01-15T14:39:25+00:00

projinfo: use PROJ.4 label for CRS, and PROJ otherwise. Add test case for CRS with towgs84 keyword

2019-01-08T20:25:08+00:00

ISO19111: remove PROJ.5 specific format for CRS (refs #1214)

2019-01-08T20:25:07+00:00

As discussed in https://github.com/OSGeo/proj.4/issues/1214#issuecomment-452084720,
the introduction of a new PROJ.5 format to export CRS using pipeline/unitconvert/axisswap
as an attempt of improving the PROJ.4 format used by GDAL and other products is
likely a dead-end since it is still lossy in many aspects and can cause confusion
with coodinate operations.

Consequently the PROJ_5 convention will be identical to PROJ_4 for CRS export.

Note: on the import side, I've kept the code that could parse unitconvert and
axisswap when building a CRS definition from a pipeline. It is there as a hidden
feature as it was kind of a tear to remove that code in case it might still be
useful...

test/cli/Makefile.am: parallelize CLI tests

2018-12-30T20:48:56+00:00

tests: remove useless mentions of no_defs (refs #201)

2018-12-27T10:03:23+00:00

Remove proj_def.dat (fixes #201)

2018-12-27T10:03:14+00:00