Oracle Spatial Relational Writer Parameters
|
Database formats include a Database Connection parameter that defines and stores authentication information. For general information about sharing database connections, please see 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:
|
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.
Table Parameters
Control the density of the tessellation used when the spatial index in created for the level. Larger numbers produce finer-grained spatial indexes, which take longer to create.
Oracle Spatial Relational directly supports composite surfaces, 3D polygons and rectangles. Writing of 3D surfaces and solids is available only for Oracle 11g and above. If the Oracle Spatial Relational writer detects an older version of Oracle Database, surface features will automatically be downgraded to a 2D representation prior to writing.
Spatial Index Creation
Controls the spatial index creation.
FME will not create any indexes for the loaded data.
FME creates a spatial index for the entire table. This is useful only during the first load of data into the table, or for a previous table that has not yet been indexed.
The FME creates an index only for the features that were loaded during the translation. This is useful when you are adding data to an existing table.