Hi Linh, On Wed, May 14, 2008 at 8:20 PM, Linh Phan <[EMAIL PROTECTED]> wrote: >> In VPB there isn't any support for substituting a custom value for >> NoDataValue elements, >> this could be added though. >> > > That would be great if you can added to VPB. Please let me know when you > have it in so I can test it. :) Thanks Robert.
When I say this "could be added" it means just that, I didn't say specially who would be added it... VPB being open source is open to end users adding features that they require, now these features might be added later by someone else so you could wait and hope that the feature will be added when you need it, or just roll your sleeves and code it. For this particular feature the next time I'm working around this code I'll have a look at adding an option to specify the default elevation to use, it shouldn't take more than a couple of hours. However, I can't say when I'll get around to this. > Yes, I have spent the last few weeks to migrate over to OSG-2.4 using > osgViewer now, which I think is easier to use than osgProducer::Viewer. Great this will make utilisiation of latest VPB features much easier. It's good to hear that you find osgViewer easier to use than osgProducer, as this was the one of the goals for the work. >> And then pass the .vrt file to VPB instead of your .tif >> > I have tried this but VPB didn't support the NoDataValue elements and still > inserted 0's for where there were no data. VPB does support GDAL NoDataValue, it just substitues 0's in for them, or alpha's them out in the case of textures. What is missing is the ability to define the default elevation to use when a NoDataValue occurs. Robert. _______________________________________________ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
