google / fusion-tables-drive-export Goto Github PK

Adjust the padding in the filter field of the exporter data set listing:

16px should do the trick.

Remove the stackdriver debugger from the dev dependencies to the regular dependencies.

Exporting one or many fusion tables returns an error:

"Error! Requested entity was not found."

Reported by @briandavidthom

I have experienced the same issue. It does not depend on different tables. All tables are covered.
It happens after a long spinner, not our regular progress screen.
My guess is that has to do with the fusion tables API or the drive API.

The exporter has a more elaborate recognition of geometry columns. It tries to parse the fields of the first row. When found a valid KML or GeoJSON it accepts that as the geometry column.

This information is however lost on the way to the visualiser. That should not happen.

I URL field could do the trick.

But beware, and check how this behaves in relation with data driven styling.

Add a link to report issues to the front page.