Bug report #19396
Default CRS for new projects not working as expected
| Status: | Open | ||
|---|---|---|---|
| Priority: | Normal | ||
| Assignee: | - | ||
| Category: | Projection Support | ||
| Affected QGIS version: | 3.2 | Regression?: | No |
| Operating System: | Windows, Linux | Easy fix?: | No |
| Pull Request or Patch supplied: | No | Resolution: | |
| Crashes QGIS or corrupts data: | No | Copied to github as #: | 27224 |
Description
In version 2.18, setting the 'Default CRS for new projects' to an 'on the fly' option enabled maps to be set to that CRS, rather than the CRS of the data added to the map.
In version 3.2 (potentially earlier versions of 3.x), when the 'Default CRS for new projects' layer is set and a table added in another CRS (in our case from PostGIS), the map CRS changes to that of the layer, overriding the 'Default CRS for new projects' option.
History
#1
Updated by Igor Evdokimov over 6 years ago
Have the same BUG. #19311-4