Google Earth on 48 screens

Back in 2009, Google developed the first Liquid Galaxy, an entirely new way to display Google Earth on eight screens – which creates an immersive experience of virtually flying around the globe. Since then, we’ve built dozens of Liquid Galaxies all over the world and open sourced the code so anyone can build their own.

Late last year, the Paris Center for Architecture and Urbanism: Le Pavillon de l’Arsenal, approached us asking if they could use Google Earth to power a new interactive display highlighting the Paris metropolitan area in 2020 with upcoming buildings in 3D. Naturally, we were excited about the project, especially when they shared that the display would be 40 square meters – posing a fun and unique challenge.

A year later, we are excited to share that the first 48 screen Liquid Galaxy is now on display in Paris. We believe this to be the largest screen showing Google Earth to date!

Photo: Vincent Fillon
What started as a 20% project to support the new Google Cultural Institute resulted in a stunning display of the Earth in almost 100M pixels – powered by 48 instances of Google Earth synchronized and operated through 4 multi-touch screens with pinch and zoom functionality. The view is even sharper due to a refresh of the entire Paris area with higher resolution imagery.

As a Parisian, it’s amazing to be able to see what the city will look like in the future. If you can’t make it to France in the near future, you can preview it at home by downloading this KML file and opening it in Google Earth.

The Canopy and Transport Hub: Patrick Berger and Jacques Anziutti architects
This project was a close collaboration between Google and Le Pavillon de l’Arsenal, as well as technology JCDecaux, End Point and design partners ultranoir.

Over the next few months we’ll be fully open sourcing this work on Liquid Galaxy, as well as the graphical interface. Keep an eye out on our source code page for updates.

The magic of gzip compression

All developers agree that saving bandwidth is a critical factor for the success of a mobile application. Less data usage means faster response times and also lower costs for the users as the vast majority of mobile data plans are limited or billed on a per-usage basis.

When using any of the Google Data APIs in your application, you can reduce the amount of data to be transferred by requesting gzip-encoded responses. On average, the size of a page of users returned by the Provisioning API (100 accounts) is about 100 Kb, while the same data, gzip-encoded, is about 5 Kb — 20 times smaller! When you can reduce data sizes at this dramatic scale, the benefits of compression will often outweigh any costs in client-side processing for decompression.

Enabling gzip-encoding in your application requires two steps. You have to edit the User-Agent

string to contain the value gzip

and you must also include an Accept-Encoding

header with the same value. For example:

User-Agent: my application - gzip

Accept-Encoding: gzip

Client libraries for the various supported programming languages make enabling gzip-encoded responses even easier. For instance, in the .NET client library it is as easy as setting the boolean UseGZip flag of the RequestFactory object:

service.RequestFactory.UseGZip = true;

For any questions, please get in touch with us in the respective forum for the API you’re using.