Hi, I'm plan to process a large database with more than 1 TB of source data. Therefore I don't want to include all source data into a single database but would like to have a modular database with "optional" parts.
I browsed the VPB sources and discovered somer options I do not understand, I would be glad to get some basic hints.. The unknown options are: --layer-inheritance [Lowest/Nearest/No] : What does this option cause? --set <setname>, What is a set name? what is the difference to the comment string I can add to the topmost node of the database via --comment? --optional-set <setname> --remove-optional-set <setname> --optional-image-layout [inline/external-set-dir/external-local-dir] --optional-elevation-layout [inline/external-set-dir/external-local-dir] How does the idea of optional layers work? I assume it is possible to plug in optional layers for DEM and for textures independent? What is about the layout (inline/external-set-dir/external-local-dir) Any hint wherer to look to learn how that works? Do I need a special terrain technique to use such a database with optional layers, or can I use the standard osgViewer? As "return of investment" of your help, I will write a usage example in the VPB wiki as soon as I understand how that works. Thank you! Cheers, Torben ------------------ Read this topic online here: http://forum.openscenegraph.org/viewtopic.php?p=41087#41087 _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
