Maciek wrote:
CREATING SUPPORT FILES FOR N51E016_v1
SETTING GREY COLOR TABLE FOR N51E016_v1 (16bit, image range)
r.in.gdal complete.
WARNING: Your color rules do not cover the whole range of data!
Frank wrote:
I didn't get the message when I tried r.in.srtm. I did make
some changes to signed/unsigned handling in the EHDR
driver which I think is being used in this case. At least
one of the changes I had to change back and I am wondering
if you got an interim version. Could you retry with a GDAL from
CVS (nightly)?
All fine now. Using today's gdal CVS I get correct min/max for the .bil file
created by r.in.srtm:
$ gdalinfo -mm ~/tmp/srtm_v1/N51E016.bil
Driver: EHdr/ESRI .hdr Labelled
<snip>
computed Min/Max=55.000,483.000
NoData Value=-32768
So r.in.srtm works fine again.
The GDAL version which was making r.in.srtm fail like described in the report,
was CVS 2006-01-09.
Thanks Frank.
Closing it.
Maciek
-------------------------------------------- Managed by Request Tracker
On Thu, Feb 09, 2006 at 11:25:43AM +0100, Maciek Sieczka via RT wrote:
Maciek wrote:
>> CREATING SUPPORT FILES FOR N51E016_v1
>> SETTING GREY COLOR TABLE FOR N51E016_v1 (16bit, image range)
>> r.in.gdal complete.
>> WARNING: Your color rules do not cover the whole range of data!
Frank wrote:
> I didn't get the message when I tried r.in.srtm. I did make
> some changes to signed/unsigned handling in the EHDR
> driver which I think is being used in this case. At least
> one of the changes I had to change back and I am wondering
> if you got an interim version. Could you retry with a GDAL from
> CVS (nightly)?
All fine now. Using today's gdal CVS I get correct min/max for the .bil file
created by r.in.srtm:
$ gdalinfo -mm ~/tmp/srtm_v1/N51E016.bil
Driver: EHdr/ESRI .hdr Labelled
<snip>
computed Min/Max=55.000,483.000
NoData Value=-32768
So r.in.srtm works fine again.
The GDAL version which was making r.in.srtm fail like described in the report,
was CVS 2006-01-09.
Thanks Frank.
Closing it.
Maciek
Glad to hear that it works again.
A remark:
This is a nice example where we would benefit from moving the
GRASS code management to a centralized foundation infrastructure
as bug reports could be easily shifted across projects as
well as cross dependencies defined.
Frank is luckily a ver responsive person so that it worked
well in this case - but in future the inter-dependencies will
steadily increase (which is generally good as it improves the
cohesion among the projects and less code replication).
Markus