[GRASS-user] GRASS and Blender
Hamish
hamish.webmail at gmail.com
Sun May 18 23:44:38 PDT 2014
Hamish wrote:
> > the added interoperability with VTK-aware software is always welcome
Vincent:
> regarding this incredible interoperability in open source projects, I
> am thinking about the lack of 3d vector digitizing tools in GRASS.
> Typically when I need to model a dam or a wedge on a topographic
> surface, I move to blender: maybe some portions of blender interface
> code (written in python) could be used as a basis for further
> improvement of v.digit...
the main question is the maintenance load and what we can value-add
to it. if we lack the developers to maintain any specialist code and it
is just a clone of an external foss4g program, sometimes it is better
to outsource and let the 3rd party experts maintain the stuff they are
experts at, and link into it as a dependency or use the two programs
together in the workflow (as many do for gdal command line tools +
grass). if we can add/integrate some geo-* smarts to their tool then it
gets very interesting to put in the core grass. We could also probably
have some success requesting API hooks into their libraries if
needed/useful.
but I've no idea how much code or complication we're talking about in
this case, so just my 2c.
regards,
--
Hamish <hamish.webmail at gmail.com>
More information about the grass-user
mailing list