The only one from Google who reads this group is Pamela, the rest of us are volunteers.
In any case, if you have lots of polygons, a KML file is not the most efficient way to load them. Encoded polygons would be better, and a custom tile layer even better than that, the latter provided you don't need much interaction with the polygons. About encoded polygons: http://facstaff.unca.edu/mcmcclur/GoogleMaps/EncodePolyline/ Examples with custom tile layers: http://maps.forum.nu/gm_main.html?lat=39.876019&lon=-107.578125&z=5&mType=5 -- Marcelo - http://maps.forum.nu -- On Feb 8, 10:18 pm, Aaron <[email protected]> wrote: > Dear Someone Who Works At Google and Does Stuff With the Maps API, > > I am working for the Sonoran Desert Network, mapping vegetation for > the National Park Service, and have put together a google map using > the API and kml files from our data. For large parks, I have layers > with hundreds of polygons. This often runs up against the KML file > size limit. > > These maps will be of great use to the public and for resource > management in the park. > > Is there any chance that for this application, I could be granted a > larger file size limit? At the moment, I am having to split up my > layers into multiple KML files, clearly inelegant. > > Thank you, > Aaron --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
