Bug report #11520
CSV import plugin does not ask for CRS
|Category:||Data Provider/Delimited Text|
|Affected QGIS version:||master||Regression?:||No|
|Operating System:||Easy fix?:||No|
|Pull Request or Patch supplied:||No||Resolution:||fixed/implemented|
|Crashes QGIS or corrupts data:||No||Copied to github as #:||19790|
When user settings are set to : "set CRS of new layers to project CRS", then no dialog is raised to ask for choosing actual CRS of delimited text layers, and this can lead to mis-reprojected layers. (say you load WGS84 data, in a project with another projection)
It is easy to solve afterward by setting the right CRS definition, but common users fall in the caveat here.
From a UX point of view, it doesn't seem pertinent that a import plugin uses settings of new layers. I would vote for a CRS chooser in Delimited text import dialog, eventually disabled if user inserts EWKT text as geometry (not sure about this).
#3 Updated by Regis Haubourg over 6 years ago
Giovanni Manghi wrote:
the option actually make sense to me, this is why in general options > CRS there is the option "prompt for CRS". But anyway a CRS selector in the import CSV plugin it would be handy indeed.
Hi Giovanni, the option makes totally good sense, agreed. But importing data is not seen by users as creating data, so the option should not apply to Import use case. An external datasource already has its SRS (explictly defined or not). I calibrate qgis profiles here with the option to automatically create data in project crs, because there is one legal crs to use, defined almost everywhere. With this On, QGis is simpler, but sometimes the workflow generates minor problem. That could be a good improvement (I saw Chris agreed, thanks!).