Version 31 (modified by osg, 6 years ago)

Replaced help dump with current osgDem arguments

osgdem

osgdem is utility program for reading geospatial imagery and digital elevation maps (DEM's) and generating large scale 3D terrain databases that OpenSceneGraph applications can load and browse in real-time. What follows is a step-by-step guide to using osgdem, followed by a list of full options available.

Quick step by step guide

What follows are the steps required to get osgTerrain/osgdem compiling and an example of how to use it to process imagery and DEM's to generate a paged databases.

1. Download, compile & install GDAL.

2. For UNIX 'make' users, make a copy of Make/dependencies and change the GDAL_INSTALL entry to:

set GDAL_INSTALL = true

Then tell the build to use your custom dependencies by setting the environmental variable OSG_DEPENDENCIES to the absolute path to your file i.e.:

export OSG_DEPENDENCIES=/home/billgates/my_osg_dependencies

3. Rebuild the OSG & install (if you haven't already).

4. Oh, make sure you have a couple of GB of spare disk space, because you're going to need it :-)

5. Download some data, for this example I'm using the Puget Sound data at:

http://www.cc.gatech.edu/projects/large_models/ps.html
Download Elevation Map: 16385 × 16385 PNG: 188MB
Download Texture Map: 16384 × 16384 PNG: 268MB

6. To avoid aliasing artifacts when accessing data I use GDAL utilitiy programs to generate overviews (basically mip maps stored in the .tiff format) via:

gdal_translate ps_height_16k.png ps_height_16k.tif
gdaladdo -r average ps_height_16k.tif 2 4 8 16 32

gdal_translate ps_texture_16k.png ps_texture_16k.tif
gdaladdo -r average ps_texture_16k.tif 2 4 8 16 32

7. Now its time to run the osgdem example to generate your PagedLOD database, the more levels you generate the longer it will take (exponentially so). 'osgdem' is just a front end to osgTerrain::DataSet where all the hard work happens. Here's what to run :

osgdem --xx 10 --yy 10 -t ps_texture_16k.tif \ 
--xx 10 --yy 10 -d ps_height_16k.tif \ 
-l 8 -v 0.1 -o puget.ive -a pegout.osga

Then go away for lunch, afternoon and tea, as generating this much data takes a while... If you don't wish to wait for the full database then reduce the number of levels it generates by setting the -l option to a lower value such as 3.
The command line options used above are:
The first part the --xx and --yy is specifying the size of the pixels in meters, since these png/tif don't have any geospatial data of their own, if you have geospatialised files then you won't need this.

The second part -t <filename> is the option for specificing the texture maps to use, you can use as many times as you wish, osgTerrain::DataSet will moziac them into a single database.

The third part -d is the option for specifying the digital elevation maps to use, as with the textures you can use as many as you like.

The -l option specificies the maximum number of levels to generate. If you use a large number then the database generation will stop once the max resolution of your source data is matched by the resulting database. The database generation will decend further where there is high res source data, decend less where there is lower res data.

The -v option specifies the scaling factor which the height is multiplied by.

] The -o <filename> is the output format to generate the databases in. This will be the name of the topmost file in the one you should load. It can be a .ive or a .osg. The .ive is faster and has embedded files.

And finally the -a <filename> tells the osgdem to write all tiles to a single archive, in this a the OpenSceneGraph native archive format, which uses the extension .osga to disguinish itself. The use of archives is not required, but is recommend since it makes managment of the whole database much more convinient - you have a single file to manage rather than what could be 10's of thousands as is the case of large databases.

8. Time to play. Simply load the database in your app, and if you've based it on osgViewer::Viewer or CompositeViewer? all the paging support is already built in. The standard osgviewer works just fine so, here goes:

osgviewer pegout.osga

9. If your imagery and DEMs have geospatial coords associated with them then the -xx, --yy and -v options will not be required, making it much simplier to specify - you just need to specifiy options such as -t imge.tif and -d terran.dt0 without any need to set the coordinate system.

10. osgdem can automatically handle mosaicing of sets of files. These can be specified via a sequence of -t <filename> and -d <filename> pairs on the commandline, or via -t <directoryname> and -d <directoryname>.

Commandline options

Parameter Description
General
--version
--version-number
--run-path
-h or --help Display commandline arguments information
--task
-s
--so
--report
--cache <filename> Read the cache file to use a look up for locally cached files.
Building
-d <filename> Specify the digital elevation map input file to process
-t <filename> Specify the texture map input file to process
--building <filename> Specify building outlines using shapefiles.
--forest <filename> Specify forest outlines using shapefiles
-a <archivename> Specify the archive to place the generated database
--ibn <buildname> Specify the intermediate build file name
-o <outputfile> Specify the output master file to generate
-l <numOfLevels> Specify the number of PagedLOD levels to generate
--image-ext <ext> Specify the Image format to output to via its plugin name, i.e. rgb, dds, jp2, jpeg.
--levels <begin_level> <end_level> Specify the range of lavels that the next source Texture or DEM will contribute to.
--layer <layer_num> Specify the layer that the next source Texture will contribute to..
-e <x> <y> <w> <h> Extents of the model to generate
--cs <coordinates system string> Set the coordinates system of source imagery, DEM or destination database. The string may be any of the usual GDAL/OGR forms, complete WKT, PROJ.4, EPS
--wkt <WKT string> Set the coordinates system of source imagery, DEM or destination database in WellKownText? form.
--wkt-file <WKT file> Set the coordinates system of source imagery, DEM or destination database by as file containing WellKownText? definition.
--skirt-ratio <float> Set the ratio of skirt height to tile size
--HEIGHT_FIELD Create a height field database
--POLYGONAL Create a height field database
--TERRAIN Create a osgTerrain::Terrain database
--LOD Create a LOD'd database
--PagedLOD Create a PagedLOD'd database
-v Set the vertical multiplier
--compressed Use OpenGL compression on RGB destination imagery
--RGBA-compressed Use OpenGL compression on RGBA destination imagery
--RGB-16 Use 16bit RGB destination imagery
--RGBA-24 Use 24bit RGB destination imagery
--RGB-16 Use 16bit RGBA destination imagery
--RGBA Use 32bit RGBA destination imagery
--vector Interpret input as a vector data set
--raster Interpret input as a raster data set (default)
--max-visible-distance-of-top-level Set the maximum visible distance that the top most tile can be viewed at
--no-terrain-simplification Switch off terrain simplification.
--default-color <r,g,b,a> Sets the default color of the terrain.
--radius-to-max-visible-distance-ratio Set the maximum visible distance ratio for all tiles apart from the top most tile. The maximum visuble distance is computed from the ratio * tile radius.
--no-mip-mapping Disable mip mapping of textures
--mip-mapping-hardware Use mip mapped textures, and generate the mipmaps in hardware when available.
--mip-mapping-imagery Use mip mapped textures, and generate the mipmaps in imagery.
--max-anisotropy Max anisotropy level to use when texturing, defaults to 1.0.
--bluemarble-east Set the coordinates system for next texture or dem to represent the eastern hemisphere of the earth.
--bluemarble-west Set the coordinates system for next texture or dem to represent the western hemisphere of the earth.
--whole-globe Set the coordinates system for next texture or dem to represent the whole hemisphere of the earth.
--geocentric Build a database in geocentric (i.e. whole earth) database.
--radius-polar Set the polar radius of the ellipsoid model when building a geocentric database.", "6356752.3142
--radius-equator Set the polar radius of the ellipsoid model when building a geocentric database.", "6378137
--spherical Set the polar and equator radius both to the average of the two.
--range
--xx
--xt
--yy
--yt
--zz
--zt
--BuildOverlays? [True/False] Switch on/off the building of overlay within the source imagery. Overlays can help reduce texture aliasing artificats.
--ReprojectSources? [True/False] Switch on/off the reprojection of any source imagery that aren't in the correct projection for the database build.
--GenerateTiles? [True/False] Switch on/off the generation of the output database tiles.
--version Print out version
--version-number Print out version number only.
--tile-image-size Set the tile maximum image size
--tile-terrain-size Set the tile maximum terrain size
--comment Added a comment/description string to the top most node in the dataset
-O string option to pass to write plugins, use \" \" for multiple options
--subtile <LOD> <X> <Y> Set the subtile to begin the build from.
--record-subtile-on-leaf-tiles Enable the setting of the subtile file name of the leaf tiles.
--split Set the distributed build split level.
--splits Set the distributed build primary and secondary split levels.
--run-path Set the path that the build should be run from.
--notify-level Set the notify level when logging messages.
--type-attribute Set the type name which specify how the shapes should be interpreted in shapefile/dbase files.
--height-attribute Set the attribute name for height attributes used in shapefile/dbase files.
--height Set the height to use for asscociated shapefiles.
--mask Set the mask to assign indivual shapefile/model.
--terrain-mask Set the overall mask to assign terrain.
--read-threads-ratio <ratio> Set the ratio number of read threads relative to number of cores to use.
--write-threads-ratio <ratio> Set the ratio number of write threads relative to number of cores to use.
--build-options <string> Set build options string.
--interpolate-terrain Enable the use of interpolation when sampling data from source DEMs.
--no-interpolate-terrain Disable the use of interpolation when sampling data from source DEMs.
--interpolate-imagery Enable the use of interpolation when sampling data from source imagery.
--no-interpolate-imagery Disable the use of interpolation when sampling data from source imagery.

Coordinate System Tips

WKT coordinate system definition format is a very comprehensive, but difficult to use as a "human enter-able" specifier for coordinate systems. osgdem uses GDAL under the hood which also allows definition of the --cs flag in PROJ4 format. PROJ4's definition format is much more human friendly.
Examples:

  • For a Latitude (Y Axis), Longitude (X Axis) and Altitude coordinate system in units of degrees use: osgdem ... --cs "+proj=latlong +datum=WGS84" -o ...
  • For a UTM coordinate system referenced to zone 47 (in this example) in units of meters use: osgdem ... --cs "+proj=utm +zone=47" -o ...
  • For a Geocentric system, with the origin being the center of the earth and units in meters use: osgdem ... --geocentric -o ...