On Tue, 26 Jan 2010, Glynn Clements wrote:
It's possible that the cropping may have changed the grid slightly.
Glynn, I do hope it's something simple. I can't do more until I have a good DEM map for the project area.
What are the grid parameters (bounds, resolution, rows/cols) for the source map and the cropped version?
Source map (demNW raster map): GRASS 6.4.0svn (Oregon):/usr4/grassbase > g.region rast=demNW -p projection: 99 (Lambert Conformal Conic) zone: 0 datum: nad83 ellipsoid: grs80 north: 1735231.43724681 south: 1120657.1324816 west: 143667.18968253 east: 952979.22944945 nsres: 32.82281055 ewres: 32.82281055 rows: 18724 cols: 24657 cells: 461677668 Resolution in feet. Cropped map (abernethy vector boundary map): GRASS 6.4.0svn (Oregon):/usr4/grassbase > g.region vect=abernethy -p projection: 99 (Lambert Conformal Conic) zone: 0 datum: nad83 ellipsoid: grs80 north: 1334419.25160578 south: 1279151.24118496 west: 769192.9282895 east: 819255.92362222 nsres: 4.99982001 ewres: 4.99979979 rows: 11054 cols: 10013 cells: 110683702 Resolution in metres.
You could try repeating the cropping process, using g.region's align= option to align the grid to the source map.
I'll try this. Thanks, Rich _______________________________________________ grass-user mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/grass-user
