[GRASS-user] Re: grass-user Digest, Vol 29, Issue 5

[Richard Chirgwin]

grass-user-request at lists.osgeo.org wrote:
> Send grass-user mailing list submissions to
> 	grass-user at lists.osgeo.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> 	http://lists.osgeo.org/mailman/listinfo/grass-user
> or, via email, send a message with subject or body 'help' to
> 	grass-user-request at lists.osgeo.org
>
> You can reach the person managing the list at
> 	grass-user-owner at lists.osgeo.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of grass-user digest..."
>
>
> Today's Topics:
>
>    1. Re: BIN raster import (Richard Chirgwin)
>    2. Re: BIN raster import (Hamish)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 03 Sep 2008 17:52:06 +1000
> From: Richard Chirgwin <rchirgwin at ozemail.com.au>
> Subject: Re: [GRASS-user] BIN raster import
> To: hamish_b at yahoo.com, grass-user at lists.osgeo.org
> Message-ID: <48BE4226.20200 at ozemail.com.au>
> Content-Type: text/plain; charset=us-ascii; format=flowed
>
> Hamish wrote:
>   
>>> here's the command:
>>> r.in.bin 'input=/home/richard/Desktop/ausdem.bin' \
>>>   output=RD_Bin bytes=2 rows=13760.5 cols=17361
>>>     
>>>       
>> you can't have half a row of data.
>> rows must be an integer. 
>>
>>
>> Hamish
>>   
>>     
> Ahh - so there's an error in the UI, which says:
> Number of rows: (rows, float, optional)
> Number of columns: (columns, float, optional)
>
> It may be that rows and columns are floating point on the "inside", but 
> the UI should make it clear that integer values are required! I was 
> trying to fiddle the row/column combinations up and down to get the file 
> size right ...
>
> Thanks for the effort, will run in the new version later on (some work 
> to do first), and see what happens.
>
> RC
>   
>>       
>>
>>   
>>     
>
>
> ------------------------------
>
> Message: 2
> Date: Wed, 3 Sep 2008 01:56:09 -0700 (PDT)
> From: Hamish <hamish_b at yahoo.com>
> Subject: Re: [GRASS-user] BIN raster import
> To: grass-user at lists.osgeo.org, Richard Chirgwin
> 	<rchirgwin at ozemail.com.au>
> Message-ID: <815913.44025.qm at web110006.mail.gq1.yahoo.com>
> Content-Type: text/plain; charset=us-ascii
>
> Richard:
>   
>> Ahh - so there's an error in the UI, which says:
>> Number of rows: (rows, float, optional)
>> Number of columns: (columns, float, optional)
>>     
>
> so there is. now fixed in SVN.
>
>   
>> It may be that rows and columns are floating point on the "inside",
>>     
>
> they are really ints on the inside.
>
>   
>> but the UI should make it clear that integer values are required!
>> I was trying to fiddle the row/column combinations up and down to
>> get the file size right ...
>>     
>
> no metadata with it?
> sometimes the cell-center as coord versus grid confluences as coords
> convention can cause the data to be off by 1 row/col from stated size.
>
>
> Hamish
>   
I'll make this suggestion for consideration in a possible future revision.

It would be nice if r.in.bin offered a "create new location" option. 
That way, the import could work byte-by-byte without worrying about 
bounds, and the user could georectify the imported raster to their 
target location after import.

Richard
>
>
>       
>
>
>
> ------------------------------
>
> _______________________________________________
> grass-user mailing list
> grass-user at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/grass-user
>
>
> End of grass-user Digest, Vol 29, Issue 5
> *****************************************
>
>