Changeset 3277

Show
Ignore:
Timestamp:
08/14/04 17:42:01 (10 years ago)
Author:
don
Message:

P*E*G*O*U*T Sound. Spelling fixes.

Files:
1 modified

Legend:

Unmodified
Added
Removed
  • OpenSceneGraph/trunk/doc/osgdem.html

    r3262 r3277  
    3838<hr style="width: 100%; height: 2px;"> 
    3939<h3><a name="Quick_step_by_step_guide:"></a>Quick step by step guide:</h3> 
    40 Follows are a the steps required to get osgTerrain/osgdem compiling and 
    41 an example of how to use it to process imagery and dem's to gernerate a 
     40What follows are the steps required to get osgTerrain/osgdem compiling and 
     41an example of how to use it to process imagery and DEM's to generate a 
    4242paged databases.<br> 
    4343<br> 
     
    46462) Get the latest OSG in CVS.<br> 
    4747<br> 
    48 3) For unix Make users, make a copy of Make/dependencies and change the 
     483) For UNIX 'make' users, make a copy of Make/dependencies and change the 
    4949GDAL_INSTALL entry to:<br> 
    5050<br> 
     
    5353<span style="font-weight: bold;"></span></div> 
    5454<span style="font-weight: bold;"><br> 
    55 &nbsp;&nbsp;&nbsp; </span>Then tell the build to use you custom 
     55&nbsp;&nbsp;&nbsp; </span>Then tell the build to use your custom 
    5656dependencies by setting the environmental variable OSG_DEPENDENCIES to 
    5757the absolute path to your file i.e.:<br> 
     
    6161</div> 
    6262&nbsp;<br> 
    63 4) Rebuild the OSG &amp; install (if you havn't already used <br> 
    64 &nbsp;<br> 
    65 5) Oh make sure you have a couple Gb of spare disk space,&nbsp; because 
    66 you going need it :-) <br> 
    67 &nbsp;<br> 
    68 6) Download some data, for this example I'm using the PegoutSound data 
     634) Rebuild the OSG &amp; install (if you haven't already).<br> 
     64&nbsp;<br> 
     655) Oh, make sure you have a couple of GB of spare disk space,&nbsp; because 
     66you're going to need it :-) <br> 
     67&nbsp;<br> 
     686) Download some data, for this example I'm using the Puget Sound data 
    6969at: <br> 
    7070&nbsp;<br> 
     
    787816384 &times; 16384 PNG: 268MB &nbsp;<br> 
    7979<br> 
    80 7) To avoid aliasing artifcates when accessing data I use <a 
     807) To avoid aliasing artifacts when accessing data I use <a 
    8181 href="http://www.remotesensing.org/gdal/gdal_utilities.html">GDAL 
    8282utilitiy 
    8383programs</a> to generate overviews (basically mip maps stored in the 
    84 .tif) 
     84.tiff format) 
    8585via: <br> 
    8686&nbsp;<br> 
     
    1021028) Now its time to run the osgdem example to generate your PagedLOD 
    103103database, the more levels you generate the longer it will take 
    104 (exponentially so), osgdem is just a front end to osgTerrain::DataSet 
     104(exponentially so). 'osgdem' is just a front end to osgTerrain::DataSet 
    105105where all the hard work happens. Here's what to run : <br> 
    106106<br> 
     
    118118&nbsp; -v 0.1 \</span><br style="font-weight: bold;"> 
    119119<span style="font-weight: bold;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    120 -o pegout.ive</span><br> 
     120-o puget.ive</span><br> 
    121121</div> 
    122122<br> 
     
    130130The first part the --xx and --yy is specifying the size of the pixels 
    131131in meters, since these png/tif don't have any geospatial data of their 
    132 own, if you have geospetialised files then you won't need this.<br> 
     132own, if you have geospatialised files then you won't need this.<br> 
    133133<br> 
    134134The second part -t &lt;filename&gt; is the option for specificing the 
    135 texture maps to use, you can use as many as you wish, 
     135texture maps to use, you can use as many times as you wish, 
    136136osgTerrain::DataSet will moziac them into a single database. &nbsp;<br> 
    137137<br> 
    138 The third part -d is the option for specificying the digital elevation 
     138The third part -d is the option for specifying the digital elevation 
    139139maps to use, as with the textures you can use as many as you like. <br> 
    140140&nbsp;<br> 
    141 The -l option specificies the maximum number of levels to generate, if 
     141The -l option specificies the maximum number of levels to generate. If 
    142142you use a large number then the database generation will stop once the 
    143 max resolution of you source data is matched by the outputed database. 
     143max resolution of your source data is matched by the resulting database. 
    144144The database generation will decend further where there is high res 
    145145source 
     
    149149multiplied by.<br> 
    150150<br> 
    151 And finally the -o &lt;filename&gt; is the output format to generat the 
     151And finally the -o &lt;filename&gt; is the output format to generate the 
    152152databases in. This will be the name of the topmost file in the one you 
    153153should load. It can be a .ive or a .osg. The .ive is faster and has 
     
    155155</div> 
    156156<br> 
    157 9) Time to play, simply load the database in your app (make sure it 
    158 support the osgDB::DatabasePager see osgsimplepager 
    159 example for detaiils). The standard osgviewer works just fine so 
     1579) Time to play. Simply load the database in your app (make sure it 
     158supports the osgDB::DatabasePager - see osgsimplepager 
     159example for details). The standard osgviewer works just fine so, 
    160160here goes: <br> 
    161161&nbsp;<br> 
     
    171171here under Linux, so you might be lucky too. <br> 
    172172<br> 
    173 11) If you imagery and dem's have geospatial coords associated with 
    174 them then the -xx, --yy and -v options will not be required making the 
     17311) If your imagery and DEMs have geospatial coords associated with 
     174them then the -xx, --yy and -v options will not be required, making  
    175175it much simplier to specify - you just need to specifiy options such as 
    176176<span style="font-weight: bold;">-t imge.tif</span> and -d terran.dt0 
    177 without any need to set to coordinate system.<br> 
    178 <br> 
    179 12) osgdem can automatically handle moziacing of sets of files, these 
     177without any need to set the coordinate system.<br> 
     178<br> 
     17912) osgdem can automatically handle mosaicing of sets of files. These 
    180180can be specified via a sequence of <span style="font-weight: bold;">-t 
    181181&lt;filename&gt;</span> and <span style="font-weight: bold;">-d