Cannot read input rasters or write output rasters with unsigned integers 
(16-bit or 32-bit).

The GDAL implementation uses a single data type for all the bands in an output 
raster.  Therefore, if an output raster's pixel class has different sized 
bands, then all the bands are written using the largest data type.  For 
example, if a pixel has two bands, one that is a short (signed 16-bit integer) 
and another that is a float (32-bit single precision), then data for both bands 
are written as float values.

For an input raster, each pixel band must have a data type that is equal to or 
larger than the type of its corresponding raster band.  For example, if the 
raster band is a float, then the corresponding pixel band must be either a 
float or a double (64-bit).  If the pixel band is smaller (e.g., a short), then 
an exception occurs.

Consequently, it is not currently possible to open certain rasters for reading 
with the same pixel class that was used to write them.  It would be much more 
useful for developers to be able to do so.

To support this, the restriction on input pixel bands based on their 
corresponding raster bands must be lifted.  One alternative is to have a type 
conversion delegate for each pixel band.  The delegate would convert the larger 
raster band data into the smaller data type used by the pixel band.  For 
convenience, the default converters would simply do range checking: if the 
raster band data value is within the [min,max] range of the pixel band's data 
type, then return the value (possibly rounded if converting a floating point 
type to an integer type); otherwise, throw some exception.

A developer could specify an explicit conversion method if she wants some other 
action (for example, clipping values outside the pixel band's data type to the 
range limits, so as to avoid any exceptions).

Extract information about the library's design goals from LANDIS-II team
presentations, and add it to the project's wiki.

Add new properties to the Grid base class that return enumerators for the
grid's row numbers and column numbers.

Example:

  IGrid grid = ...
  foreach (int row in grid.RowNumbers) {
    foreach (int column in grid.ColumnNumbers) {
      ...
      // do something with grid[row, column]
      ...
    }
  }

The current API uses the RasterIO.IMetadata interface to access a raster's 
metadata.  The new API needs a new way to provide a raster's metadata that's 
compatible with how GDAL handles metadata.

Developers using the library need API documentation.  Set up doxygen to create 
documentation from comments within the source code.

Import the source code for the raster driver that handles the ERDAS 7.4 GIS and 
LAN formats.

What steps will reproduce the problem?
1. In the svn example, run "LSML-admin distclean" on a Windows system.
2. Then repeat the command again.


What is the expected output? What do you see instead?

Expect that nothing will happen; that the command will simply report that it's 
running, but it won't have any files or directories to delete.  Instead, the 
command downloads the WinPkgTools, and then immediately deletes them.  The 
result is still correct, but the download is unnecessary.

Make sure that each source file has a copyright notice at the top.  Below
is the template for the copyright notice.  The information for the <YEAR>,
<ORIGINAL DEVELOPER>, and <ADDITIONAL CONTRIBUTORS> fields needs to be
extracted from the Subversion logs.

// Copyright <YEAR> University of Wisconsin
// All rights reserved.
//
// The copyright holder licenses this file under the New (3-clause) BSD
// License (the "License").  You may not use this file except in
// compliance with the License.  A copy of the License is available at
//
//   http://www.opensource.org/licenses/bsd-license.php
//
// and is included in the NOTICE.txt file distributed with this work.
//
// Contributors:
//   <ORIGINAL DEVELOPER>, Forest Landscape Ecology Lab, UW-Madison
//   <ADDITIONAL CONTRIBUTORS and their affiliations>

Currently, the gdal branch has only the revised raster I/O module and some 
types from the grids module.  The rest of the grids module as well as the whole 
landscapes module needs to integrated from the trunk.