[GRASS-user] GRASS and Blender

[G. Allegri]

Thanks Vincent for sharing your experience.
Indeed there aren't production ready (open source) tools to manage the
whole process.
Point data are relatively easier to manage (though they generally bring
their complexities), but CityGML like models, geological models, etc. lack
a ready to use toolbox.
I know that 3D brings exponential difficulties then 2D, and probably theres
isn't such a widespread need for it to have enough investments to support
its development in the FOSS context.
A good work is being done by Sourcepole, with PostGIS + (SF)CGAL, but the
road is still very long...

giovanni


2014-05-19 11:43 GMT+02:00 Vincent Bain <bain at toraval.fr>:

> Le lundi 19 mai 2014 à 09:57 +0200, G. Allegri a écrit :
> >
> > Do you have experimented robust workflows that can do one or both
> > things?
>
> Hello Giovanni,
> yes in a production context (natural hazrd ingeneering) I do this kind
> of back and forth quite often, but with limited functionality: for my
> personal needs, it is mainly a question of 3d point clouds export/import
> with coordinate system switching; unfortunately I cannot give any advice
> concerning the consistency of attribute data. To keep record of an
> existing database structure within GRASS, perhaps a first step would be
> to export 3d objects with their cat values, so one would retrieve it
> when importing back to GRASS.
> In blender for example I know you can add custom properties to objects
> or classes of objects, but don't know how simple it is to link it with
> e.g. .vtk "POINT_DATA" or .ply feature "property". I'll dig into that.
>
> V.
>
>
>


-- 
Giovanni Allegri
http://about.me/giovanniallegri
Twitter: https://twitter.com/_giohappy_
blog: http://blog.spaziogis.it
GEO+ geomatica in Italia http://bit.ly/GEOplus
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/grass-user/attachments/20140519/d03f471c/attachment.html>