[GRASSLIST:4299] Re: request?

[Ian MacMillan]

Hi David,
Thanks for the response.  I realize that -n lets you not crop the map, 
however it still only projects in information if it is in your current 
region.  What I was hoping for was to be able to set your region based 
on the incoming raster.  For example, if the bounding box for my 
incoming map is 34N 32S 118W 117W in a lat-long location, how would I 
know what the corresponding UTM coordinates are?  I can project it from 
some random place in the UTM location with -n, but it will only bring 
in data if I happened to overlap with the incoming raster.  Do you see 
the dilemma?  What I am looking for is a flag that sets the region to 
the incoming raster.

In addition, I don't think that m.ll2u is included in the 5.7 release.  
I am not sure how one could even project from a lat-long to a utm in 
5.7 if you didn't have the UTM coordinates already (at least with 
minimal effort).

Thanks,
-Ian

PS I hope I am not complaining too much, I love grass, and am amazed at 
all the developers do.  Just wanted to point out an awkward feature, 
and see if I am missing something.


On Sep 3, 2004, at 10:27 AM, mahoneyd at unbc.ca wrote:

> The -n option causes r.proj not to crop the resulting map to the 
> current
> region
>
> Cheers,
>
> David
>
> On Thu, 2 Sep 2004, Ian Macmillan wrote:
>
>> Hi all, I have a request for a feature to be added to r.proj, or if I 
>> am missing
>> something, could somebody tell me?  When you use r.proj, it is 
>> necessary to
>> know the region before hand.  Most times this isn't a problem, but 
>> going from
>> lat-long to utm or vice-versa, this requires the awkward steps of 
>> using m.ll2u
>> or m.u2ll on points you get from r.info, copying this information 
>> down, then
>> setting your region by hand in the new location based on the output 
>> of m.ll2u.
>> This is kind of a non-intuitive method that is difficult for new 
>> people to
>> figure out.  What would be nice is a flag in r.proj to set the region 
>> in the
>> new location based on the bounding coordinates of the raster being 
>> projected
>> in.  Is this solution too difficult to implement?  Unfortunately I 
>> don't know
>> how to code, so I don't think I can do it myself.    Anybody else 
>> have this
>> problem?
>>
>> Thanks,
>> Ian
>>
>