![]() Most FME readers have parameters to define the search envelope of data that is being read: Search Envelope parameters apply to both vector and raster datasets and can be particularly efficient if the source format has a spatial index. In FME, the easiest way to define a search envelope is to use search envelope parameters.ĭefining 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. This is to ensure that the reader will find the correct table.Ī search envelope (also known as a bounding box) is a rectangular area that defines a geographic area. Note: Even when this parameter is selected, if the table is ownedīy a user other than the current user, the prefix will Is expecting feature types with different names). Not change this parameter after generating the workspace, because it is possibleįor no features to be successfully passed onto the writer (since the writer When this parameter is selected during workspace generation, the sourceįeature types will be the table names without any prefix otherwise, they 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. ![]() This is useful, for example, when creating a workspace that Selecting this parameter indicates that the reader should return the table name withoutĪny prefixes. The full name of a table in a database is of the format:ĭepending on the database format, the prefix can be. Specifies whether to keep the table qualifier. Note: Recycled tables (names starting with BIN$) will never be included. If unchecked, Tables and Merge Filter will not include system tables or tables with special characters. 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 this parameter is unchecked, the connection to the Oracle database is closed as soon as possible after data processing is complete. A persistent connection is useful for workspaces that are long-running, or published using FME Server. If this parameter is checked (default), the Oracle database connection remains open for other requestors. If this parameter is omitted, or left blank, the default LIVE workspace will be used. All tables will be read using the same workspace. The name of the Oracle Workspace Manager workspace that will be used by the reader. Username and password to access the Oracle database.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |