Sorry my bad. I was still calling MorphToESRI on my cs object before creating
the layer. Everything is working great now.
From: gdal-dev-boun...@lists.osgeo.org [gdal-dev-boun...@lists.osgeo.org] On
Behalf Of Jeremy Palmer
Sent: Monday, 1 October 2012 6:51
Wow Even - thanks for the fix. Your response on this list amazes me.
I just tested creating FileGDB layers for the NZ CS's again. Most of the common
ones now work using the EPSG Id :) However I still get failures on these:
2111PROJCS NZGD_2000_Wanganui_Circuit
2113PROJCS NZGD_2000_Well
Le dimanche 30 septembre 2012 09:52:56, Jeremy Palmer a écrit :
> Hi All,
>
> When creating an Esri FileGDB layer the spatial reference system has to be
> defined using the "Esri" WKT definition. Otherwise you get an "General
> function failure" error.
>
See http://trac.osgeo.org/gdal/ticket/483
Le dimanche 30 septembre 2012 10:20:59, Ari Jolma a écrit :
> After #24948 configure requires --with-python and the simple
>
> ./configure
>
> does not work.
>
> I suggest to change configure.in:3452 to
>
> elif test "x$with_python" != "x" && "$with_python" != "no" ; then
>
> so that non-pytho
After #24948 configure requires --with-python and the simple
./configure
does not work.
I suggest to change configure.in:3452 to
elif test "x$with_python" != "x" && "$with_python" != "no" ; then
so that non-pythoners do not have to be so explicit about not wanting
python.
Cheers,
Ari
___
Hi All,
When creating an Esri FileGDB layer the spatial reference system has to be
defined using the "Esri" WKT definition. Otherwise you get an "General function
failure" error.
In particular the WKT coordinate system code name needs to match the name
within the Esri WKT database which is com
