[GRASS-user] g.region Options Yield Different Values

[Rich Shepard]

On Sun, 22 Nov 2009, Glynn Clements wrote:

> In particular, if you have *raster* data in an LCC projection, you need to
> know its bounds in LCC, otherwise you don't really have any data, just an
> array of numbers.

   I want to re-do the layers so they're all correct. Starting with the DEM,
here's the information from the metadata file:

Spatial_Domain:
   Bounding_Coordinates:
     West_Bounding_Coordinate: -124.896200
     East_Bounding_Coordinate: -117.01801421
     North_Bounding_Coordinate: 46.14636144
     South_Bounding_Coordinate: 41.629424

Spatial_Reference_Information:
   Horizontal_Coordinate_System_Definition:
     Planar:
       Map_Projection:
         Map_Projection_Name: Lambert Conformal Conic
         Lambert_Conformal_Conic:
           Standard_Parallel: 43.000000
           Standard_Parallel: 45.500000
           Longitude_of_Central_Meridian: -120.500000
           Latitude_of_Projection_Origin: 41.750000
           False_Easting: 1312336.000000
           False_Northing: 0.000000
         Planar_Coordinate_Information:
           Planar_Coordinate_Encoding_Method: row and column
           Coordinate_Representation:
             Abscissa_Resolution: 32.828670
             Ordinate_Resolution: 32.828670
           Planar_Distance_Units: User_Defined_Unit
         Geodetic_Model:
           Horizontal_Datum_Name: North American Datum of 1983
           Ellipsoid_Name: Geodetic Reference System 80
           Semi-major_Axis: 6378137.000000
           Denominator_of_Flattening_Ratio: 298.257222

   If I correctly understand what you wrote above, I use the projection
information when importing the data, but leave the bounds undefined. Once
the import is completed I can then run 'g.region rast=elevation10' to set
the bounds in appropriate units. Is this correct?

Rich