Open qgib opened 8 years ago
Author Name: Jürgen Fischer (@jef-n)
So what are you suggesting?
Author Name: Paolo Cavallini (@pcav)
To use QGIS provider for CSV instead of GDAL, when loading layers from the browser.
Author Name: Jürgen Fischer (@jef-n)
Author Name: Even Rouault (@rouault)
Repeating my comment in #22088: I'd note that the OGR CSV driver has gained editing capabilities in GDAL 2.1dev (specificaly to be used through QGIS), whereas AFAICS the QGIS CSV provider is read-only. It would be a shame that using the OGR CSV driver is no longer accessible. In my (admitedly biased) opinion, dealing with formats should be GDAL job ;-)
Author Name: Paolo Cavallini (@pcav)
Sounds right to me: why having a QGIS provider then?
Author Name: Nathaniel V. Kelso (@nvkelso)
+1 for keeping GDAL/OGR CSV provider. The edit ability in 2.1dev is really useful!
Author Name: Nyall Dawson (@nyalldawson)
Sounds right to me: why having a QGIS provider then?
There's lots of features in the QGIS provider not available in the OGR one. Eg custom delimeters and caching. If all these extra features were available in the OGR provider then I'd be in favor of removing the QGIS one.
Author Name: Sebastian Dietrich (Sebastian Dietrich)
I think one problem is that many users don't even know there are two different ways of handling a CSV file, nor do they know when they are used:
I was one of those users until I investigated #22088.
Author Name: Giovanni Manghi (@gioman)
Author Name: Paolo Cavallini (@pcav)
Still a unified approach seems useful to me for QGIS 3.x. Feel free to close this if appropriate.
Author Name: Giovanni Manghi (@gioman)
Author Name: Paolo Cavallini (@pcav) Original Redmine Issue: 14093
Redmine category:browser
For files that are supported by both native QGIS and the GDAL/OGR providers, like CSV, it is usually preferable to use the native one over the GDAL one. See also #22088
Related issue(s): #22088 (relates) Redmine related issue(s): 14078