{"id":8469,"date":"2019-04-05T03:05:52","date_gmt":"2019-04-05T01:05:52","guid":{"rendered":"http:\/\/www.sigterritoires.fr\/?p=8469"},"modified":"2019-04-05T09:27:15","modified_gmt":"2019-04-05T07:27:15","slug":"arcgis-qgis-sharing-data-the-file-geodatabase-working-with-the-geodatabases-file-gdal-and-gdb-using-qgis-posted-on-february-1st-2015-by-nick-burkhart","status":"publish","type":"post","link":"https:\/\/www.sigterritoires.fr\/index.php\/en\/arcgis-qgis-sharing-data-the-file-geodatabase-working-with-the-geodatabases-file-gdal-and-gdb-using-qgis-posted-on-february-1st-2015-by-nick-burkhart\/","title":{"rendered":"ArcGis <-> QGis sharing data: the geodatabase file WORKING WITH THE GEODATABASES FILE ( .GDAL AND GDB) USING QGIS Posted on February 1st , 2015 by Nick Burkhart"},"content":{"rendered":"\n

Despite\nthe\nvery widespread false idea according to which the geodatabases\nfile\n( .gdb ) cannot be read and modified using\ntools\nwithin the Esri ArcGIS platform, recent versions of GDAL (and therefore using\napplications such GDAL- queQGIS ) are capable\nof, effectively, read and extract information from the geodatabases\nfile\n. The geodatabase file format has become\na very common format for storing and exchanging data space\n, in particular since it allows the storage\nof multiple data layers and that allows the storage of data layers exceeding\nthe limits of others specifications .\nArcGIS\nusers, regularly, use geodatabases\nfile\nwhen the attribute tables exceed the storage capacity\nof\na shapefile<\/a> attribute table ( a DBF file is limited to ~ 2 GB\nin size ). <\/p>\n\n\n\n\n\n\n\n

The GDAL users who work with\ngeodatabases file should\nknow that GDAL includes henceforward a\nvery robust open source, read- only driver for the geodatabase format\nfile\n: OpenFileGDB . The specifications\nindicate that this driver is\nable to, efficiently, read the contents of databases with a large number of\nfields, without any dependent proprietary software.\n<\/p>\n\n\n\n

An additional option\nallowing\nto interact with geodatabases file\nusing\nGDAL is the FileGDB.FileGDB driver dependant on Esri’s File\nGeodatabase SDK , but it provides\nreading and writing access to geodatabases file. However,\ninternal tests at geospatial @ UCLA said that for read-only geodatabase\nfile operations, FileGDB driver can\nbe\nmany\norders\nof magnitude slower than the OpenFileGDB driver .\n<\/p>\n\n\n\n

Therefore those users who have\nto edit, regularly, geodatabases file\nshould\ninstall and use the FileGDB driver, while users who need\nonly\nto convert the contents of the geodatabase file to\nother formats should use the OpenFileGDB\ndriver. <\/p>\n\n\n\n

The QGIS users can read\ngeodatabases file by\ndraging\ngeodatabases, ending with extension.gdb directly in\nthe layers window. The geodatabase\ncan\nappear\nas\na\nfolder and cannot be selected using the Add vector layers tool in\nQGIS. The contents of the geodatabase file\nappear\nin the layers window , and each layer\ncan\nbe\nexported\nto\nanother format with the writing support in GDAL, including the\nshapefile format. <\/p>\n\n\n\n

For large geodatabases\nwhose\ncontent exceeds the limits of the shapefile specification we\nrecommend using GDAL ogr2ogr command\nline interface to copy the content of a geodatabase\nfile\ndirectly\nto a PostGIS<\/a> database. Use the following command,\nby replacing the bracketed text with appropriate values for\nyour configuration (the brackets should not be included\nin\nyour\norder\n): <\/p>\n\n\n\n

ogr2ogr-progress – overwrite –\nskipfailures -f \u00ab\u00a0PostgreSQL\u00a0\u00bb PG: \u00a0\u00bb host = localhost user =\ndbname [ postgres ] = [ dbname ] password = [password]\u00a0\u00bb \u00ab\u00a0[\npathtofilegdb ]. gdb \u00a0\u00bb \u00ab\u00a0[ tablename ]\u00a0\u00bb <\/p>\n","protected":false},"excerpt":{"rendered":"