On Mon, May 1, 2017 at 11:43 AM, Moritz Lennert < [email protected]> wrote: >> >> I have separated the binning code in r.in.lidar [3] so that it can be >> used in r.in.xyz > > > Is it different from the binning code in r.in.xyz ?
Not really. r.in.lidar was based on r.in.xyz, now they are different but of course the idea is to make them again as similar as possible. > > > >> and the missing module which would do >> the binning of a vector map into a raster map. There is actually a large >> overlap with code for grid-based decimation of a point cloud (2D with >> gridded or averaged X and Y). I already committed the code to r.in.lidar >> [4], but we had a discussion on mailing list and decided that this >> functionality should not be part of r.in.lidar, so it is disabled [5] >> but the code is still there. > > > So what you are saying is that the code should go into a library and be used by all relevant modules ? Yes. That would be ideal. Now it is in separate files in r.in.lidar and it can be copied and synced, but I think the library would not be less general than other libraries, so there is probably no reason to not include it. The only reason I didn't do it is that I wanted to do the refactoring in r.in.xyz first (which I never finished) and then work on the library. > > >> >> Anyway, a new module needs to be implemented for this. The name can be >> something like r.binning, r.vect.stats, r.point.stats, or >> r.points.stats. It might good project for beginners. > > > I like the idea. But do you really think this would be much faster than v.out.ascii | r.in.xyz ? I don't know if much faster, but it will be at least little faster. Another issue is that "v.out.ascii | r.in.xyz" is little hard to do on MS Windows and from GUI in general. Yes, there should have been a wrapper module for this already, but the a module to do the task directly is seems to me as a better solution esp. if there is the library. But the wrapper module may be a good way to start and to decide about the name and interface.
_______________________________________________ grass-user mailing list [email protected] https://lists.osgeo.org/mailman/listinfo/grass-user
