[vtkusers] vtkStripper limitation

[Carl Hetherington]

Hi,

I am using vtkStripper to collect a set of vtkLine segments into
vtkPolyLines.

There seems, to me, to be a slight limitation in the way vtkStripper
works.  The first two PolyLines that I get for an example data set are

PolyLine 1: from point id 0 to 795
PolyLine 2: from point id 3 to 0

Looking at the vtkStripper code, this output is logical because the code
finds point id 0 as a starting point and then goes on to build its first
polyline.  It does not realise that the first polyline could in fact be
extended back to point id 3.

>From my rather limited architectural understanding of VTK, I can see a
few solutions:

1.  Change vtkStripper so that when it finds a starting point for a
polyline it first searches along the length of the polyline until it has
found an end.  Only then should it start building the polyline.

2.  Add code to the end of vtkStripper to collect polylines that share end
points.

3.  Add code to my own (Python) code to collect polylines.

Does anyone have any opinions on this, or perhaps there is a better way
that I have missed?

Thanks,

Carl