Robert, I'm not sure that we want to keep the terrain interpolation code that I added to DataSet.cpp as it doesn't fix the issue that the code was intended for, it was just some test code. I didn't mean to send out those files as official submissions, it was more for Edgar to test out the double bounding boxes and see if it fixes his problem. I'm comfortable leaving in the double bounding box code as it is relatively benign, but perhaps the interpolateTerrain flag should be set to false by default until it proves useful/necessary to someone.
Thanks, Jason ________________________________________ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Robert Osfield Sent: Monday, May 15, 2006 9:13 A To: osg users Subject: Re: [osg-users] osgTerrain elevation accuracy Hi Jason, Thanks for the changes, I've now merged and checked them into CVS. I fixed the indentation to better fit with the rest of the OSG i.e. 4 space indentation rather than 2 space indentation. osgdem also needed a tweak to use the new GeospatialExtents obejct. Robert. On 5/12/06, Jason Beverage <[EMAIL PROTECTED]> wrote: Hi Edgar, I did a quick substitution of all bounding box code in the DataSet class with a 2D double bounding box called GeospatialExtents as Robert suggested. I've tried it on a few datasets here and things have worked fine so far, but the issue I'm having with scene graph heights being off by quite a large amount from the source data is still present. I added a bool, interpolateTerrain in readHeightField that takes an alternate code path to attempt to prevent upsampling of the terrain by GDAL, but my problem still exists. I figured since I'd made these changes I'd send it out to you to see if it fixed whatever problems you've been having with the float bounding boxes. Thanks, Jason -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jason Beverage Sent: Tuesday, May 09, 2006 9:10 A To: osg users Subject: RE: [osg-users] osgTerrain elevation accuracy I'll try to do this today. I've written some code to do bilinear interpolation on the source terrain data, but it is still off. Maybe a combination of it and the double bounding box will solve the issues I'm having. Thanks for your help, Jason -----Original Message----- From: [EMAIL PROTECTED] [mailto: [EMAIL PROTECTED] On Behalf Of Robert Osfield Sent: Tuesday, May 09, 2006 4:31 A To: osg users Subject: Re: [osg-users] osgTerrain elevation accuracy On 5/8/06, Edgar Ellis < [EMAIL PROTECTED]> wrote: > I haven't had a chance deal with the bounding box precision, but as > Robert said using doubles should solve the problem (perhaps a BoundingBoxd?) A local double XY box would be more appropriate as it only uses the XY dimensions of the osg::BoundingBox. _______________________________________________ osg-users mailing list [email protected] http://openscenegraph.net/mailman/listinfo/osg-users http://www.openscenegraph.org/ _______________________________________________ osg-users mailing list [email protected] http://openscenegraph.net/mailman/listinfo/osg-users http://www.openscenegraph.org/ _______________________________________________ osg-users mailing list [email protected] http://openscenegraph.net/mailman/listinfo/osg-users http://www.openscenegraph.org/ _______________________________________________ osg-users mailing list [email protected] http://openscenegraph.net/mailman/listinfo/osg-users http://www.openscenegraph.org/
