Glynn Clements wrote:
Yan Fitterer wrote:
> First, congratulations for a briliant program.
>
> My problem (is it a bug?):
> I'm getting a gtopo30 file from:
> http://edcdaac.usgs.gov/gtopo30/w020n90.html
>
> The I try to import the .DEM file into Grass with r.in.bin
>
> I get all OK (byte swap, signed integer, etc...) except that at a level of
> about 110 (going up a hill for ex.), the z (altitude) values suddently go to
> -120, and then increase in line with the terrain.
>
> Has anybody seen that behaviour?
>
> I'm running 5.0 beta 11 on Linux RH 7.0 (2.2.16 kernel)I get conflicting results.
If I import it into an x-y location, I seem to get the behaviour which
you describe. OTOH, If I import it into the appropriate lat-lon
location, I don't have any problems (the only areas with negative
altitude are where I would expect, i.e. Holland).NB: I'm running the latest 5.0 CVS, and there's a bug where it ignores
the rows/cols parameters if you specify N/E/S/W (I've fixed this, but
CVS is down right now so I can't commit it).--
Glynn Clements <glynn.clements@virgin.net>----------------------------------------
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo@geog.uni-hannover.de with
subject 'unsubscribe grass5'
I tried sending this a while ago but it was bumped back
----------
Glynn,
I just located and fixed one of the problems with r.in.bin. It was not
reading the rows and cols supplied by the user as reported by Jan.
I was not sure if you had applied a fix to the CVS for the other (?)
reported problem(s). I will hold off applying the above fix until we
have hopefully picked up (and fixed) all problems.
--
Bob Covill
Tekmap Consulting
P.O. Box 2016 Fall River, N.S.
B2T 1K6
Canada
E-Mail: bcovill@tekmap.ns.ca
Phone: 902-860-1496
Fax: 902-860-1498
----------------------------------------
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo@geog.uni-hannover.de with
subject 'unsubscribe grass5'