No, tested it again. I've now 16 KMLs and it's lame, lame, lame :) No chance, will use my own tiles :) Thanks
bratliff schrieb: > On Jan 18, 9:01 pm, "Neil.Young" <[email protected]> wrote: > >> Yeah, I'm already at tiles with this project. But KML doesn't work >> either. Too much data. I'm creating my own tiles now. But this also >> takes time :)... >> > > Instead of one KML file with 400 polys you could have 400 KML files > with one poly in each - perhaps a compromise in between. > > In the US, each state has approximately 50 to 100 counties on > average. You could have 50 state KML files with a total of 3110 > county polys. Several small states like Maine, New Hampshire, > Vermont, Massachusettes, Connecticut, Rhode Island could be clustered > into one KML file. I suspect the same thing might work in Germany. > > Google has an undocumented "mapsdt" service which will convert your > KML files into tiles. If your KML file is very complex, GGeoXml will > use "mapsdt" to build tiles. Otherwise, it will use GPoly. I have > asked Pamela to provide a way to force the use of "mapsdt" but I > believe it is fairly low priority. > > If you look at: > > www.polyarc.us/sparse > > you can see "mapsdt" in action. > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Maps API" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/Google-Maps-API?hl=en -~----------~----~----~----~------~----~------~--~---
