Oracle Spatial Object Reader Parameters

About Database Connections

Database formats include a Database Connection parameter that defines and stores authentication information. For general information about sharing database connections, please see Using Database Connections. Using Database Connections.

Note that Database Connection parameters differ slightly, depending on context and/or database format.

Connection

From the Connection parameter in a database format, you can do one of the following:

  • Select an existing, previously defined connection. See the section Reusing a Database Connection in Using Database Connections
  • Select Add Database Connection to define a new connection. See database-specific parameters below, as well as the section Adding a Database Connection in a Workspace in Using Database Connections. The new connection can be made visible only to the current user, or can be shared among multiple users.

Connection Parameters

Specifies the Oracle database to connect to. This may be a Net Service Name defined in tnsnames.ora or an Easy Connection Identifier. Either form of connection identifier may be prefixed with username and password information.

[<username>[/<password>]@][//]<hostname>[:<port>]/<service_name>.

[<username>[/<password>]@]<net_service_name>

The username and password to access the Oracle database.

Oracle Workspace

The name of the Oracle Workspace Manager workspace that will be used by the reader. All tables will be read using the same workspace. If this parameter is omitted, or left blank, the default LIVE workspace will be used.

Persistent Connection

If this parameter is checked (default), the Oracle database connection remains open for other requestors. A persistent connection is useful for workspaces that are long-running, or published using FME Flow.

If this parameter is unchecked, the connection to the Oracle database is closed as soon as possible after data processing is complete.

Include System Tables

If checked, the Tables parameter (in Reader Parameters and Reader Feature Type Parameters), and the Merge Filter checkbox in the Reader Feature Type Parameters dialog will include tables that live in system schemas, or contain special characters like / and $.

If unchecked, Tables and Merge Filter will not include system tables or tables with special characters.

Note  Recycled tables (names starting with BIN$) will never be included.

Constraints

Specifies whether to keep the table qualifier. The full name of a table in a database is of the format:

<prefix>.<table_name>

Depending on the database format, the prefix can be <database_name>.<owner_name>, <owner_name>, or <schema_name>.

Selecting this parameter indicates that the reader should return the table name without any prefixes. This is useful, for example, when creating a workspace that will be passed on to another organization using the same table names, or performing a translation to another database format but with a different user name.

When this parameter is selected during workspace generation, the source feature types will be the table names without any prefix; otherwise, they will contain the owner name as a prefix. It is recommended that you do not change this parameter after generating the workspace, because it is possible for no features to be successfully passed onto the writer (since the writer is expecting feature types with different names).

Note  Even when this parameter is selected, if the table is owned by a user other than the current user, the prefix will not be dropped. This is to ensure that the reader will find the correct table.

Controls whether 3D polygons are read by the Oracle Spatial Object reader as 3D face geometries or as regular polygons.

After specifying the database connection, click the Browse button (...) to select tables for import. A connection window appears while the system retrieves the tables from the database.

Once the Select Tables dialog appears, you can select one or more tables. Click OK to dismiss the window and add the selected table name(s) to the Tables parameter.

The WHERE clause parameter is used to constrain the row selection in tables chosen in the Tables parameter. FME will select only the rows (records) that match this condition.

The easiest method to construct a WHERE clause is by using the editor. Click the browse button (...) to open the editor, and use the SQL functions to construct the clause.

You can also type a WHERE clause directly in the parameter field:

Examples

When querying integer and number data types:

NUMLANES = 2

LENGTH > 2000

If the WHERE clause SQL is invalid, the translation will fail.

Tip  For assistance with constructing WHERE clauses, click the AI Assist button in the WHERE Clause editor.

MapInfo Symbology

Checking this box allows the reader to parse MapInfo style and index columns.

This optional generation parameter specifies the name of the MapInfo symbology style column. If a column by this name is found, it will be omitted from the schema of the generated source feature type, and the parameter will be set to the name of this column.

This optional generation parameter specifies the name of the MapInfo symbology index column. If a column by this name is found, it will be omitted from the schema of the generated source feature type.

Additional Attributes to Expose

Use this parameter to expose Format Attributes in FME Workbench when you create a workspace:

  • In a dynamic scenario, it means these attributes can be passed to the output dataset at runtime.
  • In a non-dynamic scenario, this parameter allows you to expose additional attributes on multiple feature types. Click the browse button to view the available format attributes (which are different for each format) for the reader.
 

A search envelope (also known as a bounding box) is a rectangular area that defines a geographic area. In FME, the easiest way to define a search envelope is to use search envelope parameters.

Defining a search envelope is the most efficient method of selecting an area of interest because FME will read only the data that is necessary – it does not have to read an entire dataset. Search Envelope parameters apply to both vector and raster datasets and can be particularly efficient if the source format has a spatial index.

Most FME readers have parameters to define the search envelope of data that is being read:

Screenshot with blank search envelope min and max x and y parameters

The parameters include the x and y coordinates of the bounding box as well as a parameter that defines the coordinate system.

How to Define the Bounding Box

Using the minimum and maximum x and y parameters, define a bounding box that will be used to filter the input features. Only features that intersect with the bounding box are returned. Note that the bounding box intersection is not a full geometry intersection (based on spatial relationships) that would be returned by a transformer like the SpatialFilter.

Note  If all four coordinates of the search envelope are left at 0, the search envelope will be disabled even if this option is checked.

Search Envelope Coordinate System

Specifies the coordinate system of the search envelope if it is different than the coordinate system of the data. The coordinate system associated with the data to be read must always be set if this parameter is set.

If this parameter is set, the minimum and maximum points of the search envelope are reprojected from the Search Envelope Coordinate System to the reader’s coordinate system prior to applying the envelope.

Advanced

Bulk Read Size

Rows are read from the Oracle database using a bulk reading technique to maximize performance. This parameter allows you to tune the performance of the reader by specifying how many rows are read from the database at a time.

The default is 200.

This parameter allows for the execution of SQL statements before opening a table for reading. For example, it may be necessary to create a temporary view before attempting to read from it.

For detailed information about SQL functions, click the corresponding menu item in the SQL to Run editor helpClosed.

Available menu options depend on the format.

Multiple SQL commands can be delimited by a character specified using the FME_SQL_DELIMITER directive, embedded at the beginning of the SQL block. The single character following this directive will be used to split the SQL block into SQL statements, which will then be sent to the database for execution. Note: Include a space before the character.

For example:

FME_SQL_DELIMITER ;
DELETE FROM instructors ;
DELETE FROM people
WHERE LastName='Doe' AND FirstName='John'

Multiple delimiters are not allowed and the delimiter character will be stripped before being sent to the database.

Any errors occurring during the execution of these SQL statements will normally terminate the reader or writer (depending on where the SQL statement is executed) with an error. If the specified statement is preceded by a hyphen (“-”), such errors are ignored.

This parameter allows for the execution of SQL statements after a set of tables has been read. For example, it may be necessary to clean up a temporary view after creating it.

For detailed information about SQL functions, click the corresponding menu item in the SQL to Run editor helpClosed.

Available menu options depend on the format.

Multiple SQL commands can be delimited by a character specified using the FME_SQL_DELIMITER directive, embedded at the beginning of the SQL block. The single character following this directive will be used to split the SQL block into SQL statements, which will then be sent to the database for execution. Note: Include a space before the character.

For example:

FME_SQL_DELIMITER ;
DELETE FROM instructors ;
DELETE FROM people
WHERE LastName='Doe' AND FirstName='John'

Multiple delimiters are not allowed and the delimiter character will be stripped before being sent to the database.

Any errors occurring during the execution of these SQL statements will normally terminate the reader or writer (depending on where the SQL statement is executed) with an error. If the specified statement is preceded by a hyphen (“-”), such errors are ignored.

If this parameter is set to Yes, feature geometry will be read into an aggregate.

A parameter is set on the aggregate to indicate that each part of the aggregate is independent from the others, and its own geometry. Geometry parts of the aggregate are named and contain geometry according to their respective column in the table being read.

If a geometry is read as null, it will be appended to the aggregate as a null geometry. Geometry-specific data normally added to the feature as attributes will be added as traits to the geometry instead.

Note  When using this feature, neither the geometry column, nor the feature type SELECT statement can be specified. Also, tables with topology columns will not be read in this mode.

This parameter specifies the type of relationship which must exist between the search envelope and the geometry in the target layer. Any supported relationship, or combination of relationships, may be specified.

This table lists the valid geometry interaction relationships.

Search Method Description
ANYINTERACT The objects are non-disjoint.
CONTAINS The interior and boundary of the search envelope is completely contained in the interior of the Oracle geometry.
COVEREDBY The opposite of COVERS. A COVEREDBY B implies B COVERS A.
COVERS The interior of the search envelope is completely contained in the interior or the boundary of the Oracle geometry and their boundaries intersect.
DISJOINT The boundaries and interiors do not intersect.
EQUAL The two objects have the same boundary and interior.
INSIDE The opposite of CONTAINS. A INSIDE B implies B CONTAINS A.
ON The interior and boundary of the Oracle geometry is on the boundary of the search envelope (and the search envelope covers the Oracle geometry). This relationship occurs, for example, when a line is on the boundary of a polygon.
OVERLAPBDYDISJOINT The interior of one object intersects the boundary and interior of the other object, but the two boundaries do not intersect. This relationship occurs, for example, when a line originates outside a polygon and ends inside that polygon.
OVERLAPBDYINTERSECT The boundaries and interiors of the two objects intersect.
TOUCH The boundaries intersect but the interiors do not intersect.

In addition to specifying a single relationship, one may specify a combination of relationships to be tested by concatenating them with a plus sign (+). For example, the parameter may be specified as INSIDE + TOUCH.

This specifies the test that is applied to the results of the above geometry relationship comparison. When using the object model, Spatial queries return results of TRUE rather than the name of the interaction – as they do with the older relational model – so the default test for the object model is “= ‘TRUE’”, regardless of the type of interaction involved.