Nowadays Instead of Esri's SHP of GDB files, GIS information is shared via a GeoPackage file.
This is an open, standards‑based geospatial data format defined by the OGC.
GeoPackage is designed to store multiple types of spatial data in one single file.
This aligns closely with the Bentley user feedback you’ve seen:
FGDB works well inside ArcGIS
GeoPackage works everywhere
Users increasingly expect:
One file
Open spec
No vendor lock‑in
Clean replacement for Shapefile
Aspect |
File Geodatabase (FGDB) |
GeoPackage (GPKG) |
|---|---|---|
Standard |
Esri‑defined (proprietary) |
OGC open standard |
Storage model |
Folder ( |
Single SQLite file ( |
Openness |
Spec not fully open; API‑based access |
Fully documented, open |
Typical ecosystem |
ArcGIS / Esri stack |
QGIS, GDAL, PostGIS tools, mixed stacks |
Interoperability |
Good inside Esri, limited elsewhere |
Very strong across vendors |
Portability |
Must move whole folder |
One file = easy sharing |
Database engine |
Esri custom storage engine |
SQLite |
SQL access |
Limited / Esri‑specific |
Standard SQL |
Raster + vector |
Yes |
Yes |
Multiple layers |
Yes |
Yes |
Editing model |
Single editor, multiple readers |
Single editor, multiple readers |
Sources: Esri documentation and comparative analyses [pro.arcgis.com], [carto.com], [linkedin.com]
FGDB ≈ production database for Esri users
GeoPackage ≈ interchange / delivery format for everyone else
Supporting GeoPackage does not compete with spatial databases (PostGIS, Oracle Spatial, SQL Server), but complements them by:
Improving ingestion from open‑data portals
Reducing friction for non‑Esri users
Replacing Shapefile without breaking workflows