Hi Andreas, also Processing relies on the OGR way.
Exposing native DXF import/export in Processing is in my TODO. пн, 2 бер. 2020 о 15:06 Andreas Neumann <a.neum...@carto.net> пише: > > The second option has mainly the following advantage: > > - The import is "live" meaning it is not importing into an intermediate > Geopackage file > > - if you don't care about styling/labeling, but only raw geometry then > it might work faster > > Maybe there are more differences that I am not aware of. > > Andreas > > Am 02.03.20 um 14:02 schrieb Paolo Cavallini: > > Hi Andreas, > > > > Il 02/03/20 13:57, Andreas Neumann ha scritto: > > > >> I think this situation is not ideal and Giovanni has to deal a lot with > >> such issues, where people try the second option and run into issues or > >> are disappointed, because styling/labeling/blocks are not treated well. > >> > >> Any idea how we can solve this? Can we disable OGR import (the second > >> method) and re-route the "Save As" way to our nativ export? > > I agree, duplication is confusing. Is anoyne aware of any case in which > > the second option is actually useful? > > Cheers. > _______________________________________________ > QGIS-Developer mailing list > QGIS-Developer@lists.osgeo.org > List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer > Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer -- Alexander Bruy _______________________________________________ QGIS-Developer mailing list QGIS-Developer@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer