[gdal-dev] Problems with several dozen projections
Ray at Daylon
rayg at daylongraphics.com
Wed Jul 30 03:05:51 PDT 2025
I was running a test of all available projections in PROJ 9.6.2 using
GDAL 3.11.3 (both current as of this writing), on Windows.
I got errors trying to project from lat/lon and back with the 55
projections listed in the attached CSV file. If I leave off the
SetAxisMappingStrategy calls, many more projections fail.
No deprecated or celestial body projections were tested.
When a transformation failed to go from lat/lon to the projected CRS,
the reason was usually that the transformation wound up with an infinity.
My test program is essentially this:
LatLonCRS = OGRSpatialReference(EPSG:4326)
LatLonCRS.SetAxisMappingStrategy(OAMS_TRADITIONAL_GIS_ORDER)
Projections = proj_get_crs_info_list_from_database()
For each Projection
Wkt2 = proj_as_wkt(Projection, PJ_WKT2_2019)
ProjCRS = OGRSpatialReference(Wkt2)
ProjCRS.SetAxisMappingStrategy(OAMS_TRADITIONAL_GIS_ORDER)
Xfm1 = OGRCreateCoordTransform(LatLonCRS, ProjCRS)
Xfm2 = OGRCreateCoordTransform(ProjCRS, LatLonCRS)
ProjCRS.GetAreaOfUse(West, South, East, North)
// Get center of bbox
X = (West + East) / 2
Y = (North + South) / 2
Xfm1.Transform(X, Y) // Go from lat/lon to Proj CRS
Xfm2.Transform(X, Y) // and back to lat/lon
Next projection
There were various errors logged by PROJ:
Cannot find coordinate operations from `EPSG:2299' to `EPSG:4326'
Cannot find coordinate operations from `EPSG:2301' to `EPSG:4326'
Cannot find coordinate operations from `EPSG:2303' to `EPSG:4326'
Cannot find coordinate operations from `EPSG:2304' to `EPSG:4326'
Cannot find coordinate operations from `EPSG:2305' to `EPSG:4326'
Cannot find coordinate operations from `EPSG:2306' to `EPSG:4326'
Cannot find coordinate operations from `EPSG:2307' to `EPSG:4326'
Cannot find coordinate operations from `EPSG:2963' to `EPSG:4326'
Cannot find coordinate operations from `EPSG:3144' to `EPSG:4326'
Cannot find coordinate operations from `EPSG:5017' to `EPSG:4326'
Cannot find coordinate operations from `EPSG:5800' to `EPSG:4326'
Cannot find coordinate operations from `EPSG:5801' to `EPSG:4326'
Cannot find coordinate operations from `EPSG:5802' to `EPSG:4326'
Cannot find coordinate operations from `EPSG:5803' to `EPSG:4326'
Cannot find coordinate operations from `EPSG:5808' to `EPSG:4326'
Cannot find coordinate operations from `EPSG:5809' to `EPSG:4326'
Cannot find coordinate operations from `EPSG:5810' to `EPSG:4326'
Cannot find coordinate operations from `EPSG:5811' to `EPSG:4326'
Cannot find coordinate operations from `EPSG:5812' to `EPSG:4326'
Cannot find coordinate operations from `EPSG:5813' to `EPSG:4326'
Cannot find coordinate operations from `EPSG:5814' to `EPSG:4326'
Cannot find coordinate operations from `EPSG:5815' to `EPSG:4326'
Cannot find coordinate operations from `EPSG:5816' to `EPSG:4326'
Cannot find coordinate operations from `EPSG:5817' to `EPSG:4326'
Cannot find coordinate operations from `EPSG:6715' to `EPSG:4326'
Cannot find coordinate operations from `EPSG:10642' to `EPSG:4326'
Cannot find coordinate operations from `EPSG:10740' to `EPSG:4326'
No inverse operation
Point outside of projection domain
PROJ: proj_crs_get_geodetic_crs: CRS has no geodetic CRS
PROJ: omerc: Invalid value for lat_1: lat_1 should be different from 0
PROJ: pipeline: Pipeline: Bad step definition: inv (Invalid value for an
argument)
PROJ: pipeline: Pipeline: Bad step definition: proj=omerc (Invalid value
for an argument)
PROJ: pipeline: Pipeline: Inverse operation for wag7 is not available
Are any of these bugs in PROJ or GDAL?
If so, are there any workarounds?
I was also wondering, should it be necessary to take a projection's axis
mapping into account? Isn't that a detail that GDAL or PROJ can abstract
away? Is SetAxisMappingStrategy() really needed?
My thanks in advance for any help,
Ray Gardener
-------------- next part --------------
A non-text attachment was scrubbed...
Name: proj_962_errors.csv
Type: text/csv
Size: 4828 bytes
Desc: not available
URL: <http://lists.osgeo.org/pipermail/gdal-dev/attachments/20250730/f3d8562f/attachment.csv>
More information about the gdal-dev
mailing list