GeoMedia Writing

Please visit FME Community for additional information on FME and Intergraph Geomedia compatibility.

Text Size

This can be a challenging 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.

The issue is that text features do not always come in with a reasonable text size and the approximate conversion into GeoMedia does not always produce a reasonable size. It is suggested that you adjust the scaling and bounds factors of the GeoWorkspace to take into account your particular dataset within GeoMedia, or that you explicitly express text size in the translation. This can be done by setting the fm0_text_size attribute on text features.

“Class not found” Errors

This is a message from GeoMedia that is passed back through FME. There are two basic causes:

• The GeoMedia Access Warehouse Writer requires GeoMedia to be installed in order to run; if it is not installed, then this message may result.
• If GeoMedia is installed, then there is likely more than one copy or version of GeoMedia installed on the machine and the installations are in conflict. This is possible due to the registration scheme of the GeoMedia products. The solution recommended by Intergraph is to uninstall all GeoMedia products, clean the registry of anything related to GeoMedia (especially the HKEY LOCAL MACHINE\Software\Intergraph\Applications key), and then reinstall the single version of GeoMedia you want to use.

Translation Errors

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 path in which the destination file is to be created must already exist.