Take the 2-minute tour ×
Geographic Information Systems Stack Exchange is a question and answer site for cartographers, geographers and GIS professionals. It's 100% free, no registration required.

I've been using the new FileGDB support in gdal-1.9.0 to create file geodatabases that can be opened in ArcGIS. For example (I'm doing this all on one line, so I'm not certain this will run as indented here):

ogr2ogr -overwrite -f 'FileGDB' \
    -sql "SELECT 
              CAST(gml_id AS character(255)), id, 
              CAST(scene_id AS character(255)), 
              CAST(license_type AS character(255)), 
              CAST(url AS character(255))
          FROM SDMI_Inventory" \
    sdmi_inv.gdb \
    WFS:"http://wfs.alaskamapped.org/inventory"

This worked great until 10.0 Service Pack 4, at which point ArcMap / ArcCatalog started reporting errors similar to this when you try to add / preview the layer:

Error opening feature class
The item does not have a definition. [SDMI_Inventory]
The item does not have a definition.
The XML being loaded could not be parsed. [physical name: SDMI_INVENTORY]
The item does not have a definition.
The XML being loaded could not be parsed. [physical name: SDMI_INVENTORY]

I've got the latest (1.2) API and the latest GDAL (1.9.0), x86_64 GNU/Linux.

Anyone have any ideas how to get this to work again?

share|improve this question
    
perhaps try to upgrade the database first with catalog? –  Brad Nesom May 3 '12 at 21:13
    
Brad, it is broken in SP4 whether you start a new geodatabase or overwrite an existing one. –  cswingle May 3 '12 at 22:27
    
you mean with ogr right? I wonder create using esri, ogr in to another store, and ogr back out? Might help prove if it is gdal or not then you could hit the gdal dev group for an update. (basically doing some of the legwork for the devs) –  Brad Nesom May 4 '12 at 15:35
    
I guess you would need to create an esri gdbapi specific and see if it is broken. then you could say it was gdal. –  Brad Nesom May 4 '12 at 15:37
    
Yes, a FileGDB created with ogr alone is fine with ArcGIS 10.0 SP3, but broken in SP4. I suspect it's an ArcGIS issue, not GDAL, but I don't know for sure. I was hoping there was an ogr flag related to metadata that might fix it. –  cswingle May 7 '12 at 15:16
add comment

1 Answer

I did a search for geodatabase and found the following...

NIM065375 - Incorrect renaming of the Geodatabase object within ArcCatalog; results in corruption of GDB_items table and makes the renamed objects unusable within ArcCatalog.

Also Several known issues in regard to versions
Surely you have already been here... gdal.org/ogr
issue Tracker
This shows some issues in regard to spatial reference. perhaps updating the srs prior to opening might help.
Just grasping at some straws here maybe one will cause some resolve.
You are kind of in between the gdal\dev and the gdb API\dev

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.