Download Your Fusion Tables Data

I first wrote about Fusion Tables back in 2010.

Google Fusion Tables – Are you kidding me? These stuff is “teh awesome”. Fusion tables are going to be more “killer” than Google Maps was. Yup, pay attention.


“teh awesome”? Seriously, who says that? Well I guess I did and that’s OK. Was it more “killer” than Google Maps, obviously no. It’s not that Fusion Tables was wrong, it is just there are so many alternatives to it that it really doesn’t matter anymore like it did when it first arrived.

Well if you’re like me, you probably have a lot of data in Fusion Tables and Google just sent out an email explaining how to get it out.

If you created many tables over the years, we’ve made it easy to download all your data in one step with a new dedicated Fusion Tables option in Google Takeout. You can save the rows, metadata and geometries of any base tables that you own, and export this data in the following formats: JSON, CSV and KML.

It’s a really nice tool, just tried it myself on some baseball data that I had in there. Google explains the tool as such:

The data for each table is saved to its own “archive”. The data will be saved in a Google Sheet; for datasets beyond the size limits of Sheets, you’ll get a CSV. This archive is stored in a top level folder called “ft-archive” in your Drive.

A Google Maps visualization is automatically created with the archived data. This map preserves many of the original Fusion Tables styling configurations. Any changes you make to the Sheet or CSV will appear in the map visualization.

A listing of all archived tables is stored in a Sheet. This handy Sheet is called “ft-archive-index” and lives within the “ft-archive” folder. The index Sheet summarizes each run of the archive tool and preserves the visualization URLs with encoded styles. Each time you run the archive tool, you will get additional archives based on the current data in your tables along with corresponding new rows in the archive directory.

You have until December 3, 2019 to get your data out. Google Takeout makes it easy which is really nice.

Designing a front end

I manage a GIS at a small company in Tempe, AZ. We’ve been designing web based GIS sites since the old ArcView IMS extension. We’ve moved from MapObjects IMS to ArcIMS 3,4,9 and now we’ve begun to look at UMN Mapserver. Basically we’ve heard from clients that they are having problems with the cost of maintenance of ESRI products. If we could eliminate ArcIMS/ArcSDE for these people and still provide our look and feel, this might be a market worth looking into. I’d love to make our sites work with any backend that the client wants. We’ve used .NET in our latest products, but maybe PHP or JSP would be a better choice for doing this. I’m just not sure what to think at this point, but I’ve got our database programmer looking at getting PostGIS and Mapserver installed on our Linux server.

It’s going to be quite a move from ArcIMS/ArcSDE/Oracle, but maybe we’ll learn something. I’ll post more about this next week when we get it installed.