You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
ETL of supporting geospatial datasets is currently an offline process i.e. usually involves preparing tables outside of FlowKit for later ingestion into flowdb.
Describe the solution you'd like
A foreign data wrapper for geospatial data sources to enable admins to leverage flowdb for ETL of geospatial input data e.g. admin boundary shapefiles etc.
Describe alternatives you've considered
Currently geospatial data is prepared outside of flowkit then ingested using e.g. shp2pgsql
Additional context
This should help with reproducibility of ETL steps.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
ETL of supporting geospatial datasets is currently an offline process i.e. usually involves preparing tables outside of FlowKit for later ingestion into
flowdb
.Describe the solution you'd like
A foreign data wrapper for geospatial data sources to enable admins to leverage
flowdb
for ETL of geospatial input data e.g. admin boundary shapefiles etc.Describe alternatives you've considered
Currently geospatial data is prepared outside of flowkit then ingested using e.g.
shp2pgsql
Additional context
This should help with reproducibility of ETL steps.
The text was updated successfully, but these errors were encountered: