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 have an ESRI File Geodatabase (FileGDB) (size is 15+GB), which has over 10 layers, when I open it up in ArcGIS, everything seems to be working.

I want to move this database to postgreSQL with OGR ogr2ogr.

First I am checking the ogrinfo with:

ogrinfo pathToFileGDB

I get result:

INFO: Open of `C:\Foo\My Documents\ArcGIS\Default.gdb'
  using driver `FileGDB' successful.

But I see no layers, nor does the ogr2ogr see any layers. I should see all the layers here like I saw in ArcGIS. So I am unable to move it to postgreSQL.

I tested the same thing on a smaller FileGDB(800MB) and I can see all the layers with ogrinfo, also the ogr2ogr works.

What could be the problem? Is my DB too big, if so, what could be a workaround? Any other suggestions?

share|improve this question
add comment

3 Answers 3

The file geodatabase must be a 10.0 version or newer for OGR. You can display the geodatabase version with arcpy.

print arcpy.Describe('c:/pathto/your.gdb').release

2,2,0 is 9.2
2,3,0 is 9.3.x
3,0,0 is 10.x

share|improve this answer
add comment

Another possibility is that the projection may not be recognized by the file gdb api - layers with "custom" projections may not show up:

http://trac.osgeo.org/gdal/ticket/4578

Using ESRI tools, you could check that the layers in the larger .gdb have the same projection definition as the layers in the smaller tested .gdb. Recognized projections are somewhere in the ArcGIS install folders.

share|improve this answer
add comment

You could try passing -al -so to ogrinfo, e.g. ogrinfo -al -so pathToFileGDB

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.