Import from third-party platforms
Bring community or territorial data from external platforms — such as GBIF, iNaturalist, or ArcGIS Online — into your Guardian Connector data warehouse using GC Scripts Hub.
Tools involved:
- GC Scripts Hub — connector scripts for GBIF, iNaturalist, ArcGIS, and many other sources
- PostgreSQL — where imported rows land for analysis and visualization
- File Browser — optional path for reviewing exported files
Steps
- Choose a connector in GC Scripts Hub under
f/connectors/(for examplegbif,inaturalist, orarcgis). See the Data Connectors list for what each one supports. - Create a Resource in Windmill with the credentials or parameters the connector needs (API keys, project IDs, layer URLs, bounding boxes, and so on). Your Windmill Admin typically sets this up once per source account.
- Create a Schedule that runs the connector script on an interval you choose. Name the schedule and path after the source so the Schedules page stays readable.
- Run once from the schedule's More options menu, then open the run logs to confirm success.
- Confirm the table in the warehouse (and, if you use them, create a Superset dataset or GC Explorer view on that table).
The same pattern applies to other Scripts Hub connectors (ODK, Global Forest Watch, SMART, and more). Platform-specific details live with each connector and, for biodiversity sources, in the guides linked below.
Related
- GBIF guide — discovering and importing public biodiversity records
- iNaturalist guide — project observations and the iNaturalist: Fetch Observations script
- From KoboToolbox to Superset and From CoMapeo to Explorer — full end-to-end examples of the same schedule → warehouse → visualization pattern