[GRASSLIST:9683] Re: r.proj - painfully slow or bug? (Cygwin, latest 6.1 CVS)

[Ian MacMillan]

Robert, you want to make sure that your region in the target location 
is set to the same size as the raster coming in.  If your region is 
bigger than the raster, then that blank space needs to get interpolated 
as well.  The easy way to do this is to create a vector of the region 
you want to project with v.in.region in the original location.  Project 
that into your target location with v.proj (usually an ~instantaneous 
projection) run from the target location.  Set your region in the 
target location to that raster, g.region vect=projected_vector.  You 
might need to change the resolution manually.  Then run r.proj.

Hopefully this helps,
-Ian




On Dec 30, 2005, at 8:19 AM, Robert Kuszinger wrote:

>
> Hello!
>
> Is it normal that r.proj is running for an hour on a 9M raster data
> (from UTM to EPSG:23700) with nearest neighbour?
> Grayscale DTM.
>
> I don't know if it is working at all or simply frozen or buggy?
>
>
> I'm running Grass61 in Cygwin on a 1.4 MHz Pentium M Dothan with 1GB 
> RAM (IBM TP R51)
>
> Where to check for temporary files or how to get a progress 
> information?
>
>
> It displays this (see between lines), processor is running at 100% and 
> nothing else happens....
>
> -----------------------
> GRASS 6.1.cvs (magyarorszag):/cygdrive/m/grass > r.proj input=dk_cut 
> location=latlong resolution=100
>
> Input Projection Parameters: +proj=latlong +no_defs +a=6378137 
> +rf=298.257223563 +towgs84=0.000,0.000,0.000
> Input Unit Factor: 1
>
> Output Projection Parameters: +proj=somerc +lat_0=47.14439372222222 
> +lon_0=19.04857177777778 +x_0=650000 +y_0=200000 +no_defs +a=6378160 
> +rf=298.247167427
> Output Unit Factor: 1
> -----------------------------
>
>
> thanks
>
> Robert
>


-------------------------------------------------------------
This message has been scanned by Postini anti-virus software.