Thank you Jason,
the disadvantage of osgEarth (so far) is the fact it relies on its own reader.
I would like to use my reader for accessing the data, and OSG for rendering and
interacting. Can I plug in my own IO layer in osgEarth?
Cheers,
Teodor
--
Read this topic online
Teodor Hanchevici wrote:
Hi Chris,
I will try looking into shaders. I wonder if it creating a 8x8 grid of
HeightFields and glue them to something so that they move as a single
object would solve the problem.
You mentioned that the data is put into a quad-tree, is it possible to limit
the
Hi Teodor,
osgEarth uses a plugin system to access the data. The stock drivers that
come with osgEarth (http://wush.net/trac/osgearth/wiki/TileSourcePlugins)
are simply plugins. It's fairly straightforward to write your own plugin to
support whatever type of data you need to visualize.
Thanks,
HI Teodor,
You need to use osgTerrain to do height field rendering. With larger
datasets you need to start looking at creating a paged database, and
the tool to use for this is VirtualPlanetBuilder to read your source
data and generate paged databases for you. Using VPB to generated
paged
Hi,
J-P indeed I was using it with a osg::ShapeDrawable, I will be more specific in
the future, sorry.
Robert, I will look at osgTerrain. Does this library allow one to change the
values at a specific row and column in the height field or it is used for
display only.
Thank you!
Cheers,
Hi,
I am trying to build a simple DEM editing tool, so I have to read the data
myself from different file formats. I need not only to render the surface but
also to interact and change its values.
I tried to duplicate the example in osgterrain and the performance was worse
than before.
This
Teodor Hanchevici wrote:
Hi,
I am trying to build a simple DEM editing tool, so I have to read the data
myself from different file formats. I need not only to render the surface but
also to interact and change its values.
The VPB terrain system is mainly for non-dynamic terrain.
Can
Hi Chris,
I will try looking into shaders. I wonder if it creating a 8x8 grid of
HeightFields and glue them to something so that they move as a single object
would solve the problem.
You mentioned that the data is put into a quad-tree, is it possible to limit
the depth of the tree somehow? I
Hi Teodor,
You can also take a look at osgEarth (http://www.osgearth.org ) and see if
it would be suitable for your needs. It is suited for runtime terrain
database generation and I actually uses osgTerrain under the hood. There
isn't any editing capabilities in it as of right now but it's at
Hi all,
I am trying to use a HeightField to render DEM from a TIFF file. Things work
fine up to 1024x1024 grid, however the performance is not so great for
2048x2048 or higher grids. Ideally I would like to be able to load 4096x4096
fast (1-2 seconds) and render them smoothly (15fps or
Hello Teodor,
1. Is this class the appropriate one for what I want to do?
I'm assuming you're using osg::HeightField with osg::ShapeDrawable - you
didn't specify... Please try to be more precise in the future.
In that case, no, it's not appropriate for large height fields. As
Robert has
11 matches
Mail list logo
