So right now we have QgsFeature that contains ID, attributes and a
geometry. I think we should keep that as-is because this is what is
usually expected from a layer.
And the users would be forced to deal with yet another pretty strong API
change besides the API changes you plan to commit.
In order to support multiple geometries per feature, we could possibly
allow QgsGeometry class as another attribute type (next to int, double
and QString). So providers like postgis that support multiple geometry
columns could return additional geometries wrapped as attributes in
QVariant. Would that work for you?
This would work perfectly well. I'm wondering how much work it would
mean to get this.
Matthias
_______________________________________________
Qgis-developer mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/qgis-developer
