The best of two (but there would be a bit of overhead for the algorithm): set them to null as soon as two different values are found, keep the first encountered value otherwise (all the features with same value).
giovanni 2017-06-28 10:16 GMT+02:00 Anita Graser <[email protected]>: > > > On Wed, Jun 28, 2017 at 9:53 AM, Nyall Dawson <[email protected]> > wrote: >> >> Incidentally - how should we handle attributes here (and other similar >> algorithms)? Take the first feature's attributes? Drop all attributes? >> >> > I would take the first feature's attributes because I've seen multiple > times that input datasets for aggregation algorithms (such as hulls, > dissolve, ...) are prepared in a way that the result represents a certain > class, e.g. all points where column "type" value is 'tree'. Why should we > delete the 'tree' value then ... > > Best wishes, > Anita > > > > > _______________________________________________ > 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
