Closed pramsey closed 6 years ago
+1000 would recommend to a friend
It's being requested by users in S/B: 5467978
Several big clients asking for this. +1
File Geodatabase is a really robust format for creating GIS data, w/ domains, and topology rules, it is really great for creating new data. Certain industries in GIS really love the database schema's and guidelines w/ FGDB put forth by Esri and other industry leaders. Also, it can hold a huge amount of data.
There has been no activity on this issue for more several months. We are closing it. If you think this still needs to be addressed please open a new issue.
@inigomedina this should be low-hanging fruit now, since OGR supports FGDW read natively now, no extra libraries required
Sounds great @pramsey.
In terms of user experience, it would be a good feature, for sure.
How do you feel about it in terms of our codebase? Could we go directly for an implementation of this? Would we need to prepare anything previously?
The current importer GDAL version seems to be pegged at 2.1 (would be nicer if it was 2.2.3, but hey) and OpenFGDB driver dates back to 1.11 so from a core infrastructure point-of-view, everything should already be in place. The same logic that can handle a GPKG import, which is also a multi-layer format, should be able to handle an FGDB import.
Ok. Sounds good.
Do we have any kind of doc/spec describing this feature?
Not to my knowledge. IMO anything more than "support FGDB import, make it work the same as GPKG" would be overkill.
@pramsey awesome. Glad for this integration, makes Carto more enterprise-ready :) cc @andrewbt
Closing in favor of https://github.com/CartoDB/cartodb/issues/10730
File Geodatabase (fgbd) is now a very common format in the professional GIS world: folks building geodata will likely have these files lying around their desks. OGR supports reading file geodatabase as of 1.11 using the "OpenFileGeodatabase" driver. FGDB files can contain multiple tables, so one FGDB import might create multiple tables in CartoDB.
FGDB can also contain non-spatial tables that relate to the spatial ones (commonly, FGDB data is better normalized than Shape data). They can also contain hundreds of files. In general, being able to select which tables get imported will be the next feature requested once the basic format support is added.