[gdal-dev] ERROR 6: Failed to initialize PROJ.4 with "..."

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
8 messages Options
Reply | Threaded
Open this post in threaded view
|

[gdal-dev] ERROR 6: Failed to initialize PROJ.4 with "..."

Chris Marsh
Hi,

I'm using GDAL (and by extension proj.4) to reproject a set of WGS84 coordinates to North America Albers Conic Conformal.

On all but 1 computer I run my code on, this works as expected. However, when trying to run on one of Compute Canada's newest machines, I get the error

ERROR 6: Failed to initialize PROJ.4 with `+proj=aea +lat_1=20 +lat_2=60 +lat_0=40 +lon_0=-96 +x_0=0 +y_0=0 +ellps=GRS80 +towgs84=0,0,0,0,0,0,0 +units=m +no_defs'.

I have tried building and linking against various proj.4 versions, none of which solves this problem.

The code  is straightfoward
OGRSpatialReference insrs;
    insrs.SetWellKnownGeogCS("WGS84");

    OGRSpatialReference outsrs;
    outsrs.importFromProj4("+proj=aea +lat_1=20 +lat_2=60 +lat_0=40 +lon_0=-96 +x_0=0 +y_0=0 +ellps=GRS80 +towgs84=0,0,0,0,0,0,0 +units=m +no_defs");

    OGRCoordinateTransformation* coordTrans =  NULL;
    coordTrans = OGRCreateCoordinateTransformation(&insrs, &outsrs);

    coordTrans->Transform(1, &longitude, &latitude)

with the error appearing on the Transform call. The proj.4 string is from using the ExportToWkt of GDAL for the WKT of Albers Conic Conformal. (long story as to why i'm doing this). I have tried using the WKT string and that results in the same error -- seems like it is just converted to proj.4 behind the scenes.

I am using gdal 2.2.1 and proj4 4.8 (4.9 has other issues I'm running into)

$gcc -v
Using built-in specs.
COLLECT_GCC=gcc
Target: x86_64-unknown-linux-gnu
Configured with:
Thread model: posix
gcc version 5.4.0 (GCC)

$uname -a
Linux gra-login4 3.10.0-514.21.1.el7.x86_64 #1 SMP Thu May 25 17:04:51 UTC 2017 x86_64 GNU/Linux

Cheers
Chris


_______________________________________________
gdal-dev mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/gdal-dev
Reply | Threaded
Open this post in threaded view
|

Re: ERROR 6: Failed to initialize PROJ.4 with "..."

Chris Marsh
I was wondering if anyone had thoughts on this? I posted to the proj.4 list, but seems like this may be a gdal problem and not proj.4 as the proj.4 command line has no problem with this string.
I have also tried the  newest gdal without success.
Cheers
Chris

On 12 October 2017 at 11:41, Chris Marsh <[hidden email]> wrote:
Hi,

I'm using GDAL (and by extension proj.4) to reproject a set of WGS84 coordinates to North America Albers Conic Conformal.

On all but 1 computer I run my code on, this works as expected. However, when trying to run on one of Compute Canada's newest machines, I get the error

ERROR 6: Failed to initialize PROJ.4 with `+proj=aea +lat_1=20 +lat_2=60 +lat_0=40 +lon_0=-96 +x_0=0 +y_0=0 +ellps=GRS80 +towgs84=0,0,0,0,0,0,0 +units=m +no_defs'.

I have tried building and linking against various proj.4 versions, none of which solves this problem.

The code  is straightfoward
OGRSpatialReference insrs;
    insrs.SetWellKnownGeogCS("WGS84");

    OGRSpatialReference outsrs;
    outsrs.importFromProj4("+proj=aea +lat_1=20 +lat_2=60 +lat_0=40 +lon_0=-96 +x_0=0 +y_0=0 +ellps=GRS80 +towgs84=0,0,0,0,0,0,0 +units=m +no_defs");

    OGRCoordinateTransformation* coordTrans =  NULL;
    coordTrans = OGRCreateCoordinateTransformation(&insrs, &outsrs);

    coordTrans->Transform(1, &longitude, &latitude)

with the error appearing on the Transform call. The proj.4 string is from using the ExportToWkt of GDAL for the WKT of Albers Conic Conformal. (long story as to why i'm doing this). I have tried using the WKT string and that results in the same error -- seems like it is just converted to proj.4 behind the scenes.

I am using gdal 2.2.1 and proj4 4.8 (4.9 has other issues I'm running into)

$gcc -v
Using built-in specs.
COLLECT_GCC=gcc
Target: x86_64-unknown-linux-gnu
Configured with:
Thread model: posix
gcc version 5.4.0 (GCC)

$uname -a
Linux gra-login4 3.10.0-514.21.1.el7.x86_64 #1 SMP Thu May 25 17:04:51 UTC 2017 x86_64 GNU/Linux

Cheers
Chris



_______________________________________________
gdal-dev mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/gdal-dev
Reply | Threaded
Open this post in threaded view
|

Re: ERROR 6: Failed to initialize PROJ.4 with "..."

Even Rouault-2
On mercredi 18 octobre 2017 10:20:41 CEST Chris Marsh wrote:
> I was wondering if anyone had thoughts on this? I posted to the proj.4
> list, but seems like this may be a gdal problem and not proj.4 as the
> proj.4 command line has no problem with this string.
> I have also tried the  newest gdal without success.

Try building --with-static-proj4 to avoid the issues with the dlopen()'ing of
libproj.so

Check if the following works

echo 2 49 | gdaltransform -s_srs EPSG:4326 -t_srs EPSG:32632


> Cheers
> Chris
>
> On 12 October 2017 at 11:41, Chris Marsh <[hidden email]> wrote:
> > Hi,
> >
> > I'm using GDAL (and by extension proj.4) to reproject a set of WGS84
> > coordinates to North America Albers Conic Conformal.
> >
> > On all but 1 computer I run my code on, this works as expected. However,
> > when trying to run on one of Compute Canada's newest machines, I get the
> > error
> >
> > ERROR 6: Failed to initialize PROJ.4 with `+proj=aea +lat_1=20 +lat_2=60
> > +lat_0=40 +lon_0=-96 +x_0=0 +y_0=0 +ellps=GRS80 +towgs84=0,0,0,0,0,0,0
> > +units=m +no_defs'.
> >
> > I have tried building and linking against various proj.4 versions, none of
> > which solves this problem.
> >
> > The code  is straightfoward
> > OGRSpatialReference insrs;
> >
> >     insrs.SetWellKnownGeogCS("WGS84");
> >    
> >     OGRSpatialReference outsrs;
> >     outsrs.importFromProj4("+proj=aea +lat_1=20 +lat_2=60 +lat_0=40
> >
> > +lon_0=-96 +x_0=0 +y_0=0 +ellps=GRS80 +towgs84=0,0,0,0,0,0,0 +units=m
> > +no_defs");
> >
> >     OGRCoordinateTransformation* coordTrans =  NULL;
> >     coordTrans = OGRCreateCoordinateTransformation(&insrs, &outsrs);
> >    
> >     coordTrans->Transform(1, &longitude, &latitude)
> >
> > with the error appearing on the Transform call. The proj.4 string is from
> > using the ExportToWkt of GDAL for the WKT of Albers Conic Conformal. (long
> > story as to why i'm doing this). I have tried using the WKT string and
> > that
> > results in the same error -- seems like it is just converted to proj.4
> > behind the scenes.
> >
> > I am using gdal 2.2.1 and proj4 4.8 (4.9 has other issues I'm running
> > into)
> >
> > $gcc -v
> > Using built-in specs.
> > COLLECT_GCC=gcc
> > COLLECT_LTO_WRAPPER=/cvmfs/soft.computecanada.ca/nix/store/
> > lvjwgn6hpngyy6k4xqcqa9h2cxy3fl30-gfortran-5.4.0/libexec/gcc/
> > x86_64-unknown-linux-gnu/5.4.0/lto-wrapper
> > Target: x86_64-unknown-linux-gnu
> > Configured with:
> > Thread model: posix
> > gcc version 5.4.0 (GCC)
> >
> > $uname -a
> > Linux gra-login4 3.10.0-514.21.1.el7.x86_64 #1 SMP Thu May 25 17:04:51 UTC
> > 2017 x86_64 GNU/Linux
> >
> > Cheers
> > Chris


--
Spatialys - Geospatial professional services
http://www.spatialys.com
_______________________________________________
gdal-dev mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/gdal-dev
Reply | Threaded
Open this post in threaded view
|

Re: ERROR 6: Failed to initialize PROJ.4 with "..."

Chris Marsh
Hi,

I build GDAL by specifying --with-static-proj4  on the configure command line. This does not seem to have resolved the problem.

echo 2 49 | build-release/lib/gdal/bin/gdaltransform -s_srs EPSG:4326 -t_srs EPSG:32632
-11818.9526229417 5451106.95020125 0

Cheers
Chris

On 18 October 2017 at 12:58, Even Rouault <[hidden email]> wrote:
On mercredi 18 octobre 2017 10:20:41 CEST Chris Marsh wrote:
> I was wondering if anyone had thoughts on this? I posted to the proj.4
> list, but seems like this may be a gdal problem and not proj.4 as the
> proj.4 command line has no problem with this string.
> I have also tried the  newest gdal without success.

Try building --with-static-proj4 to avoid the issues with the dlopen()'ing of
libproj.so

Check if the following works

echo 2 49 | gdaltransform -s_srs EPSG:4326 -t_srs EPSG:32632


> Cheers
> Chris
>
> On 12 October 2017 at 11:41, Chris Marsh <[hidden email]> wrote:
> > Hi,
> >
> > I'm using GDAL (and by extension proj.4) to reproject a set of WGS84
> > coordinates to North America Albers Conic Conformal.
> >
> > On all but 1 computer I run my code on, this works as expected. However,
> > when trying to run on one of Compute Canada's newest machines, I get the
> > error
> >
> > ERROR 6: Failed to initialize PROJ.4 with `+proj=aea +lat_1=20 +lat_2=60
> > +lat_0=40 +lon_0=-96 +x_0=0 +y_0=0 +ellps=GRS80 +towgs84=0,0,0,0,0,0,0
> > +units=m +no_defs'.
> >
> > I have tried building and linking against various proj.4 versions, none of
> > which solves this problem.
> >
> > The code  is straightfoward
> > OGRSpatialReference insrs;
> >
> >     insrs.SetWellKnownGeogCS("WGS84");
> >
> >     OGRSpatialReference outsrs;
> >     outsrs.importFromProj4("+proj=aea +lat_1=20 +lat_2=60 +lat_0=40
> >
> > +lon_0=-96 +x_0=0 +y_0=0 +ellps=GRS80 +towgs84=0,0,0,0,0,0,0 +units=m
> > +no_defs");
> >
> >     OGRCoordinateTransformation* coordTrans =  NULL;
> >     coordTrans = OGRCreateCoordinateTransformation(&insrs, &outsrs);
> >
> >     coordTrans->Transform(1, &longitude, &latitude)
> >
> > with the error appearing on the Transform call. The proj.4 string is from
> > using the ExportToWkt of GDAL for the WKT of Albers Conic Conformal. (long
> > story as to why i'm doing this). I have tried using the WKT string and
> > that
> > results in the same error -- seems like it is just converted to proj.4
> > behind the scenes.
> >
> > I am using gdal 2.2.1 and proj4 4.8 (4.9 has other issues I'm running
> > into)
> >
> > $gcc -v
> > Using built-in specs.
> > COLLECT_GCC=gcc
> > COLLECT_LTO_WRAPPER=/cvmfs/soft.computecanada.ca/nix/store/
> > lvjwgn6hpngyy6k4xqcqa9h2cxy3fl30-gfortran-5.4.0/libexec/gcc/
> > x86_64-unknown-linux-gnu/5.4.0/lto-wrapper
> > Target: x86_64-unknown-linux-gnu
> > Configured with:
> > Thread model: posix
> > gcc version 5.4.0 (GCC)
> >
> > $uname -a
> > Linux gra-login4 3.10.0-514.21.1.el7.x86_64 #1 SMP Thu May 25 17:04:51 UTC
> > 2017 x86_64 GNU/Linux
> >
> > Cheers
> > Chris


--
Spatialys - Geospatial professional services
http://www.spatialys.com


_______________________________________________
gdal-dev mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/gdal-dev
Reply | Threaded
Open this post in threaded view
|

Re: ERROR 6: Failed to initialize PROJ.4 with "..."

Even Rouault-2
On jeudi 19 octobre 2017 13:19:52 CEST Chris Marsh wrote:

> Hi,
>
> I build GDAL by specifying --with-static-proj4  on the configure command
> line. This does not seem to have resolved the problem.
>
> echo 2 49 | build-release/lib/gdal/bin/gdaltransform -s_srs EPSG:4326
>
> > -t_srs EPSG:32632
> > -11818.9526229417 5451106.95020125 0
>

OK, so GDAL and proj.4 have some minimum level of functionnality

And what about

echo 2 49 |  gdaltransform -s_srs EPSG:4326 -t_srs "+proj=aea +lat_1=20 +lat_2=60 +lat_0=40 +lon_0=-96 +x_0=0 +y_0=0 +ellps=GRS80 +towgs84=0,0,0,0,0,0,0 +units=m +no_defs" --debug on



--
Spatialys - Geospatial professional services
http://www.spatialys.com
_______________________________________________
gdal-dev mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/gdal-dev
Reply | Threaded
Open this post in threaded view
|

Re: ERROR 6: Failed to initialize PROJ.4 with "..."

Chris Marsh
echo 2 49 |  /build-release/lib/gdal/bin/gdaltransform -s_srs EPSG:4326 -t_srs "+proj=aea +lat_1=20 +lat_2=60 +lat_0=40 +lon_0=-96 +x_0=0 +y_0=0 +ellps=GRS80 +towgs84=0,0,0,0,0,0,0 +units=m +no_defs" --debug on
OGRCT: PROJ >= 4.8.0 features enabled
OGRCT: Using locale-safe proj version
OGRCT: Source: +proj=longlat +datum=WGS84 +no_defs
OGRCT: Target: +proj=aea +lat_1=20 +lat_2=60 +lat_0=40 +lon_0=-96 +x_0=0 +y_0=0 +ellps=GRS80 +towgs84=0,0,0,0,0,0,0 +units=m +no_defs
OGRCT: Source: +proj=aea +lat_1=20 +lat_2=60 +lat_0=40 +lon_0=-96 +x_0=0 +y_0=0 +ellps=GRS80 +towgs84=0,0,0,0,0,0,0 +units=m +no_defs
OGRCT: Target: +proj=longlat +datum=WGS84 +no_defs
5634252.86902731 4265258.45946341 0



On 19 October 2017 at 13:34, Even Rouault <[hidden email]> wrote:
On jeudi 19 octobre 2017 13:19:52 CEST Chris Marsh wrote:
> Hi,
>
> I build GDAL by specifying --with-static-proj4  on the configure command
> line. This does not seem to have resolved the problem.
>
> echo 2 49 | build-release/lib/gdal/bin/gdaltransform -s_srs EPSG:4326
>
> > -t_srs EPSG:32632
> > -11818.9526229417 5451106.95020125 0
>

OK, so GDAL and proj.4 have some minimum level of functionnality

And what about

echo 2 49 |  gdaltransform -s_srs EPSG:4326 -t_srs "+proj=aea +lat_1=20 +lat_2=60 +lat_0=40 +lon_0=-96 +x_0=0 +y_0=0 +ellps=GRS80 +towgs84=0,0,0,0,0,0,0 +units=m +no_defs" --debug on



--
Spatialys - Geospatial professional services
http://www.spatialys.com


_______________________________________________
gdal-dev mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/gdal-dev
Reply | Threaded
Open this post in threaded view
|

Re: ERROR 6: Failed to initialize PROJ.4 with "..."

Chris Marsh
Hi all,

I posted this to the proj4 mailing list and they seem pretty convinced this is a GDAL problem.

I have tried the September gdal 2.2.2 build as well as the latest GDAL git build, and finally have them building thanks to Even's help.

However, now GDAL just segfaults within the pj_init_ctx. As a reminder, it's something odd about this env as this work works flawlessly on multiple computers.

Would appreciate any help,

Cheers
Chris

[debug]: Reading forcing file data
src/tcmalloc.cc:284] Attempt to free invalid pointer 0x2aaaafa4df20 

Thread 1 received signal SIGABRT, Aborted.
0x00002aaac4900214 in raise () from /cvmfs/soft.computecanada.ca/nix/var/nix/profiles/16.09/lib/libc.so.6
(gdb) bt
#0  0x00002aaac4900214 in raise () from /cvmfs/soft.computecanada.ca/nix/var/nix/profiles/16.09/lib/libc.so.6
#1  0x00002aaac490167a in abort () from /cvmfs/soft.computecanada.ca/nix/var/nix/profiles/16.09/lib/libc.so.6
#2  0x00002aaab5bd5748 in tcmalloc::Log (mode=mode@entry=tcmalloc::kCrash, filename=filename@entry=0x2aaab5bea66e "src/tcmalloc.cc", line=line@entry=284, a=..., b=..., c=..., d=...) at src/internal_logging.cc:118
#3  0x00002aaab5bca14f in (anonymous namespace)::InvalidFree (ptr=<optimized out>) at src/tcmalloc.cc:284
#4  0x00002aaab5fe7dde in pj_dealloc (ptr=<optimized out>) at pj_malloc.c:129
#5  0x00002aaab5fe7ed1 in pj_default_destructor (P=P@entry=0x13c2b40, errlev=errlev@entry=-7) at pj_malloc.c:198
#6  0x00002aaab5fe7234 in pj_init_ctx (ctx=ctx@entry=0x2aaab6219b20 <default_context>, argc=<optimized out>, argv=argv@entry=0x7fffffff7a50) at pj_init.c:672
#7  0x00002aaab5fe7615 in pj_init_plus_ctx (ctx=0x2aaab6219b20 <default_context>, definition=0x24863340 "+proj=aea +lat_1=20 +lat_2=60 +lat_0=40 +lon_0=-96 +x_0=0 +y_0=0 +ellps=GRS80 +datum=NAD83 +units=m +no_defs ")
    at pj_init.c:411
#8  0x00002aaab4a71dc8 in OCTProj4NormalizeInternal(char const*) () from /home/cmarsh/CHM/build-release/lib/gdal/lib/libgdal.so.20
#9  0x00002aaab4a71ee6 in OCTProj4Normalize () from /home/cmarsh/CHM/build-release/lib/gdal/lib/libgdal.so.20
#10 0x00002aaab4a530ec in OGRSpatialReference::importFromProj4(char const*) () from /home/cmarsh/CHM/build-release/lib/gdal/lib/libgdal.so.20
#11 0x0000000000520a61 in core::config_forcing (this=this@entry=0x7fffffffab50, value=...) at /home/cmarsh/CHM/src/core.cpp:311
#12 0x0000000000527041 in core::init (this=this@entry=0x7fffffffab50, argc=argc@entry=3, argv=argv@entry=0x7fffffffafe8) at /home/cmarsh/CHM/src/core.cpp:1119
#13 0x00000000004f502f in main (argc=3, argv=0x7fffffffafe8) at /home/cmarsh/CHM/src/main.cpp:17


Chris Marsh
PhD Candidate
chrismarsh.ca

121 Research Drive
University of Saskatchewan

On 19 October 2017 at 13:41, Chris Marsh <[hidden email]> wrote:
echo 2 49 |  /build-release/lib/gdal/bin/gdaltransform -s_srs EPSG:4326 -t_srs "+proj=aea +lat_1=20 +lat_2=60 +lat_0=40 +lon_0=-96 +x_0=0 +y_0=0 +ellps=GRS80 +towgs84=0,0,0,0,0,0,0 +units=m +no_defs" --debug on
OGRCT: PROJ >= 4.8.0 features enabled
OGRCT: Using locale-safe proj version
OGRCT: Source: +proj=longlat +datum=WGS84 +no_defs
OGRCT: Target: +proj=aea +lat_1=20 +lat_2=60 +lat_0=40 +lon_0=-96 +x_0=0 +y_0=0 +ellps=GRS80 +towgs84=0,0,0,0,0,0,0 +units=m +no_defs
OGRCT: Source: +proj=aea +lat_1=20 +lat_2=60 +lat_0=40 +lon_0=-96 +x_0=0 +y_0=0 +ellps=GRS80 +towgs84=0,0,0,0,0,0,0 +units=m +no_defs
OGRCT: Target: +proj=longlat +datum=WGS84 +no_defs
5634252.86902731 4265258.45946341 0



On 19 October 2017 at 13:34, Even Rouault <[hidden email]> wrote:
On jeudi 19 octobre 2017 13:19:52 CEST Chris Marsh wrote:
> Hi,
>
> I build GDAL by specifying --with-static-proj4  on the configure command
> line. This does not seem to have resolved the problem.
>
> echo 2 49 | build-release/lib/gdal/bin/gdaltransform -s_srs EPSG:4326
>
> > -t_srs EPSG:32632
> > -11818.9526229417 5451106.95020125 0
>

OK, so GDAL and proj.4 have some minimum level of functionnality

And what about

echo 2 49 |  gdaltransform -s_srs EPSG:4326 -t_srs "+proj=aea +lat_1=20 +lat_2=60 +lat_0=40 +lon_0=-96 +x_0=0 +y_0=0 +ellps=GRS80 +towgs84=0,0,0,0,0,0,0 +units=m +no_defs" --debug on



--
Spatialys - Geospatial professional services
http://www.spatialys.com



_______________________________________________
gdal-dev mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/gdal-dev
Reply | Threaded
Open this post in threaded view
|

Re: ERROR 6: Failed to initialize PROJ.4 with "..."

Chris Marsh
To close the loop on this, it was a name conflict with the proj4 that is in VTK
Details here:

Thanks everyone for their help
Cheers
Chris


On 28 October 2017 at 11:26, Chris Marsh <[hidden email]> wrote:
Hi all,

I posted this to the proj4 mailing list and they seem pretty convinced this is a GDAL problem.

I have tried the September gdal 2.2.2 build as well as the latest GDAL git build, and finally have them building thanks to Even's help.

However, now GDAL just segfaults within the pj_init_ctx. As a reminder, it's something odd about this env as this work works flawlessly on multiple computers.

Would appreciate any help,

Cheers
Chris

[debug]: Reading forcing file data
src/tcmalloc.cc:284] Attempt to free invalid pointer 0x2aaaafa4df20 

Thread 1 received signal SIGABRT, Aborted.
0x00002aaac4900214 in raise () from /cvmfs/soft.computecanada.ca/nix/var/nix/profiles/16.09/lib/libc.so.6
(gdb) bt
#0  0x00002aaac4900214 in raise () from /cvmfs/soft.computecanada.ca/nix/var/nix/profiles/16.09/lib/libc.so.6
#1  0x00002aaac490167a in abort () from /cvmfs/soft.computecanada.ca/nix/var/nix/profiles/16.09/lib/libc.so.6
#2  0x00002aaab5bd5748 in tcmalloc::Log (mode=mode@entry=tcmalloc::kCrash, filename=filename@entry=0x2aaab5bea66e "src/tcmalloc.cc", line=line@entry=284, a=..., b=..., c=..., d=...) at src/internal_logging.cc:118
#3  0x00002aaab5bca14f in (anonymous namespace)::InvalidFree (ptr=<optimized out>) at src/tcmalloc.cc:284
#4  0x00002aaab5fe7dde in pj_dealloc (ptr=<optimized out>) at pj_malloc.c:129
#5  0x00002aaab5fe7ed1 in pj_default_destructor (P=P@entry=0x13c2b40, errlev=errlev@entry=-7) at pj_malloc.c:198
#6  0x00002aaab5fe7234 in pj_init_ctx (ctx=ctx@entry=0x2aaab6219b20 <default_context>, argc=<optimized out>, argv=argv@entry=0x7fffffff7a50) at pj_init.c:672
#7  0x00002aaab5fe7615 in pj_init_plus_ctx (ctx=0x2aaab6219b20 <default_context>, definition=0x24863340 "+proj=aea +lat_1=20 +lat_2=60 +lat_0=40 +lon_0=-96 +x_0=0 +y_0=0 +ellps=GRS80 +datum=NAD83 +units=m +no_defs ")
    at pj_init.c:411
#8  0x00002aaab4a71dc8 in OCTProj4NormalizeInternal(char const*) () from /home/cmarsh/CHM/build-release/lib/gdal/lib/libgdal.so.20
#9  0x00002aaab4a71ee6 in OCTProj4Normalize () from /home/cmarsh/CHM/build-release/lib/gdal/lib/libgdal.so.20
#10 0x00002aaab4a530ec in OGRSpatialReference::importFromProj4(char const*) () from /home/cmarsh/CHM/build-release/lib/gdal/lib/libgdal.so.20
#11 0x0000000000520a61 in core::config_forcing (this=this@entry=0x7fffffffab50, value=...) at /home/cmarsh/CHM/src/core.cpp:311
#12 0x0000000000527041 in core::init (this=this@entry=0x7fffffffab50, argc=argc@entry=3, argv=argv@entry=0x7fffffffafe8) at /home/cmarsh/CHM/src/core.cpp:1119
#13 0x00000000004f502f in main (argc=3, argv=0x7fffffffafe8) at /home/cmarsh/CHM/src/main.cpp:17


Chris Marsh
PhD Candidate
chrismarsh.ca

121 Research Drive
University of Saskatchewan

On 19 October 2017 at 13:41, Chris Marsh <[hidden email]> wrote:
echo 2 49 |  /build-release/lib/gdal/bin/gdaltransform -s_srs EPSG:4326 -t_srs "+proj=aea +lat_1=20 +lat_2=60 +lat_0=40 +lon_0=-96 +x_0=0 +y_0=0 +ellps=GRS80 +towgs84=0,0,0,0,0,0,0 +units=m +no_defs" --debug on
OGRCT: PROJ >= 4.8.0 features enabled
OGRCT: Using locale-safe proj version
OGRCT: Source: +proj=longlat +datum=WGS84 +no_defs
OGRCT: Target: +proj=aea +lat_1=20 +lat_2=60 +lat_0=40 +lon_0=-96 +x_0=0 +y_0=0 +ellps=GRS80 +towgs84=0,0,0,0,0,0,0 +units=m +no_defs
OGRCT: Source: +proj=aea +lat_1=20 +lat_2=60 +lat_0=40 +lon_0=-96 +x_0=0 +y_0=0 +ellps=GRS80 +towgs84=0,0,0,0,0,0,0 +units=m +no_defs
OGRCT: Target: +proj=longlat +datum=WGS84 +no_defs
5634252.86902731 4265258.45946341 0



On 19 October 2017 at 13:34, Even Rouault <[hidden email]> wrote:
On jeudi 19 octobre 2017 13:19:52 CEST Chris Marsh wrote:
> Hi,
>
> I build GDAL by specifying --with-static-proj4  on the configure command
> line. This does not seem to have resolved the problem.
>
> echo 2 49 | build-release/lib/gdal/bin/gdaltransform -s_srs EPSG:4326
>
> > -t_srs EPSG:32632
> > -11818.9526229417 5451106.95020125 0
>

OK, so GDAL and proj.4 have some minimum level of functionnality

And what about

echo 2 49 |  gdaltransform -s_srs EPSG:4326 -t_srs "+proj=aea +lat_1=20 +lat_2=60 +lat_0=40 +lon_0=-96 +x_0=0 +y_0=0 +ellps=GRS80 +towgs84=0,0,0,0,0,0,0 +units=m +no_defs" --debug on



--
Spatialys - Geospatial professional services
http://www.spatialys.com




_______________________________________________
gdal-dev mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/gdal-dev