Hot answers tagged google-fusion-tables
It is trivial with ogr2ogr and SQLite SQL dialect. Next examples write 10 first lakes into one KML file and next 10 lakes into another KML file ogr2ogr -f kml batch_1.kml lakes.shp -dialect sqlite -sql "select * from lakes limit 10" ogr2ogr -f kml batch_2.kml lakes.shp -dialect sqlite -sql "select * from lakes limit 10 offset 10"
You can use the Proj4 converter: http://trac.osgeo.org/proj/ Yes, it is a converter but you can convert bulk coordinates. Create a simple text file (let's say sweref99.txt) with the coordinates, e.g. 606905.22 6970515.93 635765.54 7223101.41 In order to convert all coordinates from this file the command is like this: cs2cs +init=epsg:3006 +no_defs +to ...
The ogr2ogr example is probably the most efficient, but if you prefer to do it without commandline you can just open the attribute table of the layer you're saving as KML, order the table on ID and starting from the top you select a number of records which you think will be within the limit (if the file is 150 megabytes, maybe select half of the records?) ...
The error message on console is: Access Not Configured. Please use Google Developers Console to activate the API for your project. At bottom of example page on openlayers.org posted in question you can see this text: View the fusiontables.js source to see how this is done. You will need to get your own apikey from Google's API Console for this to ...
I had a similar problem and used a kml parser (geoxml3) to locally parse a kml. I later ended up storing each kml file as a database table and looping through the records to plot a polygon. Loading the kml from a server was the slowest of all.
Two ways to minimize the size of each request. 1 - Make sure the polygon shapes are smoothed to the resolution. I.e. you don't need to show all the minute bends in the lake if you are viewing it at country level. So if you are going the JSON route, have different JSON files for different zoom levels. I found that having 3 different simplifications worked ...
This problem is known as Too many markers. See this article: https://developers.google.com/maps/articles/toomanymarkers for possible solutions. They list a few.
I know this post was from a while ago, but we ran into the same problem so we went off and built it as a premium service for our Google Maps enterprise offering. Needless to say it is a paid solution, so I am not going into a marketing pitch on a technical forum. However, this was one of the first posts that I found when I was actually looking fora ...
Only top voted, non community-wiki answers of a minimum length are eligible