Report on Fusion table layers

Before starting with fusion table layer, first to describe what is a layer and what is the role of layer in Google maps API. Layer is a single thickness of a material covering a surface or forming an overlying part or segment. In Google maps API term: Layers are objects on the map that consist of one or more separate items, but are manipulated as a single unit. These objects within a layer are presented by or its presentation is managed by Google maps API. Fusion table Layer: The Google Maps API allows you to render data contained in Google Fusion Tables as a layer on a map using the Fusion Tables Layer object. A Google Fusion Table is a database table where each row contains data about a particular feature; for geographic data, each row within a Google Fusion Table additionally contains location data, holding a feature's positional information. The Fusion Tables Layer provides an interface to Fusion Tables and supports automatic rendering of this location data. Only five fusion table layers can be added on the map. From these five layers only one layer can be styled using some specified style rules. Style Rules:

o o

o o o

Only the first 100,000 rows of data in a table are mapped or included in query results. Queries with spatial predicates only return data from within these first 100,000 rows. Therefore, if you apply a filter to a very large table and the filter matches data in rows after the first 100K, these rows are not displayed. When importing or inserting data, remember: The total size of the data sent in one API call cannot exceed 1MB. A cell of data in Fusion Tables supports a maximum of 1 million characters; it may sometimes be necessary to reduce the precision of coordinates or simplify polygon or line descriptions. The maximum number of vertices supported per table is 5 million. When looking at the map, you may notice: The ten largest-area components of multi-geometry are shown. When zoomed farther out, tables with more than 500 features will show dots (not lines or polygons).

The fusion tables are data tables that provide built in geographic data support. Example: The layer is built on these fusion table on is displayed on the map. These layers represent different areas. For example we have to create a layer on Rajasthan map to point out three cities named

1. Jodhpur 2. Jaipur 3. Ajmer So we have to build a table with extension .csv, or .txt. This table contains two blocks city and longitude, latitude. The longitude and latitude field is so added to determine the location of these cities on the map. So this form a fusion table that puts a layer on state Rajasthan of three objects (cities). City jaipur Jodhpur Ajmer Latitude, Longitude N 26 54' 44.1858",E 75 47' 40.8398" N 26 14' 38.9626",E 73 0' 54.4922" N 26 27' 3.248",E 74 39' 47.1094"

The above table is saved as public visibility mode. It has a table id of 4055227. The Fusion Tables Layer constructor creates a layer from a public Fusion table using the table's Encrypted ID, which can be found by selecting File > About in the Fusion Tables UI. To add a Fusion Tables layer to your map, create the layer, passing a query object with the following: A select property whose value is the column name containing the location information. You must use quotes around any column names that contain spaces, reserved words, or that do not begin with a letter. Some styles are also setup for fusion table The Fusion Tables layer constructor also accepts a Fusion Tables Layer Options styles parameter, to apply color, stroke weight, and opacity to lines and polygons. Marker icons can also be specified from the supported.

The above picture shows the location pointed by map from table with id 4055227.

Conclusion: So what we can do with fusion table is Import your own data->
Upload data tables from spreadsheets or CSV files, even KML. Developers can use the Fusion Tables API to insert, update, delete and query data programmatically. You can export your data as CSV or KML too.

Visualize it instantly->
See the data on a map or as a chart immediately. Use filters for more selective visualizations .

Publish your visualization on other web properties-> Now that you've got that nice map or chart of your data, you can embed it in a web page or blog post. Or send a link by email or IM. It will always display the latest data values from your table and helps you communicate your story more easily