Walking Men, Or The Google Street View Trike Has A Posse

walking_man_pointing.jpg
Some interesting developments since putting the Walking Man self-portrait collection out there. Thanks for the feedback and responses.
I think it’s becoming clearer that walking man is not, as I wrote, a guy who “came upon the Google Street View Trike preparing to map the Binnenhof” and who “decided to tag along.” Instead, he’s probably part of the Google Trike crew.
I’d always entertained the possibility, and when, after the initial burst of discovery and image extraction, I found some additional panos from around the lake that made it clear his relationship to the Trike was at least a factor in his appearances.
From the intro I wrote for the proof [which I’ll probably publish at some point, even as I plan to revise it for any future editions]:

His actions in the final two panoramas lend themselves to speculation: In his penultimate appearance, walking man becomes pointing man; he is seen gesturing across the plane, breaking the fourth wall, as it were, by addressing the Google Trike driver himself.
Perhaps this crossed a line about the presumption of passivity for Google’s photographic bystanders. Or maybe it violated some rule of non-engagement, a Street View Prime Directive. Is it possible that he’d been talking with the Trike rider, his personal [sic] camera operator, all along?

Yes, yes it is.

Continue reading “Walking Men, Or The Google Street View Trike Has A Posse”

walking man – a self-portrait collaboration with Google Street View

walking man proof - 1
In the Summer of 2009, an unidentified young man came upon the Google Street View Trike preparing to map the Binnenhof, the center of the Dutch government, in The Hague. He decided to tag along.
The man walked alongside the Google Trike, persistently inserting himself in the foreground of its nine computer-controlled cameras’ panoptic fields of vision.
walking man proof - 3
Meanwhile, Street View’s automated panorama generation system read his presence as a data anomaly and consistently attempted to erase him from the photos.
walking man proof - 6
The resulting images, extracted from nearly every Street View panorama of the Binnenhof complex, reveal the history and process of their own making. They are at once a minute detail in Google’s extraordinary, ongoing portrait of the entire world, and one man’s wresting of control of his own image and his audacious assertion of his own presence.
I discovered these images in February 2010.
mauritshuis_portrait1.jpg
At first, it was the distortions of time, space and perspective in these photos that caught my eye. As I began mapping out [sic] the scope of the project, however, I became fascinated by how this man seemed to travel almost precisely at the distance that simultaneously kept him in frame, but also all but guaranteed his algorithmic erasure.
Then I tried to understand the images as portraits, or self-portraits. As the exercise of the flaneur. The product of the flaneur’s gaze. An artifact of a moment in time, in space, evidence of the photographer’s decisions. As photos or cinema. Surveillance or subversion. Indexing, seriality. As virtual or real, documentary or manipulation, strategies or tactics. I looked at Muybridge and Marey. I went back to re-read Benjamin, Bergson, Barthes, de Certeau, Sontag, but these images seemed to thwart every attempt to put them into a critical or historical context as photographs.
And yet they’re so easy to look at and use; we all become Street View-proficient, if not fluent, within moments of our first encounter with it. And the walking man apparently made them on a whim, by doing nothing more than strolling along.
walking man - a self-portrait collaboration with Google Street View
I decided to extract, compile, and print the entire set of photographs as a book. The title, walking man, is a reference to Alberto Giacometti, whose sculptural notions of distance and vision I was studying at the time. “Self-portrait” is an acknowledgment of their subject’s creative intent, and “collaborative” refers not only to Google’s operation of the camera, but also to their first pass at selecting images, and to the crucial aesthetic impact their manipulations have on the images they ended up publishing.
The images are actually screencaptures from Google Maps in Safari that include every appearance of walking man within each panorama. Though I composed each screenshot, I consider this a found work, or a work made of found images. Which is why I’ve been looking lately at work by folks like Sherrie Levine and Larry Sultan.
With three exceptions, each of the 55 Street View panoramas in the set is represented by one photograph which includes all portrait elements. The first panorama in the series includes both the walking man and his reflection in the window of the Binnenhof security office, but they are at too wide an angle to include in one screencapture. So the images were extracted separately After sending the book to the printer, I found that another panorama also included a nearly straight-down image of walking man’s legs, which would not fit within the browser window on my laptop monitor. The other exception, below, was just too beautiful to resist, there are so many awesome things going on in this photograph.
walking man proof - 2
This proof copy was created using blurb.com. It’s 120 pages, and includes 57 portrait images and a reference Google Map, and a short introduction to the project. I thought the format might be too big, but it turns out it looks fantastic. The photos are a little dark, but that’s only because most of them were shot in the morning shade. My photos are dark because I shot them inside without a flash.
I am considering a limited print run, including editions reserved for the artist and the photographer, both of whom are currently unidentified.
There are several more shots from the proof on flickr.
Previous, related: How your Street View panoramas are made

The Meaning Of Maps, By Google’s Michael Jones


He’s pretty harsh on unnamed governments who complain about unblurred faces, and got more than a bit of engineer’s arrogance, which is why, I guess, he works for Google, but Michael Jones’s talk, “The Meaning of Maps,”at O’Reilly’s Where conference last week is pretty great.
Maps are not just place, they’re culture. Also, you get to see the Google Trike in action around the 13:00 mark.

Uncle Rudi, Is That You?

ft_uncle_rudi.jpg
Who are the freaks and nerds who call out picayune corrections in newspaper articles? Me, for one.
On a New York Times piece I did once, I changed an entire line during the copyediting process. The piece was much, much better for it, I think, but I got chewed out afterward because, apparently, it required several people staying late to re-layout a whole page, which delayed the closing of the section.
As penance, I’ve been pretty fastidious ever since about quickly slipping the Times’ web editors little corrections–usually of peoples’ names, ex the kind of things that might cause unnecessary embarrassment–for Arts stories. [Oy, in one pseudo-liveblog post from Miami Art Basel, the correspondent misspelled basically every name she dropped. And no, it was not Linda Yablonsky; she is an exquisite name dropper.]
Anyway, last weekend, the Financial Times mentioned the new Gerhard Richter biography in Jackie Wullschlager’s survey of books on German painting. Their whole point was about how loaded Richter’s blurred portraits of his family were, such as Uncle Rudi.
The FT transposed the captions with the Richter and a portrait by Otto Dix. When I tried to do my typical one-click correction, I was surprised to find that the FT doesn’t appear to even publish an address for corrections. Or for reaching the editors.
Setting aside the whole implication that the very idea of being corrected didn’t cross their minds, the whole FT website contact interface turns out to be oriented to subscribers/users and the support of the paid consumption experience.
As such, it has taken a week for me to receive an automated reply, and now my comment had been forwarded to the appropriate department. As the fresh screenshots show, the error remains.