diff options
| author | Even Rouault <even.rouault@spatialys.com> | 2020-03-09 23:17:11 +0100 |
|---|---|---|
| committer | Even Rouault <even.rouault@spatialys.com> | 2020-03-09 23:17:11 +0100 |
| commit | 746c8aa17a4d0e2cda1933b4c0bd79d494089f46 (patch) | |
| tree | 376011539440adbcae92f3b6b0263832cfc2f8d0 /test/unit/test_io.cpp | |
| parent | 13782b19974ed8c99a8176692e688512c96e8481 (diff) | |
| download | PROJ-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 'test/unit/test_io.cpp')
| -rw-r--r-- | test/unit/test_io.cpp | 15 |
1 files changed, 15 insertions, 0 deletions
diff --git a/test/unit/test_io.cpp b/test/unit/test_io.cpp index 767c39e9..8a2d1ad7 100644 --- a/test/unit/test_io.cpp +++ b/test/unit/test_io.cpp @@ -4344,6 +4344,21 @@ static const struct { {"False northing", 2}, }}, + {"Transverse_Mercator_Complex", + {{"False_Easting", 1}, + {"False_Northing", 2}, + {"Central_Meridian", 3}, + {"Scale_Factor", 4}, + {"Latitude_Of_Origin", 5}}, + "Transverse Mercator", + { + {"Latitude of natural origin", 5}, + {"Longitude of natural origin", 3}, + {"Scale factor at natural origin", 4}, + {"False easting", 1}, + {"False northing", 2}, + }}, + {"Albers", {{"False_Easting", 1}, {"False_Northing", 2}, |