Google has announced the public availability of its new Fusion Tables API and at the same has begun a six-month deprecation period for the SQL API. So developers need to start to move over to Fusion Tables soon.
Fusion Tables is a data visualization web application that you can use to work with large data tables to extract meaningful information.
Fusion Tables lets you store, share, query, and visualize data tables. It has a REST API that you can use to manage tables, and a query facility that can be used to 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 CSV or JSON, or you can use them as the source for apps based on the Google Maps API or Google Chart Tools. Data that can be mapped in Fusion Tables can also be a layer on a Google Map:
and it can also be a data source for Google Chart Tools:
Until now, developers have worked with Fusion Tables using Google’s SQL API. This has now been deprecated (June 26, 2012) and will cease to be available in six months, so you’ll need to move any apps you’ve created using the SQL API to Fusion Tables API.
The new API does everything the existing SQL API does, and adds the ability to read and modify table and column metadata. Fusion Tables API is also integrated with the Google APIs console so you can manage all your Google APIs in one place and take advantage of built-in reporting and authentication features.
Migrating to the new API is pretty simple; you turn on Fusion Tables in the APIs Console, update the URL endpoint in your application, remove numeric table IDs from your code, add any additional query parameters to the requests, and update the OAuth scope.
It is just over a year since Google broke away from WebKit and decided to create its own version of the rendering engine just for Chrome. What is amazing is just how much benefit Chrome has accrued fr [ ... ]