Import from Oracle Spatial¶
Use Oracle Spatial when the data already lives in an Oracle Spatial vector table.
You need to be signed in. Saving the connection once is the usual path.
Oracle Spatial appears only when GeoJibe's GDAL runtime includes the OCI driver.
This is Oracle Spatial vector support only. GeoJibe does not import GeoRaster. It copies one table into the workflow; it is not a database migration.
Before you start¶
You'll need:
- Host, port (usually
1521), and service name - An Oracle username and password
- A spatial table or view GeoJibe can read
The saved Source is the database connection. You choose the schema and table each time you import or save a Job.
You do not enter a GDAL OCI: connection string. GeoJibe builds that internally.
1. Save the Oracle Spatial Source¶
Open Sources → Add Source → Oracle Spatial.
Fill in host, port, service name, username, and password. Click Test, then Save. Name it something like Production GIS.
2. Add Oracle Spatial on the Canvas¶
Add Oracle Spatial, choose the saved Source or enter the connection, then Connect.
Choose a schema, then a table or view. Click Import. GeoJibe copies the table into the job workspace and inspects it.
After Import, Transform sees the real field names. Convert offers the same formats as an uploaded file.
You can also fill the connection in manually for a one-off run. You do not have to save a Job.
3. Process and deliver¶
Add Transform, Convert, or Python if you need them. Then choose a Destination — Download, PostGIS, another Oracle table, and the rest work as usual.
Example: Oracle Spatial → Transform → PostGIS.
Click Run.