An event on urban data: Beyond the fetish object, toward the social object
UPDATE: Event confirmed for 14th March, 2014. See the final post.
For the past half-decade or so, in a phenomenon most everyone reading this site is no doubt already intimately acquainted with, data-derived artifacts (dynamic visualizations, digital maps, interactive representations of place-specific information, even static “infographics”) have taken increasing prominence in the visual imaginary of mass culture.
We see such images all the time now: broadly speaking, the visual rhetoric associated with them is the animating stuff of everything from car commercials to the weather forecast. The same rhetoric breathes life into election and sports coverage on television, the title sequences of movies, viral Facebook posts and the interactive features on newspaper sites.
Sometimes — in fact, often — these images are deployed as abstract tokens, empty fetishes of futurity, tech-ness, data-ness, evidence-basedness…ultimately, au-courantness. Just as often, and very problematically, they’re used to “prove” things.
But we’ve also begun to see the first inklings of ways in which such artifacts can be used more interestingly, to open up rather than shut down collective discussion around issues of great popular import — to ask its users to consider how and why the state of affairs represented by a given visualization got to be that way, whether that state of affairs is at all OK with them, and what if anything ought to be done to redress it. And this is whether the topic at hand happens to be land use, urban renewal and gentrification, informal housing, the differential consequences of public and privatized mass transit or expenditures in the criminal justice system.
Very few methods of advocacy can convey the consequences of our collective decisions as viscerally as a soundly-designed visualization. (Similarly, if there’s a better way of helping people imagine the spatial implications of alternative policy directions, strategies, investments and allocations, I haven’t stumbled onto it yet, although that certainly blurs the distinction between representing that which does exist and simulating that which does not.) What would happen if such visualizations were consciously and explicitly used as the ground text and point of departure for a moderated deliberative process? Could democracy be done this way? Could this be done at regular intervals? And how might doing so lead to better outcomes (or simply more buy-in) than existing procedures?
There’s plenty of rough precedent for such a notion, albeit scattered across a few different registers of activity:
– A few savvy journalists are starting to use data-based visualizations and maps as the starting point for their more traditional investigative efforts, and the narratives built on them. Visualizations, in this mode, essentially allow unexpected correlations and fact patterns to rise to the surface of awareness, and suggest what questions it might therefore be fruitful for a reporter to ask.
– SeeClickFix, of course, already allows citizens to levy demands on local government bodies, though it doesn’t provide for the organization of autonomous response to the conditions it documents, and it forthrightly positions the objects it represents as problems rather than matters of concern. More proactive and affirmative in its framing is Change By Us, which does emphasize voluntarism, though still with a sense of supplication to (elected or appointed) representatives in government. (The site answers the question “Who’s listening?” by promising that a “network of city leaders is ready to hear your ideas and provide guidance for your projects.”) In any event, both SeeClickFix and Change By Us focus on highly granular, literally pothole- or at most community-garden-scale issues.
– Storefront Democracy, a student project of Kristin Gräfe and (ex-Urbanscaler) Jeff Kirsch, reimagined the front window of a city councillor’s district office as a site where community sentiment on various questions, expressed as votes, could be visualized. Voting is not quite the same thing as democracy, much less deliberation, but the project began to explore ways in which situated representations might be used to catalyze conversations about matters facing the community.
– There are even full-blown technological platforms that promise to enable robust networked democracy, though for all the technology involved this one at least seems to blow right by the potential of visualized states of affairs to serve as focal points for managed dissensus.
Draw out all of those threads, and what do you wind up with? I’m not at all sure, but the question is certainly provocative enough that I want to explore its implications in further depth and detail. Again, I’m interested in digital cartography and interactive representations of data used as the starting point, rather than the product and culmination, of a decision process. My intention is to disturb these things as settled facts, disinter them from the loam of zeitgeisty but near-meaningless infoporn that furnishes more than one glossy coffee-table book, and activate them instead as situated social objects. I think by now it’s clear that data-driven projects like Digital Matatus can furnish people with practical tools to manage the way things are in the city. But can they usefully catalyze conversation about the way things could (or should) be? And can we somehow bundle information about provenance into every representation of data, allowing users to ask how it was gathered, by whom, using what means and for what notional purpose, so they can arrive at their own determinations of its reliability and relevance? All of that remains to be seen.
If you find yourself nodding at any of this — or, indeed, you think it’s all deeply misguided, but nevertheless worth contesting in person — consider this a heads-up that I’ll be convening a one-day seminar on this and related topics at LSE in mid-March, and am looking for qualified speakers beyond my personal orbit and existing friendship circles. If you’re interested in either attending or speaking, please do email me at your earliest convenience at my first initial dot my last name at lse.ac.uk. Limited travel support is available – I have an event budget that allows me to fly in two to three speakers and put you up in Central London for a night, so if you or someone you know is inclined to present I definitely encourage you to get in touch. And let’s see if together we can’t figure out if there’s a thing here or not.
I really want to recommend to you this Olivier Thereaux post about broken bus systems and how they might be fixed (and not just because I happen to be taking the MUNI a great deal lately).
What Olivier absolutely nails is the expression of a thought I’ve come back to again and again over the years: that buses and bus networks are by their nature so intimidating to potential users that many people will do just about anything to avoid engaging them. I don’t mind admitting that, depending on the city, the language in use, and my relative level of energy, I’m definitely to be numbered among those people. When buses are effectively the only mode of public transit available, that “just about anything” has occasionally meant laying out ridiculous sums on taxis; more often, it’s resulted in my walking equally absurd distances across cities I barely know.
“Intimidating,” in this context, doesn’t need to mean “terrifying.” It simply implies that the system is just complicated enough, just hard enough to form a mental model of, that the fear of winding up miles away from your intended destination — and possibly with no clear return route, not enough or the right kind of money to pay for a ticket, and no way of asking for clarification — is a real thing. There’s a threshold of comfort involved, and for quite a few categories of users (the young, the old, visitors, immigrants, people with literacy or other impairments) that threshold is set too high. People in this position wind up seeking alternatives…and if practical alternatives do not exist, they do without mobility altogether. They are lost to the city, and the city is lost to them.
The point is more broadly applicable, as well. You know I believe that cities are connection machines, networks of potential subject to Metcalfe’s law. What this means in the abstract is that the total value of an urban network rises as the square of the number of nodes connected to it. What this means in human terms is that a situation in which people are too intimidated to ride the bus (or walk down the street, or leave the apartment) is a sorrow compounded. Again: everything they could offer the network that is the city is lost. And everything we take for granted about the possibilities and promise of great urban places is foreclosed to them.
If you understand things this way, there’s a clear moral imperative inscribed in the design of systems like bus networks and interfaces. Every incremental thing the designer can do to demystify, explain, clarify, and ultimately to lower the threshold at which a potential user decides the risk of climbing aboard is worth taking does a double service — if the Metcalfe’s law construction of things rings true to you, a geometrical service. You are simultaneously improving the conditions under which an individual lives his or her life, and contributing materially to the commonweal. Not bad for a day’s work, if you ask me.
This is personal for me, too, and not just because I’ve occasionally found a route map overwhelming, or decided to walk from Bloomsbury to Dalston instead of chancing the N38 and winding up in, who knows, Calais. What I’ve come to understand, in these last few years of intense concentration on issues of urban design, is that my fascination with cities grows not at all out of ease or comfort with them, but the opposite. I’m an introvert, I’ve never been comfortable approaching strangers with questions, I’m twitchily hyperaware when I’m inconveniencing others (e.g. holding up a bus by asking questions of a driver) and my gifts for language are not great. Above all, I don’t like looking vulnerable and confused any more than anyone does, especially when traveling.
I’ve gotten better on all these counts over the course of my life, but they’re still issues. They can pop to the surface at any time, and, of course, are more likely to do so under conditions of stress. Taken together, what they spell for me is a relatively circumscribed ability to get around and enjoy the things the cities I visit have to offer — relatively, that is, compared to other able-bodied people my own age and with similar levels of privilege. Even this limitation, though, makes me acutely aware of just how difficult getting around can be, how very intimidating it can all seem, and what both people and place stand to lose each and every single time this intimidation is allowed to govern outcomes.
This is why I believe Olivier is absolutely right to focus on design interventions that reduce user stress, and, with all due respect, it’s why I think people like this Speedbird commenter, who understand cities solely as generators of upside potential, are missing something in the empathy department. There are an awful lot of people, everywhere around us, in every city, who have difficulty negotiating the mobility (and other) systems that are supposed to serve their needs. As far as I’m concerned, anyway, it is the proper and maybe even the primary task of the urban systems designer to work with compassion and fearless empathy to address this difficulty. Only by doing so can we extend the very real promise of that upside potential to the greatest possible number of people who would otherwise be denied it, in part or in full, and only by doing so can we realize in turn the full flowering of what they have to offer us.
Join us in Helsinki on May 22nd for a Touchscapes workshop (updated)
Just in case folks here in town are feeling neglected, fear not: we’re doing events here as well.
As part of Helsinki’s World Design Capital 2010 Ideas Forum, and collaboration with our good friends at Nordkapp, I’m delighted to announce a workshop called “Touchscapes: Toward the next urban ecology.”
Touchscapes is inspired, in large part, by our frustration with the Symbicon/ClearChannel screens currently deployed around Helsinki, how little is being done with them, and how far short of their potential they’ve fallen. Our sense is that we are now surrounded by screens as we move through the city — personal devices, shared interactive surfaces, and now even building-sized displays — and if thinking about how to design for each of these things individually was hard enough, virtually nobody has given much thought to how they function together, as a coherent informational ecosystem.
Until now, that is, because that’s just what we aim to do in the workshop. Join us for a day of activity dedicated to understanding the challenges presented by this swarm of screens, the possibilities they offer for tangible, touch-based interaction, and their implications for the new urban information design. We’ll move back and forth between conceptual thinking and practical doing, developing solid ideas about making the most meaningful use of these emerging resources culturally, commercially, personally and socially.
Attendance is free, but spaces in the workshop are limited, so I recommend you sign up
at Nordkapp on the Facebook event page as soon as you possibly can. See you on the 22nd!
How to bring a Systems/Layers walkshop to your town
Crossposted with Do projects.
The response to the Systems/Layers walkshop we held in Wellington a few months back was tremendously gratifying, and given how much people seem to have gotten out of it we’ve been determined to set up similar events, in cities around the planet, ever since. (Previously on Do, and see participant CJ Wells’s writeup here.)
We’re fairly far along with plans to bring Systems/Layers to Barcelona in June (thanks Chris and Enric!), have just started getting into how we might do it in Taipei (thanks Sophie and TH!), and understand from e-mail inquiries that there’s interest in walkshops in Vancouver and Toronto as well. This is, of course, wonderfully exciting to us, and we’re hoping to learn as much from each of these as we did from Wellington.
What we’ve discovered is that the initial planning stages are significantly smoother if potential sponsors and other partners understand a little bit more about what Systems/Layers is, what it’s for and what people get out of it. The following is a brief summary designed to answer just these questions, and you are more than welcome to use it to raise interest in your part of the world. We’d love to hold walkshops in as many cities as are interested in having them.
Systems/Layers is a half-day “walkshop,” held in two parts. The first portion of the activity is dedicated to a slow and considered walk through a reasonably dense and built-up section of the city at hand. What we’re looking for are appearances of the networked digital in the physical, and vice versa: apertures through which the things that happen in the real world drive the “network weather,” and contexts in which that weather affects what people see, confront and are able to do.
Participants are asked to pay particular attention to:
– Places where information is being collected by the network.
– Places where networked information is being displayed.
– Places where networked information is being acted upon, either by people directly, or by physical systems that affect the choices people have available to them.
You’ll want to bring seasonally-appropriate clothing, good comfortable shoes, and a camera. We’ll provide maps of “the box,” the area through which we’ll be walking.
This portion of the day will take around 90 minutes, after which we gather in a convenient “command post” to map, review and discuss the things we’ve encountered. We allot an hour for this, but since we’re inclined to choose a command post offering reasonably-priced food and drink, discussion can go on as long as participants feel like hanging out.
Do projects’ Nurri Kim and Adam Greenfield plan and run the workshop, with the assistance of a qualified local expert/maven/mayor. (In Wellington, Tom Beard did a splendid job of this, for which we remain grateful.)
We feel the walkshop works best if it’s limited to roughly 30 participants in total, split into two teams for the walking segment and reunited for the discussion.
In order for us to bring Systems/Layers to your town, we need the sponsorship of a local arts, architecture or urbanist organization — generally, but not necessarily, a non-profit. They’ll cover the cost of our travel and accommodation, and defray these expenses by charging for participation in the walkshop. In turn, we’ll ensure both that the registration fee remains reasonable, and that one or two scholarship places are available for those who absolutely cannot afford to participate otherwise.
If you’re a representative of such an organization, and you’re interested in us putting on a Systems/Layers walkshop in your area, please get in touch. If you’re not, but you still want us to come, you could try to put together enough participants who are willing to register and pay ahead of time, so we could book flights and hotels. But really, we’ve found that the best way to do things is to approach a local gallery, community group or NGO and ask them to sponsor the event.
At least as we have it set up now, you should know that we’re not financially compensated in any way for our organization of these walkshops, beyond having our travel, accommodation and transfer expenses covered.
Our schedule tends to fill up 4-6 months ahead of time, so we’re already talking about events in the (Northern Hemisphere) spring of 2011. And of course, it’s generally cheapest to book flights and hotels well in advance. If you think Systems/Layers would be a good fit for your city, please do get in touch as soon as you possibly can. As we’ve mentioned, we’d be thrilled to work with you, and look forward to hearing from you with genuine anticipation and excitement. Wellington was amazing, Barcelona is shaping up to be pretty special, and Taipei, if we can pull it off, will be awesome. It’d mean a lot to us to add your city to this list. Thanks!
Transmobility, part II
Part II of our exploration of transmobility. I want to caution you, again, that this is very much a probe.
Perhaps it’s best to start by backing up a few steps and explaining a little better what I’m trying to do here. What I’m arguing is that the simple act of getting around the city is in the process of changing — as how could it not, when both paths themselves and the vehicles that travel them are becoming endowed with the power to sense and adapt?
Accordingly, I believe we need to conceive of a networked mobility, a transmobility: one that inherently encompasses different modes, that conceptualizes urban space as a field to be traversed and provides for the maximum number of pathways through that field, that gathers up and utilizes whatever resources are available, and that delivers this potential to people in terms they understand.
Yesterday, I posed the question as to how we might devise a transmobility that met all of these conditions, while at the same time acknowledging two additional, all-but-contradictory desiderata. These were the desire, on the one hand, to smoothen out our interactions with transit infrastructure until vehicular transportation becomes as natural as putting one foot in front of another, and on the other to fracture journeys along their length such that any arbitrary point can become a node of experience and appreciation in and of itself. Any system capable of meeting these objectives would clearly present us with a limit case…but then, I believe that limits are there to be approached.
Finally, I’m addressing all of these questions from a relatively unusual disciplinary perspective, which is that of the service, interaction or experience designer. The downside of this is that I’m all but certainly disinterring matters a professional transit planner or mobility designer would regard as settled questions, while missing the terms of art or clever hacks they would call upon as second nature. But there’s a significant upside, too, which is that I’m natively conversant with the interactive systems that will increasingly condition any discussion of mobility, both respectful of their power and professionally wary of the representations of reality that reach us through them.
So petrified, the landscape grows
In addressing the questions I posed yesterday, then, I’m inclined to start by holding up for examination some of the ways in which trips, routes and journeys are currently represented by networked artifacts. Maybe there’s something that can be gleaned from these practices, whether as useful insights or musts-to-avoid.
I would start by suggesting that the proper unit of analysis for any consideration of movement through urban space has to be the whole journey. This means grasping the seemingly obvious fact that from the user’s perspective, all movement from origin to destination comprises a single, coherent journey, no matter how many times a change from mode to mode is required.
I say “seemingly obvious,” because the interactive artifacts I’m familiar with generally haven’t represented circumstances this way.
Take a simple example: a trip that involves walking to the nearest bus stop, riding the bus downtown, and finally walking from the point you alight from the bus to your ultimate destination. Some of the more supple route-planning applications already capture this kind of utterly normal experience — HopStop, for example, is quite good, at least in New York City — but you’d be surprised how many still do not. To date, they’ve tended to treat journeys in terms solely of their discrete component segments: an in-car GPS system plots automotive routes, a transit route-planner provides for trips from station to station, and so on.
But people think about movements through the city in terms that are simultaneously more personal and more holistic. We think of getting to work, stopping off to pick up a few things for dinner on the way home, or heading crosstown to meet friends for drinks.
So contemporary representations already seem well-suited to one of our criteria, in that the seams between methods of getting around are stark and clear, and perhaps even stark and clear enough to imply the self-directed moments of experience that attend a journey on either side. As far as a GPS display is generally concerned, what happens in the car stays in the car, and what happens next is up to you.
Certainly as compared to some overweening, totalizing system that aimed at doing everything and wound up doing none of it well, there’s something refreshing about this humility of ambition. On the other hand, though, such systems manifestly do not lend themselves well to depicting an important variety of end-to-end trips through the city, which are those trips that involve one or more changes of conveyance.
Think back to our rudimentary example, above. It would be useful if, for the portion of the journey on which you take the bus, that bus “understood” that it was essentially functioning as a connector, a linkage between one segment traversed on foot and another.
And this is still truer of journeys involving intermodal junctures where both traffic and the systemic requirements of timetables and schedules permit you less freedom in planning than walking or cycling might. Such journey plans need to be adjusted on the fly, drawing in data from other sources to accurately account for unfolding events as they happen, with signaling carried through to the infrastructure itself so that some delay, misrouting or rupture in the original plan results in the traveler being offered a panoply of appropriate alternatives.
What if, instead of living with the vehicle, the representational system lived with the traveler, and could move with them across and between modes? On this count, we’re obviously most of the way there already: with turn-by-turn directions provided by Google Maps, the iPhone and its Android-equipped competitors spell howling doom for the single-purpose devices offered by Garmin and TomTom. The emergence of truly ambient approaches to informatic provisioning would guarantee that a traveler never lacked for situational awareness, whether or not they had access to personal devices at any given moment.
What if we could provide these systems with enough local intelligence to “know” that a specified endpoint offers n possibilities for onward travel? What if this intelligence was informed by a city’s mesh of active public objects, so that travel times and schedules and real-time conditions could all be taken into account? And finally, instead of presenting journey segments as self-contained, what if we treated them as if they enjoyed magnet physics?
Then, should you want (or be forced by exigencies beyond your control) to alter your travel plans, you could snap out the mode you’re currently using, and swap in another that met whatever bounding constraints you specified, whether those had to do with speed or accessibility or privacy or shelter from the weather. The RATP‘s head of Prospective and Innovative Design, Georges Amar, speaks of enabling transmodality, and this is just what we begin to approach here.
The distinction I’m trying to capture is essentially the same as that Lucy Suchman drew between global, a priori plans on the one hand and situated actions on the other. The result would be a more responsive journey-planning system that, given any set of coordinates in space and time, is capable of popping its head up, having a look around and helping you determine what your best options are.
Moments in modal culture
This isn’t to say that we don’t also conceive of mobility in terms of particular modes of travel, and all the allegiances and affinities they give rise to. As Ivan Illich put it, “Tell me how fast you go, and I’ll tell you who you are.”
It’s not simply the coarser distinctions that tell, either. These shades of meaning and interpretation are crucial even among and between people who share a mode of transport: a fixie rider self-evidently has a different conception of the human-bicycle mesh than a Brompton fan does, while New Yorkers will know perfectly well what I mean if I distinguish two friends by describing them respectively as a 6 train rider and a 7 type. (Though not directly analogous, you can summon up similar images by evoking the L Taraval versus the J Church, the Yamanote-sen against the Hibiya-sen, or the 73 bus against the 15.)
Those of us who ride public transit form personal connections with our stops, our stations and even with particular linkages between lines, and I can only imagine that both our cities and our lives would be impoverished if we gave that up. But there’s no particular reason we need to; all I’m suggesting here is that the total journey needs to be represented as such by all the networked systems traversed in the course of a given outing.
Neither, in devising our transmobility system, can we afford to neglect the specificities and particularities of the component systems that furnish us with its articulated linkages. If one train line isn’t interchangeable with another in the hearts and minds of their riders, the same is true of other kinds of frameworks.
For example, we can’t merely plug some abstract shared bicycle service into the mesh of modal enablers and call it a day. Consider the differing fates of two apparently similar bike-share networks, the Parisian Vélib and Barcelona’s Bicing. In their diverging histories, we can see how differences in business model wind up percolating upward to impact level of service. By limiting the right to use Bicing to residents, by requiring that users open accounts, and having those accounts tied in to the usual variety of identification data, the system provides would-be bad actors with a strong disincentive. You’re personally liable, accountable…responsible.
There are real and problematic downsides to this approach, but the difference this set of decisions makes on the street is immediate and obvious. A rank of Vélib bikes, even in a posh neighborhood, looks like a bicyclical charnelhouse, with maybe three or four out of every five saddles reversed, in what has become Parisians’ folk indicator to one another that a particular bike is damaged to the point that it’s unavailable for use. The Bicing installations that I saw, including ones seeing very heavy use in core commercial districts, aren’t nearly as degraded.
This goes to the point I was trying to make, earlier, by contrasting the older conception of a vehicle as an object to the emergent way of understanding it as a service. Even though they may be physically identical — may draw current from the same grid, may be housed in the same lot, may present the driver with the selfsame control interface — a ZipCar Prius doesn’t function in just exactly the same way as a City CarShare Prius does. You could design a transmobility system so it accounted for either or (preferably) both…but not interchangeably.
Again, though I want to enable smooth transitions, I’m not arguing for perfect seamlessness in transit, or anything like it. Kevin Lynch reminds us, in The Image of the City, that “[a]ny breaks in transportation — nodes, decision points — are places of intensified perception.” We ought to welcome some of this heightened awareness, as a counterpoint to the automaticity that can all too easily accompany the rhythms of transit ridership, especially when experienced on a daily or twice-daily basis. On the other hand, it’s true that some of this “intensified perception” is almost certainly down to the anxiety that attends any such decision under circumstances of time pressure, human density and the urgent necessity to perform modal transitions correctly — and this is the fraction I’d argue we’d be better off designing out of transmobility.
At most, I mean for transmobility systems to bolster, not replace, human intuition. Where alternative modes or routings exist, we’re already generally pretty good at using them tactically to optimize against one or another criterion. Sometimes you know the subway’s the only way you can possibly beat the gridlock and get to your appointment on time; other times you choose a taxi instead, because you need to arrive at a meeting looking fresh and composed. One day you have the time to take the bus and daydream your way downtown, and the next it doesn’t get you nearly close enough to where you need to be.
You know this, I know this. So if we’re going to propose any technical intervention at all, it had better be something that builds on our native nous for the city, not overwrites it with autistic AI.
And before we can even begin to speak credibly of integrated mobility services, we’d need to see existing systems display some awareness of the plenitude of alternatives travelers have available to them, some understanding of all the different real-time factors likely to influence journey planning.
To take the most basic example, journey planning for walkers requires a different kind of thinking about the city than, particularly, turn-by-turn directions for drivers. This isn’t simply for the obvious reasons, like car-centric routings that represent a neighborhood as a an impenetrable thicket, a maze of one-way streets all alike, that a walker would stroll on through placidly and unconcernedly.
It’s because, as thinkers from Reyner Banham to Jane Jacobs and Kevin Lynch to Ivan Illich have reminded us — and as anyone who’s ever ridden in a car already understands quite perfectly well — velocity is something like destiny. You simply attend to different cues as a walker than you do as a driver, you notice textures of a different gauge, different things matter. And of course the same thing is true for cyclists vis à vis both walkers and drivers.
Over the past eighteen months, I’ve finally seen some first sentinel signs of this recognition trickle into consumer-grade interactive systems, but we’ve still got a long, long way to go.
A final step would be to design the built environment itself, the ground against which all journeys transpire, to accommodate transmobility. Why wouldn’t you, at least, plan and design buildings, street furniture and other hard infrastructure so they account for the fact of networked mobility services — both in terms of the hardware that underwrites their provision, and of the potential for variability, dynamism, and open-endedness they bring to the built landscape?
In other words: why shouldn’t a bus shelter be designed with a mobile application in mind, and vice versa? Why shouldn’t both be planned so as to take into account the vehicles and embedded sensors connected to the same network? When are we finally going to take this word “network” at face value?
Of course these technologies change — over time they get lighter, more powerful, cheaper. That’s why you design things to be easy-access, easily extensible, as modular as can be: so you can swap out the CAT5 cable and spool in CAT6 (or replace it with a WiMax transponder, or whatever). Nobody’s recommending that we ought to be hard-wiring the precise state of the art as it existed last Tuesday morning into our urban infrastructure. But anyone in a position of power who, going forward, greenlights the development of such infrastructures without ensuring their ability to accommodate networked digital interaction ought to be called to account by constituents at the very next opportunity.
You know I believe that we used to call “ubiquitous computing” is now, simply, real life. Anybody who cares about cities and the people who live in them can no longer afford to treat pervasively networked informatic systems as a novelty, or even a point of municipal distinction. It’s always hard to estimate and account for, let alone attach precise dollar figures to, missed opportunities, to count the spectral fruits of paths not taken. But given how intimate the relationship between an individual’s ability to get around and a region’s economic competitiveness is known to be, there is no excuse for not pursuing advantage through the adroit use of networked systems to enhance individual and collective mobility.
What we ought to be designing are systems that allow people to compose coherent journeys, working from whatever parameters make most sense to them. We need to be asking ourselves how movement through urban space will express itself (and be experienced as travelers as a cohesive experience) across the various modes, nodes and couplings that will necessarily be involved.
The challenge before us remains integrating this tangle of pressures, constraints, opportunities and affordances into coherent user-facing propositions, ones that would offer people smoother, more flexible, more graceful and more finely-grained control over their movements through urban space. Then we could, perhaps, begin to speak of a true transmobility.
Frameworks for citizen responsiveness, enhanced: Toward a read/write urbanism
We’ve been talking a little bit about what we might gain if we begin to conceive of cities, for some limited purposes anyway, as software under active development. So far, we’ve largely positioned such tools as a backstop against the inevitable defaults, breakdowns and ruptures that municipal services are heir to: a way to ensure that when failures arise, they’ll get identified as quickly as possible, assessed as to severity, brought to the attention of the relevant agencies, and flagged for follow-up.
And as useful, and even inspiring, as this might be, to my mind it doesn’t go nearly far enough. It’s essentially the lamination together of some entirely conventional systems, provisions and practices — something that already exists in its component pieces, something, as Bruce points out here, that’s “not even impossible.”
But what if we did take a single step further out? What if we imagined that the citizen-responsiveness system we’ve designed lives in a dense mesh of active, communicating public objects? Then the framework we’ve already deployed becomes something very different. To use another metaphor from the world of information technology, it begins to look a whole lot like an operating system for cities.
Provided that, we can treat the things we encounter in urban environments as system resources, rather than a mute collection of disarticulated buildings, vehicles, sewers and sidewalks. One prospect that seems fairly straightforward is letting these resources report on their own status. Information about failures would propagate not merely to other objects on the network but reach you and me as well, in terms we can relate to, via the provisions we’ve made for issue-tracking.
And because our own human senses are still so much better at spotting emergent situations than their machinic counterparts, and will probably be for quite some time yet to come, there’s no reason to leave this all up to automation. The interface would have to be thoughtfully and carefully designed to account for the inevitable bored teenagers, drunks, and randomly questing fingers of four-year-olds, but what I have in mind is something like, “Tap here to report a problem with this bus shelter.”
In order for anything like this scheme to work, public objects would need to have a few core qualities, qualities I’ve often described as making them “addressable, queryable, and even potentially scriptable.” What does this mean?
– Addressability. In order to bring urban environments fully into the networked fold, we would first need to endow each of the discrete things we’ve defined as public objects with its own unique identifier, or address. It’s an ideal application for IPv6, the next-generation Internet Protocol, which I described in Everyware as opening up truly abyssal reaches of address space. Despite the necessity of reserving nigh-endless blocks of potentially valid addresses for housekeeping, IPv6 still offers us a ludicrous freedom in this regard; we could quite literally assign every cobblestone, traffic light and street sign on the planet a few million addresses.
It’s true that this is overkill if all you need is a unique identifier. If all you’re looking to do is specify the east-facing traffic signal at the northeast corner of 34th Street and Lexington Avenue, you can do that right now, with barcodes or RFID tags or what-have-you. You only need to resort to IPv6 addressability if your intention is to turn such objects into active network nodes. But as I’ve argued in other contexts, the cost of doing this is so low that any potential future ROI whatsoever justifies the effort.
– Queryability. Once you’ve got some method of reliably identifying things and distinguishing them from others, a sensitively-designed API allows us to pull information off of them in a meaningful, structured way, either making use of that information ourselves or passing it on to other systems and services.
We’ve so far confined our discussion to things in the public domain, but by defining open interoperability standards (and mandating the creation of a critical mass of compliant objects), the hope is that people will add resources they own and control to the network, too. This would offer incredibly finely-grained, near-realtime reads on the state of a city and the events unfolding there. Not merely, in other words, to report that this restaurant is open, but which seats at which tables are occupied, and for how long this has been the case; not merely where a private vehicle charging station is, but how long the current waits are.
Mark my words: given only the proper tools, and especially a well-designed software development kit, people will build the most incredible ecology of bespoke services on data like this. If you’re impressed by the sudden blossoming of iPhone apps, wait until you see what people come up with when they can query stadium parking lots and weather stations and bike racks and reservoir levels and wait times at the TKTS stand. You get the idea. (Some of these tools already exist: take a look at Pachube, for example.)
– And finally scriptability, by which I mean the ability to push instructions back to connected resources. This is obviously a delicate matter: depending on the object in question, it’s not always going to be appropriate or desirable to offer open scriptability. You probably want to give emergency-services vehicles the ability to override traffic signals, in other words, but not the spotty kid in the riced-out WRX. It’s also undeniable that connecting pieces of critical infrastructure to an open network increases the system’s overall vulnerability — what hackers call its “attack surface” — many, many times. If every exit is an entrance somewhere else, every aperture through which the network speaks itself is also a way in.
We should all be very clear, right up front, that this is a nontrivial risk. I’ll make it explicit: any such scheme as the one sketched out here presents the specter of warfare by cybersabotage, stealthy infrastructure attrition or subversion, and the depredations of random Saturday-night griefers. It’s also true that connected systems are vulnerable to cascading failures in ways non-coupled systems cannot ever be. Yes, yes and yes. It’s my argument that over anything but the very shortest term, the advantages to be derived from so doing will outweigh the drawbacks and occasional catastrophes — even fatal ones. But as my architect friends say, this is above all something that must be “verified in field,” validated empirically and held up to the most rigorous standards.
What do we get in return for embracing this nontrivial risk? We get a supple, adaptive interface to the urban fabric itself, something that allows us not just to nail down problems, but to identify and exploit opportunities. Armed with that, I can see no upward limit on how creative, vibrant, imaginative and productive twenty-first century urban life can be, even under the horrendous constraints I believe we’re going to face, and are perhaps already beginning to get a taste of.
Stolidly useful, “sustainable,” justifiable on the most gimlet-eyed considerations of ROI, environmental benefit and TCO? Sure. But I think we should be buckling ourselves in, because first and foremost, read/write urbanism is going to be a blast.
As far as I can tell, the phrase “ultra mapping” originates with this Wired UK article on our friends at Stamen and their recent activities in London. It sure sounds like a Stamenism, and it beautifully describes what they do. But as I turn the phrase over in my mouth (and in so doing, decide it really ought to be a single word), I’ve come to think it actually refers to something even bigger than that, a truly epochal change that we and our maps are living through together.
I’m sure cartographers and people in the geography community have been all over this, possibly even in so many words, but I believe we’re right now experiencing the most significant single evolution in mapping since someone first scratched plans on papyrus. One relatively recent and very simple intervention, made possible by the lamination together of three or four different kinds of technology, has completely changed what a map is, what it means, what we can do with it.
It’s this: that for the very first time in human history, our maps tell us where we are on them.
The fact that such depictions can now also render layers of dynamic, real-time situational information seems almost incidental to me compared to this. This one development subtly but decisively removes the locative artifacts we use from the order of abstraction. By finding ourselves situated on the plane of a given map, we’re being presented with the implication that this document is less a diagram and more a direct representation of reality — and, what’s more, one with a certain degree of fidelity, one that can be verified empirically by the simple act of walking around. How is that not epochal?
I’d argue that this begins to color our experience of all maps, even those that remain purely imaginary. We begin to look for the pulsing crosshairs or the shiny, cartoony pushpin that say YOU ARE HERE. The ability to locate oneself becomes bound up with the meaning of any representation of space whatsoever.
Now bring all the Stameny goodness implied by dynamic visualization back into the picture: all those routinely gorgeous renderings of subway ridership or crime or air quality imply something very different when you can either find yourself within their ambit or cannot. At its rawest, the suggestion is this: either these issues affect me, or they do not. And this is true even if what is being mapped is a purely historical event. The implication is there, however faint.
I’ve been a map fan all my life. I must have spent literally hundred of hours poring over various representations of place real and imagined, from the AAA TripTiks and Guides Michelin that used to litter the family car, to the Middle-Earth and Ringworld charts that so awed me when I was nine (“contour interval violated on Fist-of-God”), to the land-navigation block of the Army’s Primary Leadership Development Course (repeat after me: “a line drawing, to scale, of a portion of the Earth’s surface as seen from above”).
Nothing in all that, though, prepared me for the frisson of holding an iPhone in my hand for the first time, launching Google Maps, pressing a single button…and being located, told where I was to within a couple of meters. It’s a real epistemic break, isn’t it? Those who come after us will have a hard time imagining that there was ever such a thing as a map that couldn’t do that.
The City Is Here For You To Use: (very) provisional bibliography
A week or so back, a bright guy I met at PICNIC named Lincoln Schatz asked me if I mightn’t list for him a few things I’d been reading lately. I got about halfway through before I realized that I was really compiling a manifest of books I’d been consulting as I put together the pieces of my own.
So this is for you, Lincoln – but I bet it’d also be particularly valuable for readers who are coming at issues of networked urbanism from the information-technological side, and would like a better grounding in sociological, psychological, political and architectural thinking on these topics. (There’s also a pretty heavy overlap here with the curriculum Kevin Slavin and I built our ITP “Urban Computing” class around.)
Not all of these were equally useful, mind you. Some of the titles on the following list are perennial favorites of mine, or works I otherwise regard as essential; some are badly dated, and one or two are outright wank. But they’ve all contributed in some wise to my understanding of networked place and the possibilities it presents for the people who inhabit it.
Two caveats: first, this is very far from a comprehensive list, and secondly, you should know that I’ve provided the titles with Amazon referral links, so I make a few pennies if you should happen to click through and buy anything (for which I thank you). At any rate, I hope you find it useful.
UPDATE 19 October 20.49 EEDT
Thanks, everyone, for the suggestions. Please do bear in mind that, as I noted, this is not a comprehensive list of interesting urbanist books, but an attempt to account specifically for those works that have been influential on my own thinking. With a very few exceptions, I’m no longer looking for new insights, but for ways to consolidate and express those deriving from my encounter with the works listed.
That said, I’ll continue to update the page as I either remember titles that ought to have been included in the first place, or in fact do assimilate new points of view.
– Alexander, Christopher, et al.: A Pattern Language
– Ascher, Kate: The Works: Anatomy of a City
– Augé, Marc: Non-Places: Introduction to an Anthropology of Supermodernity
– Aymonino, Aldo and Valerio Paolo Mosco: Contemporary Public Space/Un-Volumetric Architecture
– BAVO, eds.: Urban Politics Now: Re-Imagining Democracy in the Neoliberal City
– Bachelard, Gaston: The Poetics of Space
– Baines, Phil and Catherine Dixon: Signs: Lettering in the Environment
– Banham, Reyner: The Architecture of the Well-Tempered Environment
– Benjamin, Walter: Selections from The Arcades Project
– Benkler, Yochai: The Wealth of Networks: How Social Production Transforms Markets and Freedom
– Borden, Iain: Skateboarding, Space and the City
– Brand, Stewart: How Buildings Learn
– Canetti, Elias: Crowds and Power
– Careri, Francesco: Walkscapes: Walking as an Aesthetic Practice
– Carter, Paul: Repressed Spaces
– Crawford, J.H.: Carfree Cities
– Davis, Mike: Planet of Slums
– De Cauter, Lieven: The Capsular Civilization
– De Certeau, Michel: Chapter VII, “Walking in the City,” from The Practice of Everyday Life
– DeLanda, Manuel: Part I, “Lavas and Magmas,” from A Thousand Years of Nonlinear History
– Design Trust For Public Space: Taxi 07: Roads Forward
– Di Cicco, Pier Giorgio: Municipal Mind: Manifestos for the Creative City
– Dourish, Paul: Where The Action Is
– Flusty, Steven: Building Paranoia
– Fruin, John J.: Pedestrian Planning and Design
– Gehl, Jan: Life Between Buildings: Using Public Space
– Goffman, Erving:
• Behavior in Public Places
• Interaction Ritual
– Graham, Stephen and Simon Marvin: Splintering Urbanism
– Greenfield, Adam (that’s me!): Everyware: The Dawning Age of Ubiquitous Computing
– Hall, Edward T.: The Hidden Dimension
– Hammett, Jerilou and Kingsley, eds.: The Suburbanization of New York
– Hara, Kenya: Designing Design
– Hardt, Michael and Antonio Negri: Empire
– Haydn, Florian and Robert Temel, eds.: Temporary Urban Spaces
– Holl, Steven, Juhani Pallasmaa and Alberto Pérez-Gómez: Questions of Perception
– Hughes, Jonathan and Simon Sadler, eds.: Non-Plan
– Ito, Mizuko, Daisuke Okabe, and Ken Anderson: “Portable Objects in Three Global Cities: The Personalization of Urban Places”
– Iwamoto, Lisa: Digital Fabrications
– Jacobs, Jane: The Death and Life of Great American Cities
– Kaijima, Momoyo, Junzo Koroda and Yoshiharu Tsukamoto: Made in Tokyo
– Kay, Alan: “User Interface: A Personal View,” in The art of human-computer interface design (Laurel, ed.)
– Kayden, Jerold S.: Privately Owned Public Space: The New York City Experience
– Kieran, Stephen and James Timberlake: Refabricating Architecture
– Klingmann, Anna: Brandscapes: Architecture in the Experience Economy
– Klooster, Thorsten, ed.: Smart Surfaces and their Application in Architecture and Design
– Latour, Bruno:
• Aramis, or: The Love of Technology
• Reassembling the Social
– Lefebvre, Henri: The Production of Space
– Lynch, Kevin: The Image Of The City
– McCullough, Malcolm: Digital Ground
– Mollerup, Per: Wayshowing: A Guide to Environmental Signage Principles and Practices
– Miller, Kristine F.: Designs on the Public
– Mitchell, William J.:
• City of Bits
• Me++: The Cyborg Self and the Networked City
– Moran, Joe: Reading the Everyday
– Mumford, Lewis: The City In History
– MVRDV: Metacity/Datatown
– Neuwirth, Robert: Shadow Cities: A Billion Squatters, A New Urban World
– Nold, Christian, ed.: Emotional Cartography: Technologies of the Self
– O’Hara, Kenton, et al., eds.: Public and Situated Displays: Social and Interactional Aspects of Shared Display Technologies
– Oldenburg, Ray: The Great Good Place
– Qiu, Jack Linchuan: Working Class Network Society
– Raban, Jonathan: Soft City
– RAMTV: Negotiate My Boundary
– Rheingold, Howard: Smart Mobs
– Rudofsky, Bernard: Streets for People
– Sadler, Simon: Archigram: Architecture without Architecture
– Sante, Luc: Low Life
– Sennett, Richard: The Uses of Disorder
– Senseable City Lab: New York Talk Exchange
– Solnit, Rebecca: Wanderlust: A History Of Walking
– Suchman, Lucy: Plans and Situated Actions
– Tuan, Yi-Fu: Space and Place
– Varnelis, Kazys, ed.: The Infrastructural City
– Wall, Alex: Victor Gruen: From Urban Shop to New City
– Waldheim, Charles, ed.: The Landscape Urbanism Reader
– Watkins, Susan M.: Clothing: The Portable Environment
– Whitely, Nigel: Reyner Banham: Historian of the Immediate Future
– Whyte, William H.: The Social Life of Small Urban Spaces
– Wood, Denis and Robert J. Beck: Home Rules
– Zardini, Mirko, ed.: Sense Of The City: An Alternate Approach to Urbanism
Being discussed now