a digital scan of a 35mm film image of a processing sketch running on an LCD
Skip to Content



M5 bus route as seen by Google Street View, with each panorama synced to the GPS log from my trip and time-scaled to 1/100 its original duration. (The original QuickTime file is available for download. It's 300 MB.)


Beyond the changing neighborhoods, demographics, architecture, gentrification, etc., the thing that struck me most about the M5 was the pace and aesthetics of the trip. The bus is a truly strange thing to take in New York — particularly the M5, which one could easily substitute for a ① train. Buses are slower than the subway if you're heading uptown or downtown, and often slower than walking if you need to go crosstown. The contrast between the lazy pace of the bus (we averaged 7 mph) and the rush of the city outside the window was disorienting.

Yet taking the bus connects the rider with the city. Conversations are overheard, ridership changes from neighborhood to neighborhood, stops are missed, etc. I wanted to use Google's images to explore and subvert this connection between person and place. Living in New York represents a commitment to place and physicality — it's overpriced, it's cramped, it's a lot of work — but we deal with it for the sake "being there" and sharing the experience. Google's Street View suggests that we don't have to leave our chairs to see a place, and flattening Google's 360° panoramas to fit in a rectangular frame (as done for the video) takes this further, suggesting that we don't even have to swivel our heads.

Essentially, I used Google backwards. Instead of using Street View for reconnaissance or as an alternative to making an actual trip, I used their service to outsource the documentation of the bus ride I had already taken. The result is a complete departure from the actual experience: An hour and 40 minutes spent on a bus in the physical world is compressed into a 60 second approximation; a digital copy of my analog trip on the M5.


I ran a geo-tracking application on my iPhone for the length of the bus ride. After the trip, I downloaded all of the lat / lon / time coordinates and fed them into a Processing program I built to place the points on a map and interpolate points in between those captured by the phone. (In this manor 447 original waypoints from the trip were extrapolated into 1490 film frames.) I was careful to keep the time coding intact, so that the pace of the video — while accelerated — would be true to the pace of the bus ride. From there, I sent the data to another bit Processing code written to query Google and download, composite, and save the imagery from their Street View feature for every lat / lon point logged in the previous step. Next, one more Processing program glued together the stills in sequence to create a video.

I'll post my code shortly in case it's of use to other ITP students or other others. The Street View-scraping program, in particular, demonstrates the how trivial (and handy) it is to eavesdrop on HTTP headers and reverse-engineer a simple API like the one Google uses to load Street View source images.

Oh, and the source images, I imagine, are © Google.


The resulting video wasn't quite what I expected — my attempt to capture the halting pace of the trip by adjusting the frame rate to reflect the speed of the bus at different points along the trip ended up looking more like a bandwidth-related glitch than an intentional effect. Also, the GPS signal I used to map the points was pretty noisy, and tall buildings cut the signal strength down considerably. In midtown, the position jumps around, shaking the resulting video around and cutting from block to block, destroying the sense of forward motion — in one sense it's an honest reflection of midtown's packed streets, but in another sense there's something satisfying about such a security-camera-filled and densely networked part of time falling off the GPS radar.

October 6 2009 at 4 AM


Sublime, superbe !!
I m trying to save an image given (on http://cbk0.google.com/cbk?output=tile) in php, but they are too protection !
have you got an idea for proceed.

I'm french sorry for my bad english ! Thx

May 5 2010 at 8 AM

Eric Mika:

Juan, thanks for the kind words. Did you find the example code posted here: http://frontiernerds.com/street-scraping

Just to illustrate the simplest case... you first need to get your location into latitude / longitude coordinates (geocoding). Let's say I've already taken care of that and have the following location:

lat: 40.729291
lon: -73.993671

I need to get the panorama ID for that location, so I use the following URL which returns the panID via XML:


This gives the pano_id "iwi2jXejeqytq_i5S_FyjA", along with some other useful info about the street view at that particular location. (View the source to see the XML).

Now that I have the pano_id, I can go to another URL and grab individual tiles from the panorama, here's the URL for the top left tile:


Those are the steps that work for me.

The Processing application from the Street Scraping post just automates the geocoding, downloading, and stitching process.

If you're writing your own code, there's a chance that you'll need to spoof your user-agent in the header of your HTTP requests in order to get the data you want, that might explain "protection" (403?) errors you're receiving.

Feel free to send me your code if you're still stuck.

May 5 2010 at 10 AM