Bug report #20080
Saving Memory Layer to a file misses Scaling part of the CRS
| Status: | Open | ||
|---|---|---|---|
| Priority: | Normal | ||
| Assignee: | - | ||
| Category: | Projection Support | ||
| Affected QGIS version: | 3.2.3 | Regression?: | No |
| Operating System: | Easy fix?: | No | |
| Pull Request or Patch supplied: | No | Resolution: | |
| Crashes QGIS or corrupts data: | No | Copied to github as #: | 27902 |
Description
I created a custom CRS based on a state plane, and added a +k_0 parameter to make ground references in an image measure correctly.
I reprojected a layer of existing vectors into this new CRS in a temporary/memory layer. The features projected correctly onto the map.
However, when I used "Layer/Save As..." to save to a file, the saved layer "jumped" to a new location (tested with both geopackage and shapefiles, same behavior).
The CRS listed in the Source Tab for the layer properties is NOT my named custom projection, but a USER:100.... that does not include a +k_0 parameter.
When I select my custom projection to change the CRS, the feature jumps back to its proper location.
So apparently, when saving a layer to a file, not all of the PROJ4 parameters are being included in the CRS of the saved file. This may affect more parameters than just scaling, but I have not tested any others.
Keith
Related issues
History
#1
Updated by Saber Razmjooei about 6 years ago
- Related to Bug report #20079: CRS with Scaling in PROJ4 causes Vertex Tool to fail added
#2
Updated by Giovanni Manghi about 6 years ago
- Operating System deleted (
MacOS)