Thank you for the replies everyone. Now I have a few more things worth looking into. To explain my current situation in more detail, this is the current test database that I'm working on:
osgdem --polygonal --compressed --mip-mapping-hardware --range -87721 87721 111320 -111320 -t 37N_123Wx39N_121W.tif --range 0 1113 0 1113 -t 10seh955060.tif --range -87721 0 0 -111320 -d dted/W123/N37.DT1 --range -87721 0 111320 0 -d dted/W123/N38.DT1 --range 0 87721 0 -111320 -d dted/W122/N37.DT1 --range 0 87721 111320 0 -d dted/W122/N38.DT1 -l 12 --tile-image-size 512 -o eastbay.ive My data consists of geotiffs for textures and .dt1 files for elevation. If memory serves, .dt1 just means DTED level 1. Ultimately, I'd like to take some of the leaf tiles, convert them to .flt, edit them in Creator, and convert them back to .ive so they get loaded into the database. (In a graph (in this case, OpenSceneGraph), a leaf node is a node with no children). According to http://www.openscenegraph.org/projects/VirtualPlanetBuilder/wiki/CommandLineOptions , --range is for use when you want a flat database (not geocentric), and flat is what I want. But now it sounds like maybe I should be using --cs instead of --range. I searched high and low on Google for something that explains "the usual GDAL/OGR forms, complete WKT, PROJ.4, EPS" so that I can use --cs, but everything I found is written for people who are already experts at that stuff. Anyone know where I can find something that tells me how to make one of these strings from scratch? Particularly, one that will get me a database that squashes 2x2 degrees of data centered at (38N, 122W) (all data containing geographic info) into the range -87721 87721 111320 -111320 meters? > w.r.t 4: you have missed the number 4 :) d'oh! > w.r.t. 5: VPB adds LODs until both, texture and DEM, are displayed in full > resolution. As far as > I know does VPB exactly what you want! Yes, it *does* do exactly what I want. ...Arg. Shame on me for testing this so poorly before. ...And yea for VPB! > Have you tried the optimizer? I don't know if that could work.. Haven't applied it to this problem yet, but it's on my list. Too many projects. > We had to convert the mesh nodes to triangles in creator as well as > flatten the transforms. Otherwise we had all kinds of issues. Couldn't > edit certain areas, crashes, lighting errors, etc. This was with a > fairly recent version of creator. I've been using --polygonal, so I think I should get easy-to-edit polygons. My version of Creator is *really* old. Anyway, I'm going in for a demo of new Creator next week, so maybe I'll load up a CD with models to test and include some generated terrain tiles. -- Terry Welsh / mogumbo 'at' gmail.com www.reallyslick.com / www.mogumbo.com _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
