Send data to Oracle Spatial¶

GeoJibe can write the result of a workflow straight into an Oracle Spatial vector table.

PostGIS Transform Oracle Spatial

You need to be signed in. Download is not involved — Oracle Spatial is the Destination.

Oracle Spatial appears only when GeoJibe's GDAL runtime includes the OCI driver.

This writes one spatial table. It is not GeoRaster, schema migration, or stored-procedure migration.

You do not enter a GDAL OCI: connection string. GeoJibe builds that internally.

Before you start¶

You'll need:

Save the connection once, then reuse it.

Open Destinations → Add Destination → Oracle Spatial.

Fill in Host, Port, Service name, Username, and Password.

Click Test, then Save. Name it something like Production GIS.

The saved Destination is the database login. Schema, table, and write mode belong to each workflow.

Upload or import a vector dataset. Add Transform or Convert if you need them.

Oracle Spatial is for vector data.

If you used Convert to reproject, Oracle Spatial receives that CRS. GeoJibe does not reproject again at the Destination.

Add Oracle Spatial and select the saved Destination.

Then set:

Field	Typical value
Schema	The owner, often the same as the username
Table	`NEIGHBORHOODS`
Write mode	See below

Mode	What it does
Create	Creates a new table. Fails if the table already exists.
Replace	Overwrites the table if it exists.
Append	Adds rows to an existing table. Fails if the table is missing.

Warning

Replace mode can overwrite an existing destination table.

Click Run, or Send to Oracle Spatial in Classic.

You should see a successful delivery to schema.table.

GeoJibe writes the converted layer into that table (geometry column GEOM). Open it in QGIS or your database tool to confirm.

This is a one-off unless you save a Job.

Example: PostGIS → Transform → Oracle Spatial.