Is there a workaround to exporting a >1,000-placemark map?

Showing 1-8 of 8 messages
Is there a workaround to exporting a >1,000-placemark map? M. W. Shepherd 7/7/11 1:48 PM
Summarize the issue: I recently assembled a large custom Google Map based on listings in a 1956 travel guide. I naively took on this task through Google Maps, rather than Google Earth. The icon I created for the placemarks has been revised a few times, and even though I've uploaded a new file with the same name to the same server several times, various browsers have inconsistently displayed the placemarks as the old or the new version.

It seems that the simplest way to remedy this would be to export the map as a KML so that I may batch-edit the placemarks to have the appropriate icon. Unfortunately, I am unable to do this for the entire map, since the KML export is ostensibly limited to a maximum of 1,000 placemarks, and I have somewhere around 1,500.

Is there some way that I may export the map in sections, to be recombined later? I admit that I'm relatively new to working with KML files, and I am still unclear on how to manage the data between Google Maps and, say, Google Earth via KML. I've searched many places online, including this forum, to no apparent solution.

I'm beginning to wish that I had created the map using a spreadsheet, or at least in Google Earth, since it seems plausible that I could create a relatively large (1,000+ placemarks) map in Google Earth and import it to Google Maps.

Anyway, I will appreciate any help with this issue. Had I known that I would run into such limitations, I probably wouldn't have created this project in Google Maps first.

Link to the map or business listing in question if applicable:,-84.199219&spn=13.056776,19.753418
Re: Is there a workaround to exporting a >1,000-placemark map? barryhunter 7/7/11 1:58 PM
It can be done, start with your map url:

Then add &output=kml


Then add start= and num=, eg


to get the next 1000 features. repeat (eg start=2000) if needbe.

(Note that while its certainly easier to work with larger maps in Google Earth - not least you can put stuff into folders - brining the map back to Google Maps would give similar issues, would still run into the 1000 feature limit, even just to display the map)   

Re: Is there a workaround to exporting a >1,000-placemark map? M. W. Shepherd 7/8/11 7:50 AM
Barry, after seeing your other helpful answers elsewhere in the forum, I'm glad you were able to answer my question. I was hoping that there was some hack to type in the URL that would export a specific range of placemarks.

Does importing a >1,000-placemark KML into Google Maps really run into the limit of 1,000? I was under the impression from browsing around that the display of such an imported map may be paginated (which is permissible), but it would still retain all of the placemarks. If there's actually a limit on importing as well, perhaps I should look into adapting my data to BatchGeo, which has a cap at 5,000 for its free service. I've also looked at Simile's Exhibit widget, which seems to be more complex, but more versatile.

Any further suggestions would be welcome. This map is for an educational project, and ideally, an embedded version of it would show all placemarks (as it seems to with the Google Maps default embedding code).

Thank you!
Re: Is there a workaround to exporting a >1,000-placemark map? barryhunter 7/8/11 8:29 AM
'Display'ing the KML file by pasting a URL into the search box, will run into the same 1,000 point limit - only 1000 points will be plotted. 

'Import'ing the file into My Maps should generally work, I've certainly imported maps with 3000+ features. But wont be able to display an unpaged map. If a paged map is fine, then it should be fine. 

The only way to get an unpaged map would be to use the Maps API

.... in fact I would recommend importing your KML file (once combined etc in Google Earth) into Fusion Tables. That can create an embedded map (using the Maps API) that dispalys upto 100,000 points :) [all on 'one page'] :)
Re: Is there a workaround to exporting a >1,000-placemark map? M. W. Shepherd 7/9/11 6:32 AM
Barry, thanks once again! I'll try the steps you've described when I go back to work and am not working on other projects there. I'll attempt to give an update on success or otherwise after that.
Re: Is there a workaround to exporting a >1,000-placemark map? M. W. Shepherd 7/11/11 8:48 AM
I was able to export my map as two separate KMLs using the "start/num" method, then upload the data to Fusion Tables and merge it all into one file. Thanks again for the tips!

Because I can only use Google's provided icons for the map visualization of the Fusion Table (without going through a lot of coding I don't currently understand), I've decided to use Fusion Tables for the embedded map (to show the full extent of the map in a streamlined format), with a link to the revised Google Map (My Places) for larger viewing with the custom icons.

Your solutions have opened up further cans of worms, but I'll leave those for other threads, since my main question has been answered here.

I greatly appreciate your help, Barry. Best wishes for the rest of your week!
Re: Is there a workaround to exporting a >1,000-placemark map? Sionned 8/16/11 3:32 PM
I'm trying to understand this one, and I'm getting stuck at the exporting bit here, too.  The example you gave up there appears to remove some of the information from the basic link, and then add the 'output', 'start', and 'num'.  But when I get a link for my map, the elements of the link are somewhat different and in a different order, so I'm not sure what I should do.

This is the basic link for the map I am trying to work with:,24.601135&spn=175.773847,9.84375&t=h&z=1&vpsrc=0

And this is the link I get if I click on "KML" (not the icon, the letters):

What am I missing?
Re: Is there a workaround to exporting a >1,000-placemark map? barryhunter 8/17/11 4:23 AM
You dont need to remove stuff, I just removed the unneeded stuff, just to make the example clearer. 

The important thing is to add the required stuff - add it the original map url, not the KML link.