Closed GoogleCodeExporter closed 9 years ago
Also it would be good to have option "Save to existing table". Now, as i see,
there is only one option to get tracks in one place - exporting to csv and
reimporting again.
Original comment by CAJ...@gmail.com
on 17 Feb 2011 at 6:34
Fusion tables despite the name should not resemble docs. It is a "better" way
to store data than my maps.
Original comment by sandordo...@google.com
on 18 Feb 2011 at 5:21
But at least with my maps, we could save multiple rides to the same map.
Furthermore, why not store more fields (like speed, etc.) in order to leverage
the powerful charting/filtering/etc. platform that is fusion tables? And if
not, why is it a "better" way to store data?
Original comment by chun...@gmail.com
on 18 Feb 2011 at 5:49
an single Fusion table per Track is pretty useless if you are recording lots of
tracks.
So please implement an option to choose between "Upload as new Fusion Table"
and "Upload in existing Fusion Table".
Thanks.
Original comment by Christia...@gmail.com
on 2 Mar 2011 at 11:58
Original comment by jshih@google.com
on 11 Sep 2012 at 12:55
Issue 383 has been merged into this issue.
Original comment by jshih@google.com
on 11 Sep 2012 at 1:06
Merging different Fusion Tables should be a feature of Fusion Tables.
In My Tracks, we aim to provide 2 ways sync to Drive. Afterwards, let the other
applications handle merging.
Original comment by jshih@google.com
on 13 Jun 2013 at 1:16
Original issue reported on code.google.com by
chun...@gmail.com
on 9 Feb 2011 at 8:19