Common issues that arise when using GeoMedia Warehouse readers and writers are sometimes a matter of knowledge about GeoMedia's limitations.
COM Errors and Exceptions for Geomedia Access Warehouse Writer
Various issues have arisen writing to GeoMedia Access Warehouse with FME. Your FME translation may fail with one of these messages:
- Class not found
- Class not registered
- Caught a COM Exception in 'FM0Writer::writeLine'
For causes and solutions, please refer to this FME Knowledge Center article.
Text Size
This can be an awkward issue in writing. 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, use the reader parameter Text Size in Ground Units to set the size appropriate to the bounds of your source dataset. For writing, set the writer parameter Plain Text to No and provide a suitable font size using the writer parameter Font Size.
Translation Errors
When using a GeoMedia Access Warehouse writer, translation errors can occur if the destination dataset is set to create a file in a folder that does not exist. Since the GeoMedia Access Warehouse writer is a file-based writer, it requires that the folder in which the destination file is to be created must already exist.
Translation Errors in Workbench
When using a GeoMedia SQL Server Warehouse writer, the Database Username field should be left blank in the General tab of the Feature Type Properties dialog. Entering a username in this field may cause the translation to fail.
Even if the translation is successful, the GeoMedia SQL Server Warehouse reader will not be able to read the resulting table.