I’m mapping potential construction footprints against sensitive habitats and need a reliable starter workflow to wrangle messy species CSVs into a clean geodatabase for quick overlap stats. For those using QGIS or ArcGIS Pro, do you standardize to a single GeoPackage with coded domains, or push straight into PostGIS for repeatable spatial joins and summarize-by-project? I’m aiming for something that scales past 200k records without bogging down while keeping metadata and field definitions consistent.
Push it to PostGIS and export per‑project GeoPackages; load CSVs with ogr2ogr into staging, normalize species codes to lookups, add GIST indexes, and materialize the footprints x habitats join for fast reporting. > “scales past 200k” With proper indexes it will, and you can keep CSV lineage in a JSONB column for metadata; do you have rights to run PostGIS or are you stuck in desktop?