Tuesday, 21 July 2015

What's next if our KML is too big/complex for the Google Maps API?



Our web app includes simple mapping capabilities (currently just markers and KML overlays on an embedded Google Map). This works pretty well; the only real limitation we face is KML overlays that go beyond Google's size & complexity restrictions for KML.


We're considering standing up our own server (e.g. GeoServer or ArcGIS Server); but that seems like a huge step just to serve up (for example) 15 MB of KML when Google's limit is 10 MB.


I need a sanity check: Is there some middle ground between Google's free and easy API for KML overlays, and setting up my own tile server?




No comments:

Post a Comment

arcpy - Changing output name when exporting data driven pages to JPG?

Is there a way to save the output JPG, changing the output file name to the page name, instead of page number? I mean changing the script fo...