In module storage, function geodataframe_to_postgis fails with an non-EPSG crs in the GeoDataFrame

[rbejar]

This function saves a gdf as a table in a PostGIS DB using the GeoPandas to_postgis function. That fails if the CRS in the gdf is a non-EPSG one (for example, rhealpix defined as a WKT string, but we need that). If the gdf.crs is set to None, it works, but the CRS should be stored elsewhere.

This is not a priority for now, and it does not seem to have an easy fix. But eventually it should be solved.