← Back to Library

How to animate in Google earth

In a digital landscape saturated with generic tutorials, BobbyBroccoli offers something far more valuable: a masterclass in visual storytelling that treats Google Earth not as a mapping tool, but as a cinematic engine. This isn't just about learning software shortcuts; it is a rigorous argument for how to democratize high-end documentary aesthetics using accessible, free tools. The piece stands out by revealing the hidden mechanics behind the smooth, parallax-heavy visuals that have defined a new genre of online journalism, proving that the barrier to entry for professional-grade motion graphics is lower than most assume.

The Architecture of Motion

BobbyBroccoli begins by dismantling the common misconception that browser-based tools are sufficient for complex animation. The author makes a decisive choice to champion the desktop version of the software, arguing that while the browser version offers a timeline, it lacks the foundational flexibility required for serious production. "The desktop program has existed for many years now and it's what John uses for all his videos," BobbyBroccoli writes, grounding the technical advice in the proven workflow of a respected industry practitioner. This framing is effective because it prioritizes reliability over novelty, a crucial distinction for creators who cannot afford to have their workflow break mid-project.

How to animate in Google earth

The core of the argument rests on the unique capabilities of Keyhole Markup Language (KML) files, the text-based format that stores geolocation data. BobbyBroccoli notes that while both versions can view these files, "only the desktop version supports the creation and editing of KML files." This technical limitation is presented not as a bug, but as the defining feature that separates a simple viewer from a production studio. The author's insistence on this distinction is spot-on; without the ability to create and manipulate these files natively, the user is stuck reacting to the software rather than directing it.

"Making a video in Google Earth is kind of like making a 3D PowerPoint."

This analogy, offered by BobbyBroccoli, perfectly captures the structural reality of the medium. The software does not animate on its own; it requires the user to manually construct a sequence of static views that, when played back, create the illusion of motion. The author explains that the backbone of any such video is the careful layering of images, text, and 3D models, each assigned specific camera angles. This approach demands a level of pre-planning that many casual users skip, but BobbyBroccoli insists that "the more you have to zoom in on something, the bigger it's going to have to be otherwise it's just going to be blurry." This is a vital lesson in resolution management that often gets overlooked in quick-start guides.

Engineering the Illusion

The tutorial then shifts to the mechanics of animation, where BobbyBroccoli reveals a clever workaround for the software's rigid recording engine. The program records events in a linear sequence, meaning that toggling multiple images simultaneously registers as a single, jarring event. To solve this, the author suggests a counter-intuitive trick: "assign each image the exact same camera angle that way Google Earth thinks a camera movement has occurred in between each image even though all that's happening is a pause." This insight is the piece's most valuable contribution, transforming a software limitation into a creative tool for pacing. It demonstrates a deep understanding of how the underlying code interprets user input.

Organization is presented as the next critical hurdle. BobbyBroccoli advocates for a strict naming convention, suggesting a numbering scheme like "000, 001, 002" to ensure the playback order remains intact. "This will save you a major headache," the author warns, emphasizing that the creative process is often derailed by logistical failures rather than artistic ones. The advice to group these markers into folders allows for toggling entire chapters of a video at once, a feature that streamlines the editing process significantly.

Critics might note that this workflow is incredibly labor-intensive, requiring the creation of external assets in other programs and the meticulous manual sequencing of every frame. For a newsroom under tight deadlines, the time investment required to set up these KML files and render them could be prohibitive. However, BobbyBroccoli anticipates this friction by suggesting that the final assembly in a dedicated video editor is where the magic happens, allowing the creator to "chop up the video file and sync up the camera movements to my voice." This hybrid approach acknowledges that Google Earth is a specialized tool for specific shots, not a replacement for a full post-production suite.

"I usually go with mp4 as my file type and picture quality set to high."

The author's attention to the final export settings reveals a pragmatic understanding of the digital ecosystem. By recommending a custom resolution that is slightly taller than standard 1080p, BobbyBroccoli provides a clever method to crop out the unavoidable watermark that plagues the free version of the software. "This gives just enough space to crop the watermark without being excessive," the author explains, turning a restriction into a manageable technical step. This kind of practical, hack-oriented advice is what elevates the piece from a simple manual to a strategic guide.

The Bottom Line

BobbyBroccoli's tutorial succeeds because it treats the audience as intelligent practitioners capable of mastering complex workflows if the logic is clearly explained. The strongest part of the argument is the emphasis on pre-production and file management, which are often the silent killers of creative projects. The biggest vulnerability remains the sheer time commitment required to achieve these cinematic results, a hurdle that may limit adoption to hobbyists and dedicated creators rather than breaking news outlets. For those willing to invest the effort, however, this piece provides the blueprint for unlocking a powerful, underutilized visual language.

Bottom Line

This is a definitive guide for anyone looking to elevate their visual storytelling beyond static maps, offering a rigorous, step-by-step path to professional-grade animation. While the workflow is demanding, the author's strategic workarounds for software limitations make high-end production accessible to those willing to master the details.

Sources

How to animate in Google earth

by BobbyBroccoli · BobbyBroccoli · Watch video

hey everyone this video is a tutorial for animating in google earth specifically in the style of a john boyce video for those who don't know john boyce is a sports writer for sb nation secret base they cover a lot of weird interesting stories about athletes using charts 3d models and smooth jazz his videos were a very big inspiration for my recently completed series on the physics fraud of john hendrickshone i'll be showing you step by step how i made that video and hopefully you can use this as a jumping off point to experiment with your own ideas i've even linked to some of my google earth files in the description so you can play around with them this video is meant to be watched front to back but i have put timestamps in the description so you can skip ead if you're looking for something in particular as a heads up google earth outputs video files that you'll need to chop up later in a regular video editor in addition to adding things like narration and music as for images text and 3d models i make all of those in a separate program and then import them into google earth this is a list of all the programs i use but you can swap out any of these if you already have a preference the first question you'll probably have is which version of google earth should i use there are two options google earth pro aka the desktop version and google earth studio aka the browser version these are two very different programs and your choice depends on exactly what you want to make both are free programs the desktop program has existed for many years now and it's what john uses for all his videos it's basically a downloadable version of google maps that has a bunch of extra features for movie making the browser version launched in late 2018 and in order to use it you need to fill out a quick forum but you'll get access in a day or two the browser version is quite a bit different and you'll notice it's set up like a full-on video editor with robust camera options a timeline and keyframing features so why use one over the other here's a quick list of the pros and cons i think the desktop program is ...