Troubleshooting

For convenience, feature types correspond to Google Maps Engine table names. However, table names on Google Maps Engine are not necessarily unique.

In such a situation, work around the ambiguity by renaming the tables with non-unique names using the Google Maps Engine web interface, or change the FME feature type to be a Google Maps Engine table ID. The table ID can be obtained from the Google Maps Engine web interface by opening the details page for the table, and clicking the Asset ID link.

Note that there are limits to several aspects of the storage of data in Google Maps Engine tables, including numbers of attributes, numbers of vertices per geometry, number of features per table, attribute name length, attribute value length, and number of vertices per table.

Note that Google Maps Engine API has different limits than the import tool. Please see the Overview section for more details.

Note that the links to the limit web pages may require authentication with a Google Maps Engine account.

To make use of Google Maps Engine’s geocoding functionality, the table being written to must have an attribute named gx_location.

Features being written to the table can then supply an address as the value for gx_location, which will automatically be geocoded by Google Maps Engine.

Learn more about Google Maps Engine’s geocoding functionality at http://developers.google.com/maps-engine/documentation/geocode.

When the Google Maps Engine writer creates a non-geocoded table, it populates the table with features by writing the features to a temporary KML file, and then uploading the KML file to Google Maps Engine. This is done in order to take advantage of the higher feature complexity limits enabled by the upload API for Google Maps Engine, and to minimize API requests. However, KML uploads have some limitations compared to inserting features into an existing table:

• It is an error to write features with null geometry.
• Missing and null attribute values will be written as the empty string.
• The entire KML dataset may be rejected by Google Maps Engine, in which case the reason(s) for rejection can be manually retrieved via the Google Maps Engine web interface.