The ingestion implementation I ended up using for ingesting flat/csv data simply COPYs data from file (via a streamreader), while the geospatial ingestion scheme ingests the data after reading it into GeoDataFrames (which made it very easy to add in the columns in the title, [source_data_updated and ingestion_check_time].
I'd rather update the existing data as I assume new data was published today, so I'll probably manually update my existing data warehouse but implement these fixes to use provide this behavior in stride.
The ingestion implementation I ended up using for ingesting flat/csv data simply COPYs data from file (via a streamreader), while the geospatial ingestion scheme ingests the data after reading it into GeoDataFrames (which made it very easy to add in the columns in the title, [
source_data_updatedandingestion_check_time].I'd rather update the existing data as I assume new data was published today, so I'll probably manually update my existing data warehouse but implement these fixes to use provide this behavior in stride.