Bug report #6727
CRS functions are enabled for non-spatial tables
Status: | Closed | ||
---|---|---|---|
Priority: | Normal | ||
Assignee: | - | ||
Category: | Data Provider | ||
Affected QGIS version: | master | Regression?: | No |
Operating System: | Easy fix?: | No | |
Pull Request or Patch supplied: | No | Resolution: | end of life |
Crashes QGIS or corrupts data: | No | Copied to github as #: | 15891 |
Description
Add this layer: https://issues.qgis.org/attachments/5091/Book1.csv
Right-click on it in the layers list. "Set layer CRS" and "Set project CRS from layer" are available.
Click "layer>properties>general". QGIS will claim that the layer CRS is WGS 84 (or maybe your default CRS), and the "Specify CRS" and "Update Extents" button will be available. But this is a non-spatial table, so it shouldn't have a CRS!
Now, why I noticed this:
If the project CRS is WGS 84, when I add this layer it adds immediately.
If the project CRS is something else like EPSG:2193, when I add this layer it takes a long time, and when I check in the log there is a CRS message: "Transform error caught: forward transform of (0.000000, 0.000000)...". But this is a non-spatial table, so there shouldn't be anything to transform!
History
#1
Updated by Alister Hood over 11 years ago
Non-spatial tables also appear in the "layer order" panel, and they even have checkboxes (they do not have checkboxes in the "Layers" panel).
#2
Updated by Giovanni Manghi over 7 years ago
- Easy fix? set to No
- Regression? set to No
#3
Updated by Giovanni Manghi over 5 years ago
- Resolution set to end of life
- Status changed from Open to Closed
End of life notice: QGIS 2.18 LTR
Source:
http://blog.qgis.org/2019/03/09/end-of-life-notice-qgis-2-18-ltr/