>Another one I forgot to add (a bit unrelated): > >- lots of the processing algorithms don't correctly handle z/m >geometries and the changes are often trivial to allow them to. I'd >love to see someone generate a list (based off master) of all the >algorithms which currently don't maintain z and m values and which >should. > >Nyall
Am I remembering correctly that imports via DBManager also don't handle z/m geometries? Seems like that should be an easy fix too. I'll volunteer to identify the offending processing algorithms. We're talking QGIS algorithms, right? Not from GRASS or other providers? I might need some guidance but it seems pretty straightforward. Spencer
_______________________________________________ Qgis-developer mailing list Qgis-developer@lists.osgeo.org List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer
