Wrong output CRS when input layer uses generated CRS #25152
Labels
Bug
Either a bug report, or a bug fix. Let's hope for the latter!
Processing
Relating to QGIS Processing framework or individual Processing algorithms
Author Name: Anita Graser (@anitagraser)
Original Redmine Issue: 17254
Affected QGIS version: master
Redmine category:processing/core
Assignee: Victor Olaya
Tested with qgis:fixeddistancebuffer, native:dissolve, and native:buffer using OSGeo4W 2.99
If the input layer uses a generated / custom CRS, the output layer is loaded in a wrong CRS. In my case, the layers were wrongly assigned WGS84. Note that, in settings, I've configured that QGIS should "prompt for CRS" if a layer without CRS info is loaded.
The text was updated successfully, but these errors were encountered: