Closed caprieldeluca closed 4 years ago
This is a wont-fix, as it's working as designed. It's not possible to reliably match proj strings to user CRSes defined by proj strings without a LOT of unexpected/dangerous side effects.
Proj strings are a lossy format, discouraged for use in modern workflows. Just don't use them, and use WKT instead.
Describe the bug
When a custom CRS is added from a proj4 string, the WKT definition is not saved in the tbl_srs table of the qgis.db database. When exporting a layer to the new system an loading it, it is recognized with Unkown CRS system.
How to Reproduce
+proj=tmerc +lat_0=-34.6297166 +lon_0=-58.4627 +k=0.999998 +x_0=100000 +y_0=100000 +ellps=intl +towgs84=-148,136,90,0,0,0,0 +units=m +no_defs
QGIS and OS versions
QGIS 3.10.5 at Windows 10 (64-bit) machine, OSGeo4W install.
Additional context
In the tbl_srs of qgis.db database, the WKT definition is stored only when the format of the definition in the custom CRS is changed to WKT.
Screenshots