Destinations¶
Destinations are where GeoJibe sends the finished data.
| Destination | Best for |
|---|---|
| Download | Get a file back once |
| PostGIS | Write a table |
| S3 | Store the converted file |
| SFTP | Drop the file on a server |
| GeoServer | Publish a vector layer |
| GeoNode | Publish a catalog resource |
Download¶
Use Download for one-off conversions. You do not create a saved Download connection.
After Run, click Download. Without signing in, Download is the only Destination.
Download cannot be used as a scheduled Job Destination — there is no file waiting for you next week unless you fetch it at run time.
PostGIS¶
Saved database connection, then schema, table, and write mode (Create, Replace, Append) per run.
Sync Jobs are different: they use a schema only. See Send data to PostGIS.
S3¶
Saved bucket and credentials, then an object key per run. AWS or S3-compatible storage.
SFTP¶
Saved host and login, then a remote path. Parent directories must already exist.
GeoServer¶
Saved GeoServer login. Each publish creates a new store and layer in an existing workspace. Vector data is published as GeoPackage.
GeoNode¶
Saved GeoNode login (token or username/password). Each publish creates a new catalog resource. Vector data is uploaded as GeoPackage.
Who can use which¶
| Destination | Without signing in | Saved connection |
|---|---|---|
| Download | Yes | Not used |
| PostGIS, S3, SFTP | No | Optional (can fill in once) |
| GeoServer, GeoNode | No | Required |
See Saved connections.