9 Mar
2010
9 Mar
'10
9:27 p.m.
The problem is not with affecting the Boost.Geometry submission, but the problem is with amount of work required to make the submission happen and our time. As we've discussed internally in team, we need to focus on the after-review tasks first.
We'll keep you on the list for next year then :) Yes, but I think I gave a broad overview.
A student could work on small part, a specific function. For example, to polygonize Boost.GIL raster by creating Boost.Geometry vector for all connected regions of pixels in the raster sharing a common value, It should be feasible in the given time frame.
Yes, I can see how there are a number of interesting in that domain. Both rasterizing and vectorizing. Andrew Sutton andrew.n.sutton@gmail.com