aboutsummaryrefslogtreecommitdiff
path: root/docs/source/development/reference/cpp
diff options
context:
space:
mode:
authorEven Rouault <even.rouault@spatialys.com>2020-03-09 23:17:11 +0100
committerEven Rouault <even.rouault@spatialys.com>2020-03-09 23:17:11 +0100
commit746c8aa17a4d0e2cda1933b4c0bd79d494089f46 (patch)
tree376011539440adbcae92f3b6b0263832cfc2f8d0 /docs/source/development/reference/cpp
parent13782b19974ed8c99a8176692e688512c96e8481 (diff)
downloadPROJ-746c8aa17a4d0e2cda1933b4c0bd79d494089f46.tar.gz
PROJ-746c8aa17a4d0e2cda1933b4c0bd79d494089f46.zip
Map ESRI Transverse_Mercator_Complex to Transverse Mercator
According to https://gis.stackexchange.com/questions/226679/complex-utm-projection it is highly likely that Transverse_Mercator_Complex corresponds to our extended/enhanced/Poder-Engsager transverse mercator method (etmerc), or something similarly precise. So we can map that to the standard Transverse Mercator method, since etmerc is used for it.
Diffstat (limited to 'docs/source/development/reference/cpp')
0 files changed, 0 insertions, 0 deletions