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

Robert Kuszinger kuszinger at giscom.hu
Fri Dec 30 11:19:34 EST 2005


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




More information about the grass-user mailing list