Saved connections¶
Save the connection once, then reuse it.
Examples:
- Production PostGIS
- Production GeoServer
- Field Data S3
You do not save the whole workflow here. You save how to reach the system. The table name, object key, layer, or project still belongs to each run or Job.
Why they exist¶
Without a saved connection you would retype host, bucket, and password every time.
With a saved connection:
- Save Production PostGIS.
- In any workflow, pick it as the Destination.
- Enter only this run's schema and table.
One connection can feed many Jobs.
Sources you can save¶
| Type | What is saved | Chosen per workflow |
|---|---|---|
| URL | The URL | Import when you use it |
| HTTP/API | Method, URL, auth type, encrypted credentials, query, headers, POST body | Import when you use it |
| FeatureServer | Service URL | Layer |
| PostGIS | Host, database, login | Schema and table |
| SQL Server | Host, database, login, encryption | Schema and table |
| MySQL / MariaDB | Host, database, login | Table |
| Oracle Spatial | Host, service name, login | Schema and table |
| GeoServer | Server URL and login | Workspace and layer |
| GeoNode | Server URL and login | Dataset |
| OGC Features | Service URL, auth, optional protocol | Collection / feature type |
| STAC | API URL, auth, optional collection | Collection, item, and asset |
| CKAN | Portal URL, optional API token, optional dataset | Dataset and resource |
| S3 | Endpoint, bucket, keys | Object key |
| Azure Blob Storage | Storage account, auth type, encrypted SAS or account key, optional container | Container and blob path |
| Google Drive | Connected Google account | Drive file |
| Hub | Server and token | Folder, dataset, version |
| Google BigQuery | Project and service-account JSON key | Dataset and table |
| Snowflake | Account, username, warehouse, role, auth method | Database, schema, and table |
| QFieldCloud | Server and login | Project and GeoPackage |
| Mergin Maps | Server and login | Project and GeoPackage |
Upload cannot be saved.
DuckDB cannot be saved. It is a file you upload for one run.
Destinations you can save¶
| Type | What is saved | Chosen per workflow |
|---|---|---|
| PostGIS | Database login | Schema, table, write mode |
| SQL Server | Database login, encryption | Schema, table, write mode |
| MySQL / MariaDB | Database login | Table, write mode |
| Oracle Spatial | Database login | Schema, table, write mode |
| Google BigQuery | Project and service-account JSON key | Dataset, table, write mode |
| Snowflake | Account, username, warehouse, role, auth method | Database, schema, table, write mode, spatial type |
| S3 | Bucket and keys | Object key, overwrite |
| Azure Blob Storage | Storage account, auth type, encrypted SAS or account key, optional container | Blob path, overwrite |
| Google Drive | Connected Google account | Folder and filename |
| SFTP | Host and login | Remote path, overwrite |
| Hub | Server and token | Folder, mode, dataset |
| GeoServer | Server and login | Workspace, store, layer |
| GeoNode | Server and login | Title, name, permissions |
| Webhook | Endpoint, method, authentication | Request format, timeout, success codes |
Download cannot be saved.
DuckDB cannot be saved. It writes a .duckdb file you download, like Download.
Notification webhooks (Job outcome JSON) are a separate saved resource from Webhook Destinations. Manage them from the Job editor. See Job Notifications.
Credentials¶
Passwords, keys, and tokens are stored securely on the server. They are not shown back in full after save. Test checks that GeoJibe can reach the system without delivering data.
You need to be signed in to create or use saved connections.
Manage¶
Open Sources or Destinations in the sidebar.
- Add Source / Add Destination
- Edit, Test, Save
- Delete — blocked if a Job still uses that connection
Manage Sources and Manage Destinations from Canvas Properties open the same lists.