Database Connection
| Database Connections |
|---|
|
Connections store authentication information. For general information about sharing database connections, please see Using Database Connections. Note that different subsets of Database Connection parameters are made available in different contexts.  Connection
Select an existing connection, or Add Database Connection to define a new connection. The new connection can be made visible only to the current user, or can be shared among multiple users. |
Geomedia Access Warehouse File
Contains the filename of a Microsoft Access database or an existing ODBC data source name.
Password
For a password-protected GeoMedia Access warehouse, this is a required parameter.
Constraints
Table List
After you have specified the database connection, click the Browse button to select tables for import. A connection window appears while the system compiles a table from the database.
Once the table list appears, you can select one or more tables, and then click OK to dismiss the window. The table name(s) will appear in the Table List field in the parameter box.
Text Options
Text Size In Ground Units
GeoMedia can store text in two variations: plain text and rich text. Since FME supports plain text only, the GeoMedia reader will convert all rich text to plain text and set the text size to either the default (1 ground unit) or to the user-supplied size in ground units. The default is 1 and the range is any positive number less than 2,147,483,647.
Note: Often a dataset will appear with very small text that you cannot see until you zoom in closely, and other times the text seems too large for the data. It is suggested that for reading, set the size appropriate to the bounds of your source dataset.
Schema Attributes
Additional Attributes to Expose
Use this parameter to expose Format Attributes in 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 where you have multiple feature types, it is convenient to expose additional attributes using this one parameter. For example, if you have ten feature types and want to expose the same attribute in each one, it is easier to define it once than it is to set each feature type individually in the workspace.
Use Search Envelope
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.
If all four coordinates of the search envelope are specified as 0, the search envelope will be disabled.
Clip to Search Envelope
When selected, this parameter removes any portions of imported features being read that are outside the Search Envelope.
The example below illustrates the results of the Search Envelope when Clip to Search Envelope is not selected (set to No) and when it is selected (set to Yes).
- No: Any features that cross the search envelope boundary will be read, including the portion that lies outside of the boundary.
- Yes: Any features that cross the search envelope boundary will be clipped at the boundary, and only the portion that lies inside the boundary will be read. The underlying function for the Clip to Search Envelope function is an intersection; however, when Clip to Search Envelope is selected, a clipping operation is also performed in addition to the intersection.
Advanced
Use Oriented Points
The parameter defines how the GeoMedia oriented points will be read:
- Yes: All GeoMedia oriented points are returned with orientation information.
- No (default): All GeoMedia-oriented points are returned as normal points without orientation information.
Handle Multiple Spatial Columns
If this parameter is changed to Yes, feature geometry will be read into an aggregate. A directive 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.
Note: When using this feature, the feature type SELECT statement may not be specified.