On 26 October 2017 at 19:51, Matthias Kuhn <[email protected]> wrote: > Hi, > > I wouldn't have any problem with having one algorithm for all of this. > Personally I tend to think of geometry as just another attribute (in > good old database manner). > > The only thing I would be worried about is the naming which will make it > hard to discover for people looking to only modify the geometry. A > possibility would be to rename it to "refactor feature", "refactor > fields and geometry" or expose multiple algorithms (based on the same > code internally), "refactor fields", "refactor feature", "refactor > geometry".
Note that there's already a separate "geometry by expression" algorithm in master, so I'm not sure it makes sense to add this to the "refactor fields" algorithm. However - I do think there'd be LOTS of use in adding this to the new "aggregate" algorithm. Nyall > > Cheers > Matthias > > On 10/26/2017 11:44 AM, Arnaud Morvan wrote: >> Hello, >> >> A customer ask us to allow, in refactor fields, the use of an expression >> to calculate the output geometry. >> >> I know that the orientation in QGIS 3.0 is to have simple algorithms >> instead of having complex ones, >> it that direction, it should make sense to create another algorithm to >> do that. >> >> But another side, having this functionnality in refactorfields allow >> doing complex things without need to create a model. >> >> Does anyone has an opinion on this ? >> >> Regards >> > _______________________________________________ > QGIS-Developer mailing list > [email protected] > List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer > Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer _______________________________________________ QGIS-Developer mailing list [email protected] List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
