[GRASSLIST:6241] r.in.bin all nan import GMT grd file.

I'm trying to import some GMT grd files into grass. I think I have done this
successfully a long time (and several versions) ago, but now I can't get it
to work.

r.in.bin -hf seems to work, but all the data is nans. r.info reports:
| Range of data: min = nan max = nan

I know the grd file is not all nans because I can generate plots from it in
GMT.

Any suggestions?

This is grass 6.0 on intel/linux, the same machine generated the grd files.

Regards
Gordon

--

Gordon Keith
Programmer/Data Analyst
Marine Acoustics
CSIRO Marine Research
http://www.marine.csiro.au

There are 10 sorts of people, those who understand binary,
and those who don't.

After more effort (recompiling gdal --with-netcdf) I can now get a raster of
all nans from a normal GMT grid using r.in.gdal as well as from a type 1 grid
using r.in.bin.

In both cases the program runs successfully and correctly gets the region
information from the grid file, but no data.

r.in.gdal thinks the projection is x,y, but it is in fact lat,lon. But i get
the same result using the -o and location= options.

Thoughts?

On Thu, 24 Mar 2005 12:26, Gordon Keith wrote:

I'm trying to import some GMT grd files into grass. I think I have done
this successfully a long time (and several versions) ago, but now I can't
get it to work.

r.in.bin -hf seems to work, but all the data is nans. r.info reports:
| Range of data: min = nan max = nan

I know the grd file is not all nans because I can generate plots from it in
GMT.

Any suggestions?

This is grass 6.0 on intel/linux, the same machine generated the grd files.

Regards
Gordon

--

Gordon Keith
Programmer/Data Analyst
Marine Acoustics
CSIRO Marine Research
http://www.marine.csiro.au

"But what... is it good for?"
- Engineer at Advanced Computing Systems Division of IBM, 1968,
commenting on the role of the microchip.

On Thu, 24 Mar 2005 16:03:25 +1100, Gordon Keith <gordon.keith@csiro.au> wrote:

After more effort (recompiling gdal --with-netcdf) I can now get a raster of
all nans from a normal GMT grid using r.in.gdal as well as from a type 1 grid
using r.in.bin.

In both cases the program runs successfully and correctly gets the region
information from the grid file, but no data.

r.in.gdal thinks the projection is x,y, but it is in fact lat,lon. But i get
the same result using the -o and location= options.

Thoughts?

Gordon,

Is this a file I could take a look at? The netCDF support in GDAL is
still pretty sloppy.

Best regards,
--
---------------------------------------+--------------------------------------
I set the clouds in motion - turn up | Frank Warmerdam, warmerdam@pobox.com
light and sound - activate the windows | http://pobox.com/~warmerdam
and watch the world go round - Rush | Geospatial Programmer for Rent