[gdal-dev] Re: OGR FileGDB driver: Failed at creating table ... (General function failure.)

[Hermann Peifer]

On 15/09/2011 16:46, Hermann Peifer wrote:
>
> My quick-fix:
> I edited ../local/share/gdal/pcs.csv and changed "ETRS89 / LAEA Europe"
> into "ETRS 1989 / LAEA", ..et voilà: the error is gone. "ETRS 1989 /
> LAEA" is ESRI'ified into "ETRS_1989_LAEA", which is exactly the expected
> string for this SRS.
>
> I am not sure if it is worth filing a ticket for this specific case, as
> it is part of a wider ESRI-WKT-versus-GDAL/OGR-WKT dilemma, which in
> return is known already, see e.g. Uwe's post from some days ago.
>

I am not sure if people are still interested but for the sake of the 
exercise I just created a new FileGDB by assigning a "spatial reference" 
which only contains ESRI's string identifier of EPSG:3035, see [1]. This 
works fine and does not generate any error. However, any minor change in 
the string "ETRS_1989_LAEA" leads to the FileGDB API's "General function 
failure".

Frank, Even, Paul, et al.:
Could it perhaps make sense if the morphToESRI() function paid more 
attention to these string identifiers in order to produce even more 
"ESRI-friendly" WKT?

Hermann



[1]

$ ogr2ogr -f filegdb out.gdb in.gdb -a_srs nonsense.wkt

$ cat nonsense.wkt
PROJCS["ETRS_1989_LAEA"]

$ ogrinfo -al -so out.gdb
OGR: OGROpen(out.gdb/0x7a2240) succeeded as FileGDB.
INFO: Open of `out.gdb'
       using driver `FileGDB' successful.

Layer name: eea_1Kgrid
Geometry: Multi Polygon
Feature Count: 9
Extent: (-17.000000, 28.000000) - (-17.000000, 28.000000)
Layer SRS WKT:
PROJCS["ETRS_1989_LAEA",
     UNIT["Meter",1]]
FID Column = OBJECTID
Geometry Column = SHAPE
CELLCODE: String (0.0)
Shape_Length: Real (0.0)
Shape_Area: Real (0.0)