Top reasons to use ESRI File Geodatabase
A file geodatabase is a collection of files in a folder on disk that can store, query, and manage both spatial and nonspatial data. ESRI started this concept when Microsoft announced a 2GB limit for Access geodatabase. Access databases were primarily used as personal geodatabases.
ESRI came up with File Geodatabase format to store the data. It is a folder or directory where all the relavant files are put in and ArcObjects API identifies it as featureclasses, featuredatasets, tables and geometric networks.
- Improved versatality and usability - The file geodatabase is stored and organized in folder. Each featureclass or table is stored in one or more files.
- Optimized performance - Although the folder is scrambled with lot of files , the performance is optimized for faster response times.
- Storage Limitation - The FGDB is limited to 1TB per instance. With the use of configuration keywords, this can be expanded to 256TB.
- Easy data migration - The FGDB can be moved or copied from one place to another by simply copy/paste command.
- Improved editing model - FGDB do not lock down the entire geodatabase if the user is editing a featureclass. This model supports single data editor and many data viewers concurrently.
- Spatial Index - The FGDBs allow updates to spatial index settings for faster display , edit and query spatial data.
- Data Compression - The vector data can be stored in the file geodatabase in a compressed format that reduces storage requirements. Compression reduces the overall size on the disk. The performance of compressed data is similar to the uncompressed data.