diff options
| author | Even Rouault <even.rouault@spatialys.com> | 2021-06-17 17:53:11 +0200 |
|---|---|---|
| committer | Even Rouault <even.rouault@spatialys.com> | 2021-06-17 17:53:11 +0200 |
| commit | 5f6fac3afdb03aef5a26ce5f60c10ed612fa6fc2 (patch) | |
| tree | f26e1e183d1cd73e84eef01571d9596f76d1b5a3 /src/sqlite3_utils.cpp | |
| parent | 987c8e9a4521c3e80fac73dbaa76ff77747d854b (diff) | |
| download | PROJ-5f6fac3afdb03aef5a26ce5f60c10ed612fa6fc2.tar.gz PROJ-5f6fac3afdb03aef5a26ce5f60c10ed612fa6fc2.zip | |
proj_trans/cs2cs: If two operations have the same accuracy, use the one that is contained within a larger one
Relates to https://github.com/OSGeo/gdal/issues/3998
Before that change, cs2cs on a NAD83(HARN) to WGS84 transformation would
use the "NAD83(HARN) to WGS 84 (1)" transformation (a null Helmert
shift) that is valid for whole US, including non-CONUS areas, even when
used on points located on CONUS that has a "NAD83(HARN) to WGS 84 (3)"
transformation (non-null Helmert shift) with same accuracy (1m).
But if doing EPSG:2874 "NAD83(HARN) / California zone 5 (ftUS)" to
WGS84, we would use this later "NAD83(HARN) to WGS 84 (3)"
transformation because the area of use of EPSG:2874 restricts to CONUS.
This isn't consistant.
With that change, we now have more consistent behavior, even if it can
be argued which of the 2 transformations is the best...
$ echo 34 -120 | src/cs2cs -d 8 EPSG:4326 "NAD83(HARN)" | src/cs2cs "NAD83(HARN)" EPSG:2874
5955507.74 1828410.98 0.00
$ echo 34 -120 | src/cs2cs EPSG:4326 EPSG:2874
5955507.74 1828410.98 0.00
Diffstat (limited to 'src/sqlite3_utils.cpp')
0 files changed, 0 insertions, 0 deletions