Thanks Nyall. I think I had a misunderstanding in that the XY routines were
the preferred method to use unless you have Z/M dimensions. I will look at
changing my code.
Calvin
On Wed, Dec 5, 2018 at 6:06 PM Nyall Dawson wrote:
> On Wed, 5 Dec 2018 at 02:52, C Hamilton wrote:
> >
> > QgsGeometry has the following static functions
> >
> > QgsGeometry.fromPolylineXY( list of QgsPointXY)
> > QgsGeometry.fromMultiPolylineXY( list of QgsPointXY lists)
> >
> > If I am working with QgsPoint rather than QgsPointXY there is
> >
> > QgsGeometry.fromPolyline( list of QgsPoint)
> >
> > However there is not a similar multi polyline function. Why not?
>
> Because there's been no demand for this, until now. But in general all
> those fromPolylineXY etc methods should be avoided wherever possible.
> They are very slow (lots of list allocations) and don't handle Z/M
> dimensions.
>
> You're better to work directly with the QGIS geometry subclasses like
> QgsLineString, QgsMultiLineString instead.
>
> Nyall
>
>
> >
> > QgsGeometry.fromMultiPolyline( list of QgsPoint list)
> >
> > What is the proper way to implement this?
> >
> > Thanks
> > ___
> > Qgis-user mailing list
> > qgis-u...@lists.osgeo.org
> > List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
> > Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
>
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
