AFAICT, the issue is not so much that the FileGDB only supports certain
projections, but that it only accepts a very specific WKT string for a
given SRS. A single character of difference can cause the FileGDB API to
not recognise the SRS, then fall back to a "General function failure".
GDAL/OG
Stacey,
You should not need to use cs2cs - pretty much the same capabilities
are available from the ogr2ogr command line. What command are you
using now? And what version of GDAL/OGR? With modern versions the
following command should work well:
ogr2ogr -s_srs EPSG:3857 -t_srs EPSG:4326 out.s
Hi list,
I'm trying to compile gdal from source with added ArcSDE support, but it
doesn't compile. I get this error:
libsde.so: undefined reference to `pthread_atfork'
My configure command looks like this:
./configure --with-sde=/home/sde/bin/sde100/sdeexe100/
--with-sde-version=100 --prefix=/ho
I've run into this. It seems to be that there are only certain projections
that are supported in FileGDB. I tried to convert data in to the Spherical
Mercator projection and none of the projections I used (either epsg, esri
epsg, or esri wkt) would work. I believe that Even R. determined that it
wa
On 15/09/2011 06:17, Paul Ramsey wrote:
Interesting. I wonder if this is a mismatch between FGDB considering
the fid to be a column and ogr considering it to be something more
intrinsic... I think it warrants a ticket unless other layer types
misbehave in a similar way.
P.
Being an (innocent)
