Google Fusion Tables (Spatial) Reader Parameters

The Google Fusion Table (Spatial) Reader produces an FME feature for each row in a worksheet in the provided spreadsheet. The reader will create geometry from KML data or latitude/longitude data in the same column. The reader cannot handle geocoded location data or latitude/longitude data in two separate columns. All columns of the Google Fusion Table will appear as attributes in the feature type, including all location columns.

Google Fusion Tables formats allow you to easily upload and manage data in the cloud (for example, spreadsheets and comma-separated value [CSV] files).

Google Fusion Tables makes it easy to create visualizations like maps, timelines and other charts, and either share these with collaborators or make them publicly accessible. Users can also merge datasets that belong to different owners.

It offers a REST API to run SQL-like queries to manage tables (create, delete), manage data rows (insert, update, delete), and query the table for all rows that match spatial or data conditions. The results of queries can be output to a CSV file, or used in the Google Maps API or Google Chart Tools.

There are two versions:

  • Google Fusion Tables Non-spatial, which supports all the column types as attributes,
  • Google Fusion Tables Spatial which, for convenience, creates geometry from location columns

Both versions can read from and write to private and public tables.

Please note that only KML geometry or latitude/longitude points in the same column will be interpreted as geometry by the Google Fusion Tables Spatial Reader, although multiple latitude and longitude columns or geocoded data will be preserved as attributes for subsequent processing.

The FME Google Fusion Tables Reader can read geometric portions of private or public tables when present, or non-geometry or attribute processing when no location columns are present.

The Google Fusion Tables (both Spatial and Non-Spatial) formats do not use a dataset like most other formats. Instead, connection parameters are supplied similar to a database connection by clicking the Parameters button when generating a new workspace or adding a reader.

Connection

Constraints

Schema Attributes

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.

Advanced