Oracle Spatial Point Cloud Reader/Writer

FME can read and write Point Cloud and attribute data stored using Oracle Spatial. This module communicates directly with Oracle Spatial for maximum throughput.

Note  If only attributes are to be read or written, use the Oracle Non-Spatial Reader/Writer.

This section assumes familiarity with Oracle Spatial, its Point Cloud support, and its indexing mechanisms.

Tip: The FeatureReader transformer performs queries against any FME-supported format.

Oracle Spatial Relational Product and System Requirements

Dependencies  Reading and writing of point clouds is available only for Oracle 11g and above.

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 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 as the value of the Service Name or Easy Connect parameter.

Reader Overview

This reader reads point cloud tables from Oracle Spatial databases.

Writer Overview

The Oracle Spatial Point Cloud writer module stores point cloud and attribute data in an Oracle Spatial database. Only uppercase table names are supported.

The Oracle Spatial Point Cloud writer provides the following capabilities:

  • Transaction Support: The Oracle Spatial Point Cloud writer 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: The Oracle Spatial Point Cloud writer uses the information within the FME mapping file to automatically create database tables as needed. Creation of related tables is also supported, such as the block table for Point Cloud columns. Metadata tables and triggers are also created or updated accordingly.
  • Table Dropping: The Oracle Spatial Point Cloud writer has an option that allows each table to be written to be dropped if recreating, or truncated if appending. Likewise, related tables, such as block tables for point cloud columns, will be dropped when empty. Metadata tables are updated via Data Manipulation Language (DML) triggers; however, the triggers themselves are not currently dropped.
  • Index Creation: The Oracle Spatial Point Cloud writer will set up and populate all needed indexes and index tables as part of the loading process.
  • Bulk Loading: The Oracle Spatial Point Cloud writer uses a bulk loading technique to ensure speedy data load.