On Friday 16 November 2007, Boris Avdeev wrote: > Now, when you asking... > Now it is this: > > projection: 3 (Latitude-Longitude) > zone: 0 > datum: wgs84 > ellipsoid: wgs84 > north: 48:50:24.701676N > south: 34:38:56.353164N > west: 45:57:00.735336E > east: 55:00:56.276712E > nsres: 0:01:00.033312 > ewres: 0:00:59.991804 > rows: 851 > cols: 544 > cells: 462944 > > But I believe that at the time I started r.patch it was this: > > projection: 3 (Latitude-Longitude) > zone: 0 > datum: wgs84 > ellipsoid: wgs84 > north: 46N > south: 35N > west: 35E > east: 55E > nsres: 0:00:03 > ewres: 0:00:03 > rows: 13200 > cols: 24000 > cells: 316800000 > > since I was trying to preserve resolution of original srtms. > > Boris >
That is pretty big, but not impossibly big. Have you considered something like gdal_merge.py for merging the files outside of GRASS ? cheers, Dylan > > PS Sorry Dylan > > On Nov 16, 2007 12:49 PM, Dylan Beaudette <[EMAIL PROTECTED]> wrote: > > On Friday 16 November 2007, Boris Avdeev wrote: > > > Hello grass (ab)users! > > > I am using r.patch to merge 200 1 degree, 3 seconds resolution srtm's > > > (1-2 Mb each). After 24 hours of real time and 20 hours of Xeon > > > processor time I have 39% completed! My guess that this task shouldn't > > > take so long. Is r.patch a wrong tool to do this thing? Or is it a > > > bug? I am using grass-6.3.cvs. > > > > > > Thanks, > > > Boris > > > > check region extents and resolution ... can you send the output from > > g.region -p ? > > > > Dylan > > > > > > -- > > Dylan Beaudette > > Soil Resource Laboratory > > http://casoilresource.lawr.ucdavis.edu/ > > University of California at Davis > > 530.754.7341 -- Dylan Beaudette Soil Resource Laboratory http://casoilresource.lawr.ucdavis.edu/ University of California at Davis 530.754.7341 _______________________________________________ grass-user mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/grass-user
