[GRASS-dev] Re: [GRASS GIS] #224: cache bug in DGLib

GRASS GIS trac at osgeo.org
Sun Oct 24 06:46:59 EDT 2010


#224: cache bug in DGLib
----------------------+-----------------------------------------------------
  Reporter:  martinl  |       Owner:  grass-dev@…              
      Type:  defect   |      Status:  reopened                 
  Priority:  major    |   Milestone:  6.4.1                    
 Component:  Vector   |     Version:  6.4.0                    
Resolution:           |    Keywords:  dglib, cache, v.net.path 
  Platform:  All      |         Cpu:  All                      
----------------------+-----------------------------------------------------

Comment(by mmetz):

 Replying to [comment:16 huhabla]:
 > I have tested v.net.path using a dataset with 460000 lines, one start
 point and 100 end points. It works quite fast (<5min) and the result seems
 to be correct. Screenshot is attached. IMHO back porting to 6.4.1 would be
 greatly appreciated.

 Thanks for testing!

 Would it be asked too much to do the same test with the cache disabled and
 compare results? I am aware that this might take some time, e.g. running
 overnight.

 Also, with cache enabled it would be great if you could design a test
 where you recover a path to a given point and in the very next step
 recover a path from the same starting point but the end point must be
 exactly one line (edge) farther away from the previous end point. First,
 this second end point must be reachable, second, the shortest path to this
 second end point should go through the previous end point, unless there is
 a shorter path avoiding the previous end point. I have done that with a
 small test vector that should represent all sorts of special cases
 targeting BUG1 and BUG2 but I might have overlooked something.

 Markus M

-- 
Ticket URL: <http://trac.osgeo.org/grass/ticket/224#comment:17>
GRASS GIS <http://grass.osgeo.org>



More information about the grass-dev mailing list