Gems ingestion pipeline

[amyfromandi]

Need to verify if there is code to extract the points or geomaterialdict in another file. Reference #171 for details

[amyfromandi]

Update
geomaterialdict is explicitly ignored in gems_etl implementation. It seems like it's an irrelevant file for the partner to ingest. Also, in this code, points are not being extracted from the .gdb; looks like the code has yet to be written.

However, our get_dataframes() is already using the right G.read_file() to get the layers (both spatial and non-spatial) from the .gdb for us to ingest. The only difference is that we need to include a read_geometry parameter to tell geopandas to read spatial vs non-spatial files. This depicts whether we insert the data into the database or apply a metadata merge on it.

Lots of refactoring with this change. Will push my updates soon.

[amyfromandi]

• b_interval and t_interval accurately populated based on geochronological order and valid interval_names that exist in macrostrat.intervals
• need a lookup function to infer formal strat_name based on the name and descrip columns from DMU.
• verify .gdb scraping tool to download all valid arizona .gdb's
• test bulk .gdb ingestion with Arizona maps!