HTML tags cleaned, sections reorganized

git-svn-id: https://svn.osgeo.org/grass/grass/trunk@31448 15284696-431f-4ddb-bdfa-cd5b030d7da7

raster/r.in.gdal/description.html

@@ -1,9 +1,8 @@
 <h2>DESCRIPTION</h2>
 
 <em>r.in.gdal</em> allows a user to create a (binary) GRASS raster map layer,
-or imagery group,
-from any GDAL supported raster map format, with an optional title.  The
-imported file may also be optionally used to create a new location.
+or imagery group, from any GDAL supported raster map format, with an optional 
+title. The imported file may also be optionally used to create a new location.
 
 <!--<h2>OPTIONS</h2>
 
@@ -18,14 +17,14 @@ are updated.  This will fail if the user doesn't have write access to the
 PERMANENT mapset.
 </dl>-->
 
-<h2>GDAL supported raster formats</h2>
+<h3>GDAL supported raster formats</h3>
 
 Full details on GDAL supported formats are available at:<p>
 
 <a href="http://www.gdal.org/formats_list.html">http://www.gdal.org/formats_list.html</a><p>
 
-Selected formats of more than 45 supported formats:
-<pre>
+Selected formats of more than 80 supported formats:
+<div class="code"><pre>
 
 Long Format Name                                        Code                    Creation        Georeferencing          Maximum File Size
 
@@ -77,20 +76,25 @@ USGS SDTS DEM (*CATD.DDF)                               SDTS
 SAR CEOS                                                SAR_CEOS                No              Yes                     --
 USGS ASCII DEM (.dem)                                   USGSDEM                 No              Yes                     --
 X11 Pixmap (.xpm)                                       XPM                     Yes             No			
-</pre>
-<h2>Location Creation</h2>
+</pre></div>
 
-<b>r.in.gdal</b> attempts to preserve projection information when importing
+<h3>Location Creation</h3>
+
+<em>r.in.gdal</em> attempts to preserve projection information when importing
 datasets if the source format includes projection information, and if
 the GDAL driver supports it.  If the projection of the source dataset does
-not match the projection of the current location <b>r.in.gdal</b> will 
+not match the projection of the current location <em>r.in.gdal</em> will 
 report an error message (<tt>Projection of dataset does not appear to 
 match current location</tt>) and then report the PROJ_INFO parameters of
-the source dataset.<p>
+the source dataset.
+
+<p>
 
 If the user wishes to ignore the difference between the apparent coordinate
 system of the source data and the current location, they may pass the 
-<b>-o</b> flag to override the projection check. <p>
+<b>-o</b> flag to override the projection check. 
+
+<p>
 
 If the user wishes to import the data with the full projection definition,
 it is possible to have r.in.gdal automatically create a new location based
@@ -98,23 +102,28 @@ on the projection and extents of the file being read.  This is accomplished
 by passing the name to be used for the new location via the <b>location</b>
 parameter.  Upon completion of the command, a new location will have been
 created (with only a PERMANENT mapset), and the raster will have been
-imported with the indicated <b>output</b> name into the PERMANENT mapset.<p>
+imported with the indicated <b>output</b> name into the PERMANENT mapset.
+
+<p>
 
 Support for GCPs: In case the image contains GCPs they are written to a
 POINTS file within an imagery group. They can directly be used for 
-<a href=i.rectify.html>i.rectify</a>. The <em>target</em> option allows to
+<a href=i.rectify.html>i.rectify</a>. The <b>target</b> option allows to
 automatically re-project the GCPs from their own projection into another
 projection read from the PROJ_INFO file of the location name
-<em>target</em>.
+<b>target</b>.
 
 <h2>NOTES</h2>
 
-I plan to make a variety of improvements to <b>r.in.gdal</b> in the future
-including support for reporting everything known about a dataset if the 
-<b>output</b> parameter is not set.<p>
+Planned improvements to <em>r.in.gdal</em> in the future include support for
+reporting everything known about a dataset if the <b>output</b> parameter is not set.
+
+<p>
 
-The <b>r.in.gdal</b> comand does support the following features, as long as 
-the underlying format driver supports it:<p>
+The <em>r.in.gdal</em> comand does support the following features, as long as 
+the underlying format driver supports it:
+
+<p>
 
 <dl>
 
@@ -137,7 +146,7 @@ point cell layers (*.real and *.imaginary).<br>
 <dt> Georeferencing
 <dd> If the dataset has affine georeferencing information, this will be used
 to set the north, south, east and west edges.  Rotational coefficients will
-be ignored, resulting in incorrect positioning for rotated datasets.  <br>
+be ignored, resulting in incorrect positioning for rotated datasets.<br>
 
 <dt> Projection
 <dd> The datasets projection will be used to compare to the current location
@@ -164,6 +173,27 @@ the points with i.rectify.<br>
 
 </dl>
 
+<h3>Error Messages</h3>
+
+<i>"ERROR: Input map is rotated - cannot import."</i><br>
+In this case the image must be first externally rotated, applying the rotation info stored in 
+the metadata field of the raster image file. For example, the 
+<a href="http://www.gdal.org/gdal_utilities.html">gdalwarp</a>  software can be used 
+to transform the map to North-up (note, there are several gdalwarp parameters to select the
+resampling algorithm):
+
+<div class="code"><pre>
+gdalwarp rotated.tif northup.tif
+</pre></div>
+
+<p>
+<i>"ERROR: Projection of dataset does not appear to match the current location."</i><br>
+
+You need to create a location whose projection matches the data you
+wish to import. Try using <b>location</b> parameter to create a new location based 
+upon the projection information in the file. If desired, you can then re-project
+it to another location with <em>r.proj</em>.
+
 <h2>EXAMPLES</h2>
 
 <h3>GTOPO30 DEM</h3>
@@ -210,28 +240,6 @@ r.in.gdal HDF4_EOS:EOS_GRID:"MOD15A2.A2003153.h18v04.004.2003171141042.hdf":MOD_
 # ... likewise for other HDF bands in the file.
 </pre></div>
 
-
-<h2>NOTES</h2>
-
-<i>"ERROR: Input map is rotated - cannot import."</i><br>
-In this case the image must be first externally rotated, applying the rotation info stored in 
-the metadata field of the raster image file. For example, the 
-<a href="http://www.gdal.org/gdal_utilities.html">gdalwarp</a>  software can be used 
-to transform the map to North-up (note, there are several gdalwarp parameters to select the
-resampling algorithm):
-
-<div class="code"><pre>
-gdalwarp rotated.tif northup.tif
-</pre></div>
-
-<p>
-<i>"ERROR: Projection of dataset does not appear to match the current location."</i><br>
-
-You need to create a location whose projection matches the data you
-wish to import. Try using <em>location</em> parameter to create a new location based 
-upon the projection information in the file. If desired, you can then re-project
-it to another location with <em>r.proj</em>.
-
 <h2>SEE ALSO</h2>
 <em>
 <a href="r.colors.html">r.colors</a>,
@@ -249,4 +257,4 @@ GDAL Pages: <a href="http://www.gdal.org">http://www.gdal.org/</a><br>
 
 <a href="http://home.gdal.org/warmerda/">Frank Warmerdam</a> (<a href="mailto:warmerdam AT pobox dot com">email</a>).
 
-<p><i>Last changed: $Date$</i>
+<p><i>Last changed: $Date$</i>I