PROJ/include, branch docker-build-updates

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

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"

Merge pull request #1426 from mwtoews/intel

2019-04-18T09:28:44+00:00

CMake: better support for Intel compiler

createOperations(): do not attempt using a unrelated datum intermediate when doing geog2D<-->geog3D conversions of same datum

2019-04-16T19:03:19+00:00

Seen when testing transformations between "CR 05" (EPSG:5365) and "CR-SIRGAS" (EPSG:8907)
which require going through their corresponding 3D GeogCRS to find a Helmert
transformation.

CMake: better support for Intel compiler

2019-04-16T09:59:52+00:00

Add proj_normalize_for_visualization()

2019-03-28T23:47:41+00:00

Fixes #1301

This function takes the output PJ from proj_create_crs_to_crs(),
and add (or undo) the needed axis swap operations so that the
object returned by proj_normalize_for_visualization() has the usual
GIS axis order.
In this implementation, this does something only if the coordinate
system of the source or target CRS, geographic or projected, has
NORTH, EAST ordering.
CompoundCRS wrapping those objects are also handled.

WKT2_2018: always export ID of SOURCECRS/TARGETCRS and STEPs

2019-03-25T12:56:43+00:00

even if there is one on upper node

This is a particular logic allowed by paragraph 7.3.3 Identifier
of OGC 18-010r6

WKT2_2018: always export ID in base crs node, even if there is one on upper node

2019-03-25T12:05:40+00:00

This is a particular logic allowed by paragraph 7.3.3 Identifier
of OGC 18-010r6

WKT2_2018: export ID in base crs node, when there is none on top of upper node

2019-03-25T11:44:35+00:00

This is the standard logic, that is now possible since ID is
allowed in BASEGEOGCRS and similar node

crs.cpp: remove non-intented (harmless here) pass by reference of a pointer

2019-03-25T11:44:34+00:00