Honey, I Shrunk the KML !

In this post I will initiate a series of articles to provide tips on how to optimize content rendering (KML) viewed in Google Earth, Google Earth Plugin and Google Maps.
KML format is XML-based, so it tends to be very verbose and therefore the more features are generated in this format, the higher tends to be the final size of the generated content.

Why optimize?

1. To reduce bandwidth consumption
   In a corporate environment where the server that provides the data and Google Earth are on different computers on the same network, save on bandwidth consumption is a good practice to enable up to other computers on the same network also consuming the same data and not create an impact in other applications.
2. To reduce processing time
   A non-optimized KML consumes more processing (and hence the computer) than an optimized. This processing is reflected in the speed with which information is updated on Google Earth / Maps.
3. To reduce battery consumption (mobile)
   Less processing will result in less battery consumption, therefore, more autonomy for the battery

What we will see:

• KML optimization
• Optimization for display in Google Earth
• Optimization for display in Google Earth Plugin

Stay tuned !