Re: [visualization-api] Re: Google Visualization API - Maps

2014-08-13 Thread Sofiya Niaz
Yes, I am planning on switching to use Google Maps API instead but however I was just curious if anyone has dealt with more than (let's say) 500 markers or more in the past and how quick was it for the map to load On Tue, Aug 12, 2014 at 6:02 PM, Andrew Gallant agall...@google.com wrote: Batch

[visualization-api] Re: Google Visualization API - Maps

2014-08-12 Thread Sofiya Niaz
Hi Andrew and Carlos, Thanks for your input. Is it possible that the map load time could be reduced to a minute or so by using geocoding service and have the server load it by using Fusion tables as specified here https://developers.google.com/maps/articles/toomanymarkers. This is considering

[visualization-api] Re: Google Visualization API - Maps

2014-08-12 Thread Andrew Gallant
Batch geocoding your points should speed up the load time all by itself. The layers that article talks about are not available through the Visualization API's Map visualization; you would need to use the Google Maps API to have access to the layers. On Tuesday, August 12, 2014 6:26:15 PM

[visualization-api] Re: Google Visualization API - Maps

2014-08-07 Thread Carlos Moreira
Hi! Like Andrew already said, it's better to geocode the addresses first. If you use coordinates instead of text strings as the location data, the markers will load much faster. Like they in the documentation: The fastest modes are dataMode='regions' with locations specified as ISO codes,

[visualization-api] Re: Google Visualization API - Maps

2014-08-06 Thread Andrew Gallant
15 minutes seems quite excessive, even if you are using the maximum of 400 points. I don't know how the Map visualization works on the back-end, but you may have better luck batch geocoding your addresses first (Geocoding API https://developers.google.com/maps/documentation/geocoding/), and