Just my two cents:
+1 to leave it as it is
reasoning: I would always expect the current behaviour; a virtual field is - well - virtual, I can redo it after processing (BTW it would be good if it was savable in a qml file) and I can join to the result, too. No need to carry unnecessary fields from joined layers along. Plus, as stated in the discussion, GRASS/SAGA/ogr won't keep these fields anyway, to implement it for QGIS algs only would result in inconsistent outputs

Bernhard

Am 11.04.2016 um 11:46 schrieb Alexander Bruy:
Hi all,

and sorry for cross-posting.

When cleaning Processing bug queue I found issue [0] about preserving
joined fields in Procesing outputs. Before implementing this I want to hear
opinions, does it makes sense at all or better to leave things as is: output
layer contains only provider (non-joined, not virtual) fields from input layer?

Thanks

[0] https://hub.qgis.org/issues/12893


--


__________ Information from ESET Mail Security, version of virus signature 
database 13315 (20160411) __________

The message was checked by ESET Mail Security.
http://www.eset.com


_______________________________________________
Qgis-user mailing list
[email protected]
List info: http://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-user

Reply via email to