aboutsummaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorEven Rouault <even.rouault@spatialys.com>2019-09-23 13:26:02 +0200
committerEven Rouault <even.rouault@spatialys.com>2019-09-23 13:26:02 +0200
commitda802e250b2487d41013829437740628b2ede667 (patch)
tree4b3bcb89b8b94d9718f4cbf73db70f548ce798c0 /docs
parent91d3d51a5abafb773fca3e4aae3223cdedfc51af (diff)
downloadPROJ-da802e250b2487d41013829437740628b2ede667.tar.gz
PROJ-da802e250b2487d41013829437740628b2ede667.zip
Document the autopromotion to 3D when mix of 2D/3D CRS in createOperations(), and test it (fixes #1623)
Diffstat (limited to 'docs')
-rw-r--r--docs/source/apps/projinfo.rst9
1 files changed, 6 insertions, 3 deletions
diff --git a/docs/source/apps/projinfo.rst b/docs/source/apps/projinfo.rst
index 8fbf0546..f6bf9ab0 100644
--- a/docs/source/apps/projinfo.rst
+++ b/docs/source/apps/projinfo.rst
@@ -224,9 +224,12 @@ The following control parameters can appear in any order:
.. versionadded:: 7.0
- "Promote" the CRS(s) to their 3D version. Useful for example when wanting
- to transform between a 2D projected CRS with elevations as ellipsoidal
- height to a 3D geographic CRS or a compoundCRS.
+ "Promote" the CRS(s) to their 3D version. In the context of researching
+ available coordinate transformations, explicitly specifying this option is
+ not necessary, because when one of the source or target CRS has a vertical
+ component but not the other one, the one that has no vertical component is
+ automatically promoted to a 3D version, where its vertical axis is the
+ ellipsoidal height in metres, using the ellipsoid of the base geodetic CRS.
.. option:: --c-ify