[GRASSLIST:141] Re: Considering replacing ESRI

[David Finlayson]

That is similar to what I eventually did, though I hesitate to admit 
that I dumped the grid from Grass, did the rotation in ArcInfo and then 
brought it back into Grass for my final processing.

The problem with this approach is that my program can only be ported to 
another user if they have all of the dependent programs (ArcInfo in this 
case, or the Gimp, or Image magic etc).

I think that this is the unspoken down side to the Unix paradigm.  You 
wind up with this spaghetti of dependencies that make it impossible to 
hand a script over to a buddy on their machine.

It would be better if I learned enough C to get my rotation program 
added to Grass.  Or better yet, write a Python interface to the C API so 
that I could read and write to the rasters directly from Python!

Cheers,

David Finlayson

Morten Hulden wrote:
> On Thu, 22 May 2003, David Finlayson wrote:
> 
> 
>>I don't think that grass can rotate rasters (ESRI can).
>>
>>I tried to get around this a few months ago by writing a Python script 
>>that did the work. Unfortunately, it isn't very efficient and can take 
>>20 mins or so to rotate large grids. If you are interested I can send 
>>you the script.
> 
> 
> Consider that after rotation the projection would no longer be what it 
> was. So the new raster would have to be stored in a new (XY) location.
> 
> Why not simply export tif/png, rotate with Gimp or other external image 
> handler, reimport into XY-location?
> 
> 

-- 
David Finlayson
School of Oceanography
Box 357940
University of Washington
Seattle, WA  98195-7940
USA

Office: Marine Sciences Building, Room 112
Phone: (206) 616-9407
Web: http://students.washington.edu/dfinlays