Open GoogleCodeExporter opened 9 years ago
Original comment by rshap...@google.com
on 10 Nov 2010 at 9:20
Original comment by rshap...@google.com
on 21 Jan 2011 at 7:11
Yeah I completely agree. I have a column with a path to photos. Unfortunately
the root folder was moved to a new server so now I am changing all of the paths
manually (500 entries).
Original comment by G.D.Bo...@gmail.com
on 23 Mar 2012 at 1:39
Find and replace would definitely be a nice to have.
G.D.Bowie why would you not export, modify (in a txt editor, excel, etc),
delete all rows in ft and then re-import into ft? Would be a lot easier than
changing 500 entries one by one.
Original comment by daned...@gmail.com
on 23 Mar 2012 at 3:57
@Daned: I just merged two tables. One with polling stations, one with county
boundaries. Unfortunately one of the counties was consistently misspelled so
that the merge didn't work properly. To correct the typo I had to download a 70
MB CSV file before I could search and replace in Excel. This is far from
convenient :-(. Having a search and replace function in FT would have been much
better.
Original comment by timo.lu...@gmail.com
on 16 Jul 2012 at 1:48
When dealing with large data sets I often use Google Refine to give it a quick
once over and deal with data inconsistency issues. It would be great to have
some of Google Refine's functionality naively in Fusion Tables.
Original comment by daned...@gmail.com
on 16 Jul 2012 at 3:32
[deleted comment]
Totally agree. Common feature in any table editor.
Original comment by Frederic...@gmail.com
on 18 Nov 2012 at 7:06
Agree. I added some numeric data. The "0" value came through as NULL (ie
nothing, not even a "0". shading the map by that data column results in ugly
red blotches where the NULL values are.
Original comment by hank.kar...@gmail.com
on 20 Sep 2013 at 2:10
Speaking of Refine, it would also be convenient to be able to import FT into
Refine. Such ability was lost when the APIs were changed
Original comment by gibed...@gmail.com
on 27 Sep 2013 at 3:24
Fully agree! Editing on fusion tables is really not handy for big cells content.
Original comment by i...@geo.admin.ch
on 17 Apr 2015 at 9:11
Original issue reported on code.google.com by
erv...@gmail.com
on 6 Nov 2010 at 10:41