Hi,
Pierre Bourdin (gmail) wrote:
Hi,
I can confirm it works well with many textures...
Here's screenshot of some terrain build with 2 textures:
http://perso.imerir.com/bourdin/wiki/doku.php/en/projet/massane
The only problem I have is with Shapefile, but I'm using osggis for
that... If you know how to use them with osgdem ? I'm interested...
sorry, I should have made it more clear that I meant gdal raster
formats. I don't know of better way than osggis to include vector data.
jp
For the --terrain option, it works also very well, but I have to disable
GL_ARB extension with my ATI otherwise it crashes.
Pierre
Le vendredi 15 mai 2009 à 09:08 +0200, J.P. Delport a écrit :
Hi,
Mao wrote:
Hi! Recently, our project is planning to migrate from mini to VPB.
However, we encounter with several questions.
1. In the example of osgDEM, I infer that osgDEM processes tiff
format only. But tiff uses 32-bit offset which limits its size to 4G
bytes. Most of our data are ERDAS img file or rrd file, which are huge
in size. Yesterday, we processed an img file of size 20G bytes, and
gdal_translate it to a 21G bytes tiff. That confused me. How can VPB
handle extra bytes?
osgdem/virtualplanetbuilder can read all files that gdal can read, so
have a look here:
http://www.gdal.org/formats_list.html
You can use the gdal tools to split your large data into multiple
smaller geotiffs <2GB if you want.
2. Another thing is that, texture files we got sometimes are in
pieces, and we should use gdal_merge.py to merge them into one big tiff.
According to the source code, VPB can handle only one texture file. Can
we use multiple texture files?
It is better in pieces :) Smaller files, easier to handle. VPB can
handle multiple texture files, you can even pass a directory name and it
would use all the files in the directory.
See here too:
http://www.openscenegraph.org/projects/VirtualPlanetBuilder/wiki/ExampleClusterJPD
3. The last question is when applied with “--Terrain” or
“—HEIGHT_FIELD” options, there is no texture at all. Can we encapsulate
both texture and DEM data into one output file? And it seems that
osg::HeightField does not provide height = getHieghtAt(terrain.x,
terrain.y) method.
Hi, --terrain works for me. You can have DEM layer + multiple texture
layers. I can't answer about height_field.
jp
Thank you very much for listening!
------------------------------------------------------------------------
_______________________________________________
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Pierre BOURDIN
I.M.E.R.I.R.
Av. Pascot BP 90443
66004 PERPIGNAN
tél: 04 68 56 84 95
fax: 04 68 55 03 86
email: bour...@imerir.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
_______________________________________________
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
--
This message is subject to the CSIR's copyright terms and conditions, e-mail legal notice, and implemented Open Document Format (ODF) standard.
The full disclaimer details can be found at http://www.csir.co.za/disclaimer.html.
This message has been scanned for viruses and dangerous content by MailScanner,
and is believed to be clean. MailScanner thanks Transtec Computers for their support.
_______________________________________________
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
