[GRASS-dev] [GRASS GIS] #2185: Painfully Slow 'v.in.ogr' Vector Import

[GRASS GIS]

#2185: Painfully Slow 'v.in.ogr' Vector Import
-------------------------+------------------------------------------------
  Reporter:  justinzane  |      Owner:  grass-dev@…
      Type:  defect      |     Status:  new
  Priority:  normal      |  Milestone:  7.0.6
 Component:  Vector      |    Version:  svn-trunk
Resolution:              |   Keywords:  import, OGR, performance, v.in.ogr
       CPU:  x86-64      |   Platform:  Linux
-------------------------+------------------------------------------------

Comment (by mmetz):

 Replying to [comment:37 hcho]:
 > Yes, that's what I found too. Vect_line_intersection2 doesn't have this
 issue, but it still creates a single point intersection at the first
 vertex of the second new line (line ID 3) in the geojson example.
 >
 > Line ID 1: original unbroken line
 >
 > 1st iteration
 > Line ID 2-4: new broken lines
 >
 > 2nd iteration
 > Line ID 5: identical to line 3
 > Line ID 6: start node of line 3
 >
 > Lines 5 & 6 shouldn't be returned at all from the intersection routine,
 I think. The patch fixes this.

 I found another issue in Vect_segment_intersection(): the order of the
 segments matters, i.e. the intersection point of a with b can be slightly
 different from the intersection point of b with a. The second attached
 patch fixes that and also avoids that infinite loop. I opt to apply both
 patches.

--
Ticket URL: <https://trac.osgeo.org/grass/ticket/2185#comment:38>
GRASS GIS <https://grass.osgeo.org>