RE: [GRASS5] r.in.gdal

Don't forget also the optimization trick, if you haven't
tried it already.

CFLAGS=-g ./configure ...

configure grass as normal and then re-compile r.in.gdal.
(I would assume you can rebuild only r.in.gdal with
gmake.)

This has fixed at least 2 other user's r.in.gdal (maybe),
one of whom was running Redhat 8.0.

My theory is that for Redhat >7, optimization is breaking
r.in.gdal.

Please let us know if you have tried this already or if it works.

John

-----Original Message-----
From: Bernhard Reiter [mailto:bernhard@intevation.de]
Sent: Monday, January 26, 2004 11:56 AM
To: grass-dev
Subject: Re: [GRASS5] r.in.gdal

On Mon, Jan 26, 2004 at 10:10:41AM -0600, Tom Parker wrote:
> I'm trying to resolve the r.in.gdal segmentation fault
mentioned several
> times on the mailing list over the past year. The problem
shows itself no
> matter what type of raster file I try and import.
>
> My sytem is redhat 9 with gdal/proj/grass all built from CVS.
>
> After installing and/or building and installing several
versions of both
> grass and gdal as binaries or built from source the problem
isn't fixed. If
> there is a simple fix I'd love to know it or I'd be happy
to try and help
> fix the problem.

Can you build with debugging support and try
to see what the traceback says?

Check: http://grass.itc.it/grassdevel.html
for links to the "debugging" hints

Are there any versions you didn't build yourself?
  Bernhard

I tried the 5.3 update with no luck, I'm going to switch to an older gdal
not the latest from cvs and see if that helps the 5.3 r.in.gdal patch.

-----Original Message-----
From: John Gillette [mailto:JGillette@rfmd.com]
Sent: Monday, January 26, 2004 11:55 AM
To: grass-dev; Tom Parker
Subject: RE: [GRASS5] r.in.gdal

Don't forget also the optimization trick, if you haven't
tried it already.

CFLAGS=-g ./configure ...

configure grass as normal and then re-compile r.in.gdal.
(I would assume you can rebuild only r.in.gdal with
gmake.)

This has fixed at least 2 other user's r.in.gdal (maybe),
one of whom was running Redhat 8.0.

My theory is that for Redhat >7, optimization is breaking
r.in.gdal.

Please let us know if you have tried this already or if it works.

John

-----Original Message-----
From: Bernhard Reiter [mailto:bernhard@intevation.de]
Sent: Monday, January 26, 2004 11:56 AM
To: grass-dev
Subject: Re: [GRASS5] r.in.gdal

On Mon, Jan 26, 2004 at 10:10:41AM -0600, Tom Parker wrote:
> I'm trying to resolve the r.in.gdal segmentation fault
mentioned several
> times on the mailing list over the past year. The problem
shows itself no
> matter what type of raster file I try and import.
>
> My sytem is redhat 9 with gdal/proj/grass all built from CVS.
>
> After installing and/or building and installing several
versions of both
> grass and gdal as binaries or built from source the problem
isn't fixed. If
> there is a simple fix I'd love to know it or I'd be happy
to try and help
> fix the problem.

Can you build with debugging support and try
to see what the traceback says?

Check: http://grass.itc.it/grassdevel.html
for links to the "debugging" hints

Are there any versions you didn't build yourself?
  Bernhard

On Mon, Jan 26, 2004 at 01:11:11PM -0600, Tom Parker wrote:

I tried the 5.3 update with no luck, I'm going to switch to an older gdal
not the latest from cvs and see if that helps the 5.3 r.in.gdal patch.

Could you post the dataset in question somewhere? Then we could try
to replicate the problem.

Markus

-----Original Message-----
From: John Gillette [mailto:JGillette@rfmd.com]
Sent: Monday, January 26, 2004 11:55 AM
To: grass-dev; Tom Parker
Subject: RE: [GRASS5] r.in.gdal

Don't forget also the optimization trick, if you haven't
tried it already.

CFLAGS=-g ./configure ...

configure grass as normal and then re-compile r.in.gdal.
(I would assume you can rebuild only r.in.gdal with
gmake.)

This has fixed at least 2 other user's r.in.gdal (maybe),
one of whom was running Redhat 8.0.

My theory is that for Redhat >7, optimization is breaking
r.in.gdal.

Please let us know if you have tried this already or if it works.

John

> -----Original Message-----
> From: Bernhard Reiter [mailto:bernhard@intevation.de]
> Sent: Monday, January 26, 2004 11:56 AM
> To: grass-dev
> Subject: Re: [GRASS5] r.in.gdal
>
>
> On Mon, Jan 26, 2004 at 10:10:41AM -0600, Tom Parker wrote:
> > I'm trying to resolve the r.in.gdal segmentation fault
> mentioned several
> > times on the mailing list over the past year. The problem
> shows itself no
> > matter what type of raster file I try and import.
> >
> > My sytem is redhat 9 with gdal/proj/grass all built from CVS.
> >
> > After installing and/or building and installing several
> versions of both
> > grass and gdal as binaries or built from source the problem
> isn't fixed. If
> > there is a simple fix I'd love to know it or I'd be happy
> to try and help
> > fix the problem.
>
> Can you build with debugging support and try
> to see what the traceback says?
>
> Check: http://grass.itc.it/grassdevel.html
> for links to the "debugging" hints
>
> Are there any versions you didn't build yourself?
> Bernhard
>

_______________________________________________
grass5 mailing list
grass5@grass.itc.it
http://grass.itc.it/mailman/listinfo/grass5

I will, I'm still trying to fix it myself but if I fail I'll certainly ask
for more help :slight_smile:

-----Original Message-----
From: grass5-admin@grass.itc.it [mailto:grass5-admin@grass.itc.it]On
Behalf Of Markus Neteler
Sent: Monday, January 26, 2004 3:47 PM
To: grass-dev
Subject: Re: [GRASS5] r.in.gdal

On Mon, Jan 26, 2004 at 01:11:11PM -0600, Tom Parker wrote:

I tried the 5.3 update with no luck, I'm going to switch to an older gdal
not the latest from cvs and see if that helps the 5.3 r.in.gdal patch.

Could you post the dataset in question somewhere? Then we could try
to replicate the problem.

Markus

-----Original Message-----
From: John Gillette [mailto:JGillette@rfmd.com]
Sent: Monday, January 26, 2004 11:55 AM
To: grass-dev; Tom Parker
Subject: RE: [GRASS5] r.in.gdal

Don't forget also the optimization trick, if you haven't
tried it already.

CFLAGS=-g ./configure ...

configure grass as normal and then re-compile r.in.gdal.
(I would assume you can rebuild only r.in.gdal with
gmake.)

This has fixed at least 2 other user's r.in.gdal (maybe),
one of whom was running Redhat 8.0.

My theory is that for Redhat >7, optimization is breaking
r.in.gdal.

Please let us know if you have tried this already or if it works.

John

> -----Original Message-----
> From: Bernhard Reiter [mailto:bernhard@intevation.de]
> Sent: Monday, January 26, 2004 11:56 AM
> To: grass-dev
> Subject: Re: [GRASS5] r.in.gdal
>
>
> On Mon, Jan 26, 2004 at 10:10:41AM -0600, Tom Parker wrote:
> > I'm trying to resolve the r.in.gdal segmentation fault
> mentioned several
> > times on the mailing list over the past year. The problem
> shows itself no
> > matter what type of raster file I try and import.
> >
> > My sytem is redhat 9 with gdal/proj/grass all built from CVS.
> >
> > After installing and/or building and installing several
> versions of both
> > grass and gdal as binaries or built from source the problem
> isn't fixed. If
> > there is a simple fix I'd love to know it or I'd be happy
> to try and help
> > fix the problem.
>
> Can you build with debugging support and try
> to see what the traceback says?
>
> Check: http://grass.itc.it/grassdevel.html
> for links to the "debugging" hints
>
> Are there any versions you didn't build yourself?
> Bernhard
>

_______________________________________________
grass5 mailing list
grass5@grass.itc.it
http://grass.itc.it/mailman/listinfo/grass5

_______________________________________________
grass5 mailing list
grass5@grass.itc.it
http://grass.itc.it/mailman/listinfo/grass5

Hallelujah, it works.

proj-4.4.7
gdal-1.1.9
grass-5.3-cvs

seem to play nicely together.

I'm guessing the problem with the CVS version of gdal is related to a
problem I asked the gdal-dev list about last week. My C++ file readers that
depend on gdal/ogr/proj were reporting these errors in the console window.

ERROR 1: failed to load NAD27-83 correction file
...
ERROR 1: failed to load NAD27-83 correction file
ERROR 1: Reprojection failed, err = -38, further errors will be suppressed
on the transform object.

SO, I think that since I have been setting up my grass builds with this
configure command.

configure --without-postgres --without-odbc --without-fftw --with-gdal --wit
h-proj

It is failing to load the NAD27-83 correction file in r.in.gdal as well. My
initial attempts were just to add printf statements into main.c in the
r.in.gdal folder but that was less than helpful.

I will study the debugging hints now to see if I can be more helpful in the
future.

Thanks again.
Tom

-----Original Message-----
From: grass5-admin@grass.itc.it [mailto:grass5-admin@grass.itc.it]On
Behalf Of Tom Parker
Sent: Monday, January 26, 2004 4:03 PM
To: grass-dev
Subject: RE: [GRASS5] r.in.gdal

I will, I'm still trying to fix it myself but if I fail I'll certainly ask
for more help :slight_smile:

-----Original Message-----
From: grass5-admin@grass.itc.it [mailto:grass5-admin@grass.itc.it]On
Behalf Of Markus Neteler
Sent: Monday, January 26, 2004 3:47 PM
To: grass-dev
Subject: Re: [GRASS5] r.in.gdal

On Mon, Jan 26, 2004 at 01:11:11PM -0600, Tom Parker wrote:

I tried the 5.3 update with no luck, I'm going to switch to an older gdal
not the latest from cvs and see if that helps the 5.3 r.in.gdal patch.

Could you post the dataset in question somewhere? Then we could try
to replicate the problem.

Markus

-----Original Message-----
From: John Gillette [mailto:JGillette@rfmd.com]
Sent: Monday, January 26, 2004 11:55 AM
To: grass-dev; Tom Parker
Subject: RE: [GRASS5] r.in.gdal

Don't forget also the optimization trick, if you haven't
tried it already.

CFLAGS=-g ./configure ...

configure grass as normal and then re-compile r.in.gdal.
(I would assume you can rebuild only r.in.gdal with
gmake.)

This has fixed at least 2 other user's r.in.gdal (maybe),
one of whom was running Redhat 8.0.

My theory is that for Redhat >7, optimization is breaking
r.in.gdal.

Please let us know if you have tried this already or if it works.

John

> -----Original Message-----
> From: Bernhard Reiter [mailto:bernhard@intevation.de]
> Sent: Monday, January 26, 2004 11:56 AM
> To: grass-dev
> Subject: Re: [GRASS5] r.in.gdal
>
>
> On Mon, Jan 26, 2004 at 10:10:41AM -0600, Tom Parker wrote:
> > I'm trying to resolve the r.in.gdal segmentation fault
> mentioned several
> > times on the mailing list over the past year. The problem
> shows itself no
> > matter what type of raster file I try and import.
> >
> > My sytem is redhat 9 with gdal/proj/grass all built from CVS.
> >
> > After installing and/or building and installing several
> versions of both
> > grass and gdal as binaries or built from source the problem
> isn't fixed. If
> > there is a simple fix I'd love to know it or I'd be happy
> to try and help
> > fix the problem.
>
> Can you build with debugging support and try
> to see what the traceback says?
>
> Check: http://grass.itc.it/grassdevel.html
> for links to the "debugging" hints
>
> Are there any versions you didn't build yourself?
> Bernhard
>

_______________________________________________
grass5 mailing list
grass5@grass.itc.it
http://grass.itc.it/mailman/listinfo/grass5

_______________________________________________
grass5 mailing list
grass5@grass.itc.it
http://grass.itc.it/mailman/listinfo/grass5

_______________________________________________
grass5 mailing list
grass5@grass.itc.it
http://grass.itc.it/mailman/listinfo/grass5

On Mon, Jan 26, 2004 at 04:22:15PM -0600, Tom Parker wrote:

Hallelujah, it works.

proj-4.4.7
gdal-1.1.9
grass-5.3-cvs

seem to play nicely together.

I'm guessing the problem with the CVS version of gdal is related to a
problem I asked the gdal-dev list about last week. My C++ file readers that
depend on gdal/ogr/proj were reporting these errors in the console window.

ERROR 1: failed to load NAD27-83 correction file
...
ERROR 1: failed to load NAD27-83 correction file
ERROR 1: Reprojection failed, err = -38, further errors will be suppressed
on the transform object.

SO, I think that since I have been setting up my grass builds with this
configure command.

configure --without-postgres --without-odbc --without-fftw --with-gdal --wit
h-proj

It is failing to load the NAD27-83 correction file in r.in.gdal as well. My
initial attempts were just to add printf statements into main.c in the
r.in.gdal folder but that was less than helpful.

I will study the debugging hints now to see if I can be more helpful in the
future.

Did you install the NAD27-83 correction files?
See
http://www.remotesensing.org/proj/faq.html
"How do I build/configure PROJ.4 to support datum shifting.
After downloading and unpacking the PROJ.4 source, also download and unpack the set of datum shift files. This would be a file like ftp://ftp.remotesensing.org/pub/proj/proj-nad27-1.1.tar.gz. This file should be unpacked within the proj/nad directory. Then proceed with the configuration, build and install. This will ensure that the build system knows about the grid shift files, and applies the ascii to binary preprocessing step.

How do I debug problems with NAD27/NAD83 datum shifting?
...
The PROJ_DEBUG environment can be defined (any value) to force extra output from the PROJ.4 library to stderr...
"

Once I had the same problem and installation of proj-nad27-1.1.tar.gz
helped together with recompilation of PROJ4.

Markus