g.region and terraflow

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

g.region and terraflow

Robert Kuszinger
Hi,


it seems that terraflow could handle only and exatly only the situation when

g.region raster=sourcedtm

Is it true?

I tried to script setting g.region to raster and then limit extent changing to a smaller
sub-portion of the image.

Full image: (g.,region raster=....)

projection: 99 (HD72 / EOV)
zone:       0
datum:      towgs84=52.17,-71.82,-14.9,0,0,0,0
ellipsoid:  grs67
north:      370558.27203605
south:      -22830.24409709
west:       409913.84498418
east:       981298.29128666
nsres:      9.99996228
ewres:      10.00007782

rows:       39339
cols:       57138
cells:      2247751782


Partial region:


projection: 99 (HD72 / EOV)
zone:       0
datum:      towgs84=52.17,-71.82,-14.9,0,0,0,0
ellipsoid:  grs67
north:      213209.19577188
south:      193529.27000484
west:       488723.80321904
east:       508433.95660226
nsres:      9.99996228
ewres:      10.00007782

rows:       1968
cols:       1971
cells:      3878928

Is there any hope? Beyond Star Wars IV?

thanks
Robert







_______________________________________________
grass-user mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/grass-user
Reply | Threaded
Open this post in threaded view
|

Re: g.region and terraflow

Mark Seibel
Hi.

Not sure if this is part of the problem, but the g.region " -a "   switch will align the raster and should get rid of the non-square (rectangular) cells.

Mark

_______________________________________________
grass-user mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/grass-user