Thanks Moritz - good suggestion - I just need to these as deliverables out to 2 separate clients (nice to get paid work for this stuff) - then I will write up and contribute back via Wiki.
>> >> The slow rate of writing out the v.net.allpair results from >> PostgreSQL was due to the sheer volume of line strings, as the number >> of pairs increased (n^2). Simple math said stop. I’ve since >> changed my approach and am using v.net.distance in a novel way where >> the to_cat is the origin, and the from_cat is a string of >> destinations - this is an equivalent way of generating multiple >> v.net.paths in a single operation. Moreover, I’m feeding each origin >> - destination collection into GNU Parallel as a separate job, so it >> rips through the data at scale! > > It would be great if you could put this info in a more structured form onto > the GRASS wiki, possibly as a FAQ. > > Moritz _______________________________________________ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
