Re: Export of hand populated data from Google table in CSV (and Excel)

[asgallant]

There are limitations to what you can do (due to browser security issues), but you roll your own method.  I wrote a hack to accomplish this a while back: http://jsfiddle.net/asgallant/MqERY/3/ (the relevant section of code is near the bottom, see the "var runOnce = ..." line).

On Thursday, September 13, 2012 12:09:02 PM UTC-4, ben wrote:

Hi, is there a way or do you know if it is planned to export the data from hand-populated tables automatically (in CSV and preferable also in Excel)? We have seen that the documentation says 

"To use a toolbar, your visualization must get its data from a URL; you cannot pass in hand-populated DataTable or DataView objects. You will pass the URL of the data used to populate your visualization into the drawToolbar() method." Would be great if Google could add this functionality to export all data in a table automatically in those two formats (as I bet we are not the only onces with this requirement?!). 

Thanks!

ben

[asgallant]

What do you mean when you say it causes the API not to load?  That event listener shouldn't be created until after the API loaded.  If you share the source code you are using on your local machine, I'll take a look and see what might be happening.

On Tuesday, January 15, 2013 4:37:34 PM UTC-5, MTap1 wrote:

Hi, I am attempting to export the elevation profiles from googles elevation API to a CSV file using your hack example:   http://jsfiddle.net/asgallant/MqERY/3/.  The code works wonderfully in Dreamweaver, exporting to Google Chrome.  However, when I run the code on a localhost, the  "var runOnce = ..." function causes the API not to load. This occurs for my altered code as well as for the code you provided in the hack.  Is Google preventing this function for some reason?

Any help would be great.  :)

[MTap1]

Thanks for the help!  :)   Like I mentioned, everything works fine on my own computer (even your code).  However, when I alter the table data to support a .csv format, the "...  var output = csvData.join('\n');  " line from your example causes the map/charts/etc to fail to load on my localhost port.  Replacing the "\n" with anything else (e.g., ",") will sort of fix the issue, but I fail to get the .csv in two column form. I had the same problem when trying to print the data from a table to a textarea in the body of my page.   

Try running this code on your localhost:  http://tinkerbin.com/IXRYVDkF.   It's your code marked up where I am having an issue.   

Also, here is my code (printing to text area, but same issue occurs):

function plotElevation(results) {

    elevations = results;

    var obj=document.getElementById('textlocation'); //This assigns the textarea

    

    var path = [];

    for (var i = 0; i < results.length; i++) {

      path.push(elevations[i].location);

    }

    

    if (polyline) {

      polyline.setMap(null);

    }

    

    polyline = new google.maps.Polyline({

      path: path,

      strokeColor: "#79d6fe",

      map: map});

    

    data = new google.visualization.DataTable();

    data.addColumn('string', 'Resolution (m)');

    data.addColumn('number', 'Elevation (m)');

var len= 0;

    for (var i = 0; i < results.length; i++) {

len = len + elevations[i].resolution;

len1 = Math.round(len);

var print_len = len1.toString();

      data.addRow([print_len, elevations[i].elevation ]);

var txt=document.createTextNode(print_len+", "+elevations[i].elevation+"\n") //This prescribes what to write in the textarea

obj.appendChild(txt) /This adds text to the textarea

    }

var endcode = document.createTextNode('Next City...'+"\n")

obj.appendChild(endcode)

    document.getElementById('chart_div').style.display = 'block';

    chart.draw(data, {

      width: 600,

      height: 150,

      legend: 'none',

      titleY: 'Elevation (m)',

  titleX: 'Resolution (m)',

      focusBorderColor: '#00ff00',

  colors: ['#cedfad']

    });

  }

In my body:

<textarea name= "textloc" id="textlocation" style="resize: none;" cols="25" rows="20" ></textarea></td>

[asgallant]

The tinkerbin link you sent doesn't contain any code.

[MTap1]

If you use your example:  http://jsfiddle.net/asgallant/MqERY/3/   The error I am encountering occurs at line 206 in the script window.   SO sorry for the two attempts to explain.  I am not sure what happened to the tinkerbin info...

[asgallant]

What is the error you are getting?  You mentioned above that the chart's don't load with '\n' in the join, but they do load if you have ',' - is that true?  If so, I have no idea what is going on, as that code has nothing at all to do with drawing the charts.  I could see how it may affect opening the CSV (it is possible you need to use '\r\n' instead of '\n' for opening the CSV in Windows, but I just ran the test code and downloaded the CSV which opened fine in Excel, so I don't think that's the issue).

[MTap1]

Still having issues, even after doing some more reading on the issue.   I am using google's app engine to upload the script to my local host.   I attached a better version to mess around with, but I cannot seem to find a solution that will allow the '\n' to remain.   

Thanks, again, for all your help.   This is more of a hobby for me, but working through the bugs is really allowing me to get a better sense of the power of using google's API's.

[asgallant]

I played around a bit and the only change I can recommend making is from loading the deprecated "columnchart" package to the current "corechart" package (as the chart won't draw in IE 9 using the old package).  I never encountered any error with the "\n".

IE doesn't handle the URI properly, and so will never trigger a CSV download.  This has nothing to do with the javascript, it is a limitation of the browser.

[MTap1]

Thanks!   To recap: the "\n" issue only occurs in Chrome, Firefox runs the map (but prompts a warning message upon loading about the javascript), and IE doesn't handle the URI properly.   Oddly, when you run the file on a local machine, all of these issues wash away.  

Thanks for all your help.  Sometimes an extra pair of eyes can point you to the obvious.