Oracle Spatial Object Reader/Writer
FME can read and write geometric and attribute data stored using Oracle Spatial.
This module communicates directly with Oracle Spatial for maximum throughput.
Using FME with Oracle Formats
Oracle Format | Data Type |
---|---|
attributes only |
|
raster |
|
Oracle Spatial Object Reader/Writer |
object relational model (referred to as the object model) |
point cloud |
|
relational model |
Oracle Spatial Product and System Requirements
Format |
FME Platform |
Operating System |
||||
---|---|---|---|---|---|---|
Reader/Writer |
FME Form |
FME Flow |
FME Flow Hosted |
Windows 64-bit |
Linux |
Mac |
Reader |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Writer |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Format Notes
Oracle and FME |
Description |
---|---|
3D Geometry Support |
Reading and writing of 3D surfaces and solids is available only for Oracle 11g and above. |
Oracle Instant Client |
Instant Client can be used to run your OCI, OCCI, JDBC, and ODBC applications without installing a full Oracle Client. Instant Client supports SQL*Plus. See the FME Community for more information on how Instant Client works with FME. |
Oracle Wallet |
To use an Oracle Wallet with FME, leave the Username and Password parameters empty, and enter the name of the Oracle Wallet as the value of the Service Name or Easy Connect parameter. |
By default, Oracle Spatial can only support geometry with less than 1,048,576 ordinates. Note For more information about supporting larger geometries, see Increasing the Size of Ordinate Arrays to Support Very Large Geometries in the Oracle Spatial Developer's Guide.
|
Reader Overview
The Oracle Spatial Object reader reads attributes and geometry from Spatial tables in an Oracle Spatial Database.
Writer Overview
The Oracle Spatial Object writer module stores geometric and attribute data in an Oracle Spatial database. Both uppercase and lowercase table names are supported. The writer supports the following features:
Feature |
Description |
---|---|
Transaction Support |
Provides transaction support that eases the data loading process. Occasionally, a data load operation terminates prematurely due to data difficulties. The transaction support provides a mechanism for reloading corrected data without data loss or duplication. |
Table Creation |
Uses the information within the FME workspace to automatically create database tables as needed. |
Table Dropping |
Allows each table to be written to be dropped if recreating, or truncated if appending. |
Index Creation |
Sets up and populates all needed indexes and index tables as part of the loading process. |
Bulk Loading |
Uses a bulk loading technique to ensure speedy data load. |