Wellington

Wellington: Notes on that Newsroom NZ Piece (updated)

Posted on October 1, 2018 in Journalism, Wellington

According to Newsroom NZ’s Simon Louisson, I am “the US Consultant behind the Wellington bus nightmare.” Wellington, New Zealand is having some problems with recent bus service changes. I have had no role in Wellington for the last six years, and did not even know the service changes were happening until I read about them in the media, but I, being a foreigner, must be to blame!

Jarrett Walker, the US consultant that has united Wellingtonians in their loathing for the chaotic new bus network, has also redesigned Dublin’s network and has met an even more rigorous negative response.

The entire article is false and defamatory, so if you read it, please also read this.

Through my employer at the time, the Australian firm MRCagney, I did a project for the Greater Wellington Regional Council on the design of the bus network in Wellington (the city only). This work was mostly in 2011, ending in early ’12. My role ended with the completion of the draft network plan. I had no role in how the plan was presented to the public, and when that didn’t go well in 2012, I assumed it was dead. That is always a possible and valid outcome of a public consultation process.

This year, a somewhat similar plan was implemented without my knowledge and involvement. The implementation has not gone well, for a variety of reasons, most of them not related to the network design. One of the big ones was a decision to switch operating companies at the same time in a way that changed the drivers’ working conditions, something I always advise against.

At it happens, my role in Wellington was exactly the same as my role in the Auckland redesign, which has been rolled out over the last several years to great success. In Auckland, too, I led the original design process six years ago, then had no further role except to offer encouragement.

But no facts will prevent Newsroom NZ from constructing me as a cartoon villain, through an astonishing series of blatant falsehoods about who I am and what I believe.

Jarrett Walker, head of JWA, is one of America’s foremost advocates of public transport over cars, but he sees the intense reactions of Wellingtonians and Dubliners as a welcome part of the process. His stance opposing ride-sharing has led Tesla manufacturer Elon Musk to call him “a sanctimonious idiot”.

My exchange with Elon Musk had nothing to do with ride-sharing. It was about Musk’s insulting and ignorant comments about public transport which I identified as an example of elite projection. And while it’s true that I anticipate negative feedback on my plans, that doesn’t mean my goal is to make people upset, as he seems to imply here. All I have said, in many ways, is what every politician knows: Changing anything will upset some people.

In paragraph after paragraph, Mr Louisson wanders around the internet finding things I wrote that sound vaguely incriminating to him, and uses these to construct false descriptions of my views:

Walker takes a very binary view of change. In his blog he says cities should either totally revamp a network or leave it as it is.

That appears to be a perversion of this post, which points out that network plans have a degree of interdependence that limits how much they can be revised without falling apart. People who need me to be a villain imagine me saying “my way or the highway,” which is nonsense. Plans get revised a lot through public consultation, and that’s a good thing.

And anyone who knows me will burst out laughing at this:

His company, Jarrett Walker [and] Associates, is very comfortable with the neo-liberal mantra of user-pays, and a strong commercial imperative underlies much of its design work.

Bonus points if you can figure out what text of mine was misread to fabricate this, because I can’t think of one. I have always advocated heavy state subsidy of public transport. As for commercial, that’s a confusing term that I never use myself, because it gives the impression that the only reason to serve lots of people is greed. (Tip: Sometimes you do it because you want to improve lots of people’s lives.) And even so, of course, I don’t bring an imperative to carry lots of people, because I encourage each city to think about the ridership-coverage tradeoff.

Mr Louisson formed all these insights without interviewing me, but you won’t find out why unless you get to paragraph 28:

Asked to comment on the implementation of the Wellington redesign, Walker seemed at pains to distance himself, saying in an email, “Unfortunately, I have not had any role in Wellington since 2012, and have not had time to study recent events there closely enough to have an opinion.”
While JWA’s work had involved developing a network redesign proposal, “I had no role in the public consultation at that time or in anything that has occurred since.”

My quoted words are indeed the only words I sent to Mr Louisson. I was trying to establish that it would not be interesting to interview me, because I could tell him nothing about what had happened to transit in his city in the last six years.

Does this make me “behind” a revised plan, implemented without my involvement or even my knowledge six years later? And does my unwillingness to comment on something I know nothing about license a reporter to just make up stories about who I am and what I believe?

Remember, if you don’t want your name dragged through the dirt in the media, it’s an easy thing to avoid: Say nothing. Do nothing. Propose nothing. Change nothing.

That’s why nothing gets done.

wellington: some sharp (and critical, and nice) comments on our network plan

Posted on March 12, 2012 in Wellington

Wellington readers: Here’s a remarkably thoughtful piece (and not just because it quotes me) on the network plan that I worked on. It’s also cross posted here. Attached are a few comments that people like me live for. For example:

The proposed changes to service to my corner in Brooklyn will have a revolutionary effect on my life, essentially making public transport a viable option, where it is not right now. I am quite excited and hope these changes go through.

You’d be surprised how touching this sort of comment can be to a network designer, even one who’s been in the transit trenches for 20 years. It really is all about humans.

dissent of the week: trolley buses in wrong place vs motor buses in right one

Posted on March 7, 2012 in Trolleybuses, Wellington

In a network redesign for Wellington, New Zealand that I led last year, we assumed that it was more important to design the network around customer needs than to maximize the use of trolley buses. So we designed some routes that run partly under trolleywire and partly not, and that are therefore to be run (for now) by motorbuses. A study of the future of trolley buses in Wellington is soon to begin, but as I said in my last post on the subject, they wanted their trolleybus policy to follow from the city's transport network, rather than preceding and constraining it.

One commenter said this was the wrong priority:

"This seems unwise to me. The benefits of trolleybuses are so great that it would often be better to run a trolleybus on a somewhat suboptimal route than a motorbus on a more optimal one. Thus any proposed routes or route changes should absolutely take into account the political and technical feasibility of operating the new routes with trolleybuses.

I am fairly familiar with the large trolleybus networks of San Francisco and Vancouver, and both have stretches of trolley wire that are no longer used much because the bus route underneath them had ceased to make sense as part of the larger network. But I can also think of examples where buses still do pretty weird and possibly obsolete things so that they can stay on trolleywire. Seattle's network, for example, is much more wire-constrained overall. (A Seattle network designed without wire in mind, for example, would almost certainly make it easier to access Queen Anne Hill from the north.

Because trolleybuses boomed in the 1940s-60s but then stagnated, most trolleybus lines in North America (and New Zealand) have been unchanged for 50 years or more, while the city has grown and changed around them. As a city's demand expands, and especially as it grows more multidirectional, routes need to either extend or be revised to fit a new structure that meets the new needs. Trolley wire can become an obstacle to doing that.

Vancouver's 41st Avenue the clearest example. Today, almost all service at the west end of this busy transit corridor extends to the University of British Columbia, about 7 km beyond where the trolley wire ends. UBC is now a superpower ridership source at almost all times of day. Should trolleywire be extended the rest of the way? Quite possibly, but right now, it would be absured to run 41st Avenue buses ending 7 km short of the university just because the wire ends there.

I certainly believe in the long term future of trolleybuses as part of both an emissions strategy and as protection against fossil fuel cost volatility, but sometimes the existing wire is just in the wrong place. Argue for more wire, yes, but meanwhile, should we just treat the trolleybuses as separate and inviolable, no matter how obsolete or problematic their routes become?

wellington: responding to environmentalist critiques of a network plan

Posted on February 27, 2012 in Wellington

I spent much of 2011 leading a major study for Greater Wellington Regional Council, which developed a proposed new bus network for New Zealand's national capital. The resulting proposal re-allocates existing resources to create a much more extensive network of high-frequency all-day service, so as to expand the area in which transit can be used spontaneously for all of life's needs. This kind of extreme convenience is essential to reach a range of sustainability outcomes, notably by making it much easier for someone to chose to own fewer cars.

A remarkable outcome of our proposal is that the percentage of the population within walking distance of frequent all-day service goes up from 58% to 75%. The last 25% live in very hard-to-reach or low-density places where it would be cost-prohibitive to run frequent service, so we are bringing high-frequency service to almost all parts of the city where it the densities and road network make it viable.

That's important because frequency is freedom. High-frequency service (every 7-15 minutes or better) is service that's ready to go whenever you need to go, and that can even be used spontaneously to move around the city.

This kind of network design work is a holistic exercise in multi-variable problem solving. Each idea for improvement has many knock-on effects that we have to evaluate, and it takes skill and experience to see the best network patterns that optmise across so many issues. The outcomes don't please everyone, and especially don't please people who are opposed to all kinds of change. But it is exactly the sort of network design that leads to stronger urban transit networks that more people find useful. This kind of design also supports more intense urban development where that's appropriate, thus providing more alternatives to horizontal expansion of the urban region.

However, we're getting a lot of objections from the Green end of the spectrum. These have been summarised for me as follows. For the benefit of Wellington readers and also for anyone interested in the issue of Green responses to network plans, I'd like to reply briefly to each. These are my own views and do not represent the policy of Greater Wellington Regional Council or any other agency involved in the proposal. The concerns are in italic, with my responses below.

1. Some concern that technocrat/experts (even smart, nice people with great intentions) may not come up with a better solution than the whole community using the network–therefore it would be desirable to have more extended community input before implementing changes, or alternatively, to take staged approach to implementation to see if it works as intended.

I'm a big advocate of crowdsourcing network design ideas, and often run workshops that invite local stakeholders to think together about a network design problem. That tool was not used in this study, but we did look for every possible source to inform the planning, and of course the government is consulting with the public now in anticipation that some changes will occur as a result. Note also that we relied extensively on data about how the system is currently being used, and this too is a form of public input.

However, if you haven't been designing transit networks for a long time, there are some facts and techniques that won't be intuitively obvious to you. My book Human Transit is designed to address exactly this comprehension gap. It helps people who aren't transit planners to understand the transit network design problem, and thus to better evaluate transit proposals. And as I say many times in the book, the point is not to impose my values but to help communities express and implement theirs.

2. Concern that current journeys are influenced by the transfer fare penalty, and until we implement integrated ticketing, we won't really know the journey desire lines and therefore that really needs to happen before a network review.

I have said consistently throughout the project that to fully succeed, the proposal will need integrated fares permitting free connections, at least within Go Wellington, the operator covering most of the city. I'm told that a separate study on fare policy, including connections, will be underway soon.

Again, charging for connections is perverse, because connections are a necessary inconvenience, not a value-added feature. One strong reason to potentially postpone the Northern Suburbs area of the plan is that it requires free connections between different operators (two bus companies and a rail line) and this is much harder to achieve than free connections within the one operating company that covers the rest of Wellington. It makes sense to start in the main part of Wellington covered by one operator, where eliminating connection penalties is realistic in the short term.

3. Concern that the infrastructure for the trolley buses will be immediately removed on the routes that will be superseded, before we know if the new proposed routes will be successful and permanent.

At no time during the project did anyone suggest to me that this be done. On the contrary, the thinking throughout the project was about ensuring that the trolleys had every possible opportunity to succeed. In fact, one proposed line, Line C, is mostly under trolley wire and designed to be easily converted to trolleys once there is a decision to expand the trolley network.

I personally am a trolleybus advocate, as you can see here. However, our task in this study was to design the best possible network for the city, without presuming an outcome about a future debate about trolleybuses. That debate will occur in a separate study that the council is undertaking now.

Planning is impossible without separability. Greens in particular tend to see how everything is deeply connected to everything else, so they are understandably suspicious about studying anything in isolation. Often they're right, and two issues really have to be studied together. Still, while everything is connected, governments simply can't do studies of every connected issue at once.

In this study, we dealt with this question around the trolley bus issue and also around the fare policy issue. Wellington needs a study and public discussion about the future of the trolleys. Wellington also needs a review of fare policy addressing the connection issue. But if we did a plan that tried to deal with all those issues as well, it would be so huge and multi-messaged that few people could follow the whole thing, or see how the parts are related. The hard experience of planners and elected officials is that such overly grand proposals usually fall over from their sheer complexity of message and the diversity of controversies they raise.

So the Regional Council took the view that we should study the city's mobility and access needs first, and get some clarity about what the network should ultimately look like. That's because they wanted their fare policy, and their trolley policy, to follow from the city's transport network rather than preceding and constraining it. If your goal is a city where people feel freer and more empowered to access the riches of their city at all times of day, that's the logical course.

4. That the network review will be used as an opportunity to force the wholesale removal of trolleys by those who are politically inclined to ditch them because of short term thinking.

I can't control how the proposal is used, but this was not the intent, and I don't agree that the proposal advances a case for removing trolleybuses.

The proposal does reduce the number of trolley buses needed in service, but only in the context of reducing the number of all buses needed. Fleet requirement overall drops dramatically under the proposal, because there is tremendous inefficiency in the existing peak schedules and we wanted to reallocate that service to create more abundant mobility all day. (However, we also checked existing peak loads, and took great care to ensure that the plan will be able to handle all peak crowding that's currently observed.)

Since the trolley fleet requirement goes down in the context of the whole fleet requirement going down, we clearly weren't discriminating against trolleybuses in any way.

The proposed fleet reduction is a good thing for Wellington, becuase it makes service cheaper to operate and thus creates the potential for future abundance. Don't measure the plan by its fleet requirement. Measure it by the mobility outcomes that it delivers, including the dramatic expansion of all day frequency.

5. The debate about the trade off between maximizing patronage and maximizing coverage (for social inclusion) was not explicitly had by the community… This policy to maximize patronage is essentially a decree by Government, and GW should be consulting more explicitly about this trade off before just deciding to redesign the network to maximize patronage.

I have facilitated exactly this debate many times, and Chapter 10 of Human Transit is all about it. I agree that the debate should ideally be a public one.

In this study, the decision was to avoid reducing coverage as much as possible. We retained coverage to virtually all areas now served, though not necessarily on the same streets, and in some cases we expanded it. If we had been charged with shifting priorities massively toward ridership, we'd have proposed deleting a lot of coverage to low density or hard-to-serve areas, including areas like Kowhai Park, Wright's Hill, Houghton Bay, Melrose, Owhiro Bay, Broadmeadows etc. We didn't do that.

Related point: radical network redesign has a human cost in terms of elderly, infirm, other marginalized users who may be too confused, disoriented or afraid to use the new network because they will feel lost.

This is a major issue in every network design. But this concern, stated so broadly, becomes a reason to never change anything, and to allow the network to retreat into irrelevance by never updating it to reflect the needs of a changing city with growing sustainability goals.

The answer to all these needs is a mixture of (a) careful information and travel training, to ensure that information or understanding is not a barrier to the new network, (b) appropriate on-demand services for people who simply cannot use fixed route service, in their location, for reasons of disability, and (c) urgent attention to where facilities are built for seniors, disabled persons, and others at risk of falling into this "marginalized" category. Locate on the network of high-quality freqeuent services (which the plan expands) and you won't need to worry about your service changing often in the future, because the more frequent a service is, the more permanent it is.

6. Some concern about the principle of designing for an all day basic network because the nature of journeys in Wellington is very different during the day for work trips and other kinds of trips off peak etc.

While travel patterns change in the course of the day, there is a very important reason to resist changing the pattern of service several times during the day. Such changes result in maddening complexity, and dramatically undermine's people ability to use the system freely and spontaneously.

Imagine what driving in Wellington would be like if you had to remember that the basic geography of the city changes completely several times during the day. Suppose that during the day streets changed direction, or became longer or shorter, or closed at certain hours (different for each street), or even that streets connected to each other differently depending on the time. You might justify this based on optmising flows for each moment of demand, but it would drive any motorist (or cyclist, or pedestrian) mad.

Buses physically can change their patterns in very microscopic ways, but good urban networks don't do that much because the overriding goal is to be simple and legible. Sustainability outcomes in particular, notably reducing car ownership, require that the transit options be simple and easy to trust. And that means transit lines that are doing the same thing all the time.

So instead of changing patterns by time of day, we focus on designing a basic network that makes sense at all times, and then adding supplemental peak-only services when certain flows appear. Even then, we focus on trying to make the all-day network useful for as many trips as possible. Because that's how you build a network that feels, and is, permanent, ready to support the further growth of the city in a more sustainable form. For a more complete discussion of this issue, see Chapter 8 of Human Transit.

To sum up, the proposal is designed to aggressively support the growth of Wellington in more sustainable ways, and as such it deserves some Green support. Unfortunately, mobility and access outcomes are hard to illustrate. I wish every citizen had access to an online tool that would show how their personal transit access would change under the proposal. It would something like mapnificent.net for both existing and proposed networks, showing how the proposal expands the area that you can get to quickly, and thus, in a very basic sense, expands your freedom.

Only a network that does that will help people sell cars and trust public transport more for all the needs of life. So consider judging the plan on how well it does that.

how do you compare to your peers? should you care?

Posted on October 11, 2011 in Auckland, Brisbane, Calgary, Edmonton, Honolulu, Melbourne, Ottawa, Portland, Seattle, Strategic Transit Planning, Sydney, Urban Structure, Vancouver, Wellington

Admit it: You've always cared, at least in secret, about how you compare to your peers: your friends, your fellow students, your graduating class, your co-workers, your generation. Well, deep down, transit authorities and city governments care too, which is why comparing a city to other similar cities always gets attention.

Sometimes peer comparisons cause complacency, especially if you choose the wrong peers. Wellington has the highest transit mode share in New Zealand, but in a country with only one other big, dense city, that obviously shouldn't imply that it's reached nirvana. Working in greater Vancouver I always have to emphasize that they are doing so well by North American standards that they have to start comparing themselves to European port cities in their size class (Glasgow, Edinburgh, Copenhagen, Helsinki, Marseilles). My general advice: If your peer comparison says you're wonderful, throw a party and revel in this for 48 hours, then look for a more motivating group of peers.

At the other extreme, nothing is more motivating than being told that you're dead last among your peers. Earlier this year I worked (through my Australian employer MRCagney under the leadership of Ian Wallis Associates) on a peer comparison study for Auckland, New Zealand, which compared Auckland's transit performance with all the five biggest Australian cities plus a selection of North American ones. Download the full report here. Remember, if you're in any of the peer cities that it uses (Wellington, Brisbane, Perth, Adelaide, Sydney, Melbourne, Edmonton, Ottawa, Calgary, Vancouver, Honolulu, Portland, Seattle) this is your peer study too! Just keep the tables and refocus the text (citing the source of course!).

More generally, the report is a good illustration of how peer comparison can work at its best, and also of the cautions that must be shouted from the sidelines once the conclusions take fire in the media, as they certainly have in Auckland. From yesterday's New Zealand Herald:

Consultants have ranked Auckland last out of 14 cities – in New Zealand, Australia, Canada and the United States – included in a benchmark study for the average number of public transport trips taken annually by its residents.
Aucklanders also pay the highest fares of any of the cities, amounting to 24c for every kilometre travelled on the average 44 public transport trips they take each year, compared with 17c in Wellington.

The rest of the article is further grim statistics, plus quotations from political leaders demanding that something be done.

I'm sympathetic to Auckland Transport in this case. Remember, a city's transit performance is mostly about the physical layout of the city and the constraints on other modes; the quality of the transit system by itself can't overcome problems in those areas. The nature of the economy also matters. Wellington is much smaller but it has much more severe chokepoints in its urban structure. In fact, all travel between the northern and southern parts of the city must go through a single chokepoint less than 1 km wide, which is also the (very dense) downtown. Wellington's economy is dominated by government, which is generally a sector disposed to use transit heavily. All of these features are hugely important in driving Wellington's mode share above Auckland's, and yet they don't include anything about the respective quality of the transit systems.

Peer comparisons also carry the false assumption that everyone wants to be the same kind of city, and is therefore working to the same kind of goals. (This attitude, taken to extreme, produces the absurdity of top ten "best cities for transit" lists.) Low mode share for transit may mean your transit system is failing, but it may mean that it's not trying for mode share, or at least that it has other objectives or constraints that prevent it from focusing on that goal. It may just mean that your city has different values. It may mean the city stikes a different balance between cycling, transit, and walking based on its own geography.

Still, service quality matters, and there's a lot that Auckland can do. I hope the city's opinion leaders are listening to Auckland Transport as well as berating it, so that they understand the real choices that must be made to move Auckland forward. If there's a real conversation, great things can be accomplished.

wellington: a sensible tourist on the cable car

Posted on October 1, 2011 in Architecture, Technophilia, Wellington

This blog rarely goes on about interesting transit vehicles, since my main interest is in getting people where they're going in whatever vehicle makes sense for the purpose. But while working in Wellington last month, I made early morning ritual of climbing to the Botanic Gardens summit just west of downtown, and on one such walk I took some time to admire the cable car.

"Cable car" generally means any vehicle attached to a cable that provides the locomotion. The car has no engine, but an engine of some kind is moving the cable. The cable can be aerial (gondolas, aerial trams) or underground (San Francisco cable cars) or it can just lie on the surface in a special guideway, as in most funiculars. Wellington's is essentially a funicular: it runs in a dead-straight track up the side of a steep hill. The two cars are fixed to the ends of a single cable, connected at the top, so that they move in counterweight fashion, one car rising as the other descends.

Unlike most funiculars, though, it has more than two stations — five in fact. At Talavera station in the exact middle, tracks widen out so that the cars can pass. Everywhere else the cars share one track, but with two separate rollers for the two cables:

(In this case, the presence of just one cable means that one car is below us, the other above.)

The spacing of the other stations is limited by the design or the system, because when a car is at the station one up from the bottom, the other is stuck the same distance below the top. In Wellington, even spacing of stations — not always ideal for local geography — ensures that both cars are at stations whenever they stop.

But enough with technology fetishes. Why is this thing useful?

Easy: it's a straight line, running at high frequency, through high density, where competitors are at a disadvantage.

Cable cars (aerial or surface) can make sense in settings where you want a straight line up the side of a steep hill — especially if there's no straight road that a bus could follow. That's exactly what the Wellington line (marked by the five yellow pins) is:

The terminal stations are Lambton Quay in the heart of downtown and the Botanic Gardens summit. There's demand everywhere on this dense hillside. Botanic Gardens station offers a level walk into the fairly dense Kelburn district to the southwest, while Lambton Quay is right on the Golden Mile, where buses come every minute or less to take you north or south through downtown, and beyond.

The other stations are Victoria University, one down from the top, Talavera in the middle, and Clifton, one up from the bottom. Victoria University's campus is visible on the south side of the above image. It has its own bus services, but it's a short level walk along a terrace to its station.

And while climbing this hill is something I might do as early morning exercise, it's understandable that you might want an alternative to that. The climb is 120m of elevation gain in only 612m of horizontal length, a grade of nearly 20%.

But the real reason I thought to write about it is the interesting feature observable at the top.

The vehicles themselves are designed for their constant slope. The floor is always parallel to sea level while the car's structure is tilted 20% from the floor, to match the grade.

As a result, it's possible to open the car on both sides and produce a level boarding from the surrounding ground. Where the car dwells at the top, as in this image, you can even walk right through the car as though it were part of the sidewalk.

I'm always interested in ways to make transit feel more continuous with the pedestrian realm. I long for buses with precise docking for absolute level boarding — not just to eliminate the delay of wheelchair ramps but also to create a feeling that the bus is a moving piece of sidewalk, that you are not leaving the street to crawl into an oppressive enclosure. Local transit won't really feel effortless to use until we have this effect.

So that's why this image appealed to me, so much that I even indulged some uncharacteristic technology-fetishism. Because the effect in this picture in important, and if I need a cable car to get it, I'll take a cable car.

can transit-only streets work in small cities?

Posted on June 18, 2011 in Legibility, Trolleybuses, Wellington

Yes, says Wellington, New Zealand (pop. 389,000)!

In North American debates about pedestrian and transit malls, we're usually told that such things only work in Europe, with the implication that age, historic density, and cultural history of European cities makes them unrealistic mentors for the young North American city. Well, as an urban culture, New Zealand is even younger than North America. In fact, the urbanization of both Australia and New Zealand happened around the same time as that of the North American west, and the level of attachment to cars is also comparable. So North America needs a better excuse!

Wellington's "Golden Mile," long the core business strip and highrise office district, is now a two-lane, largely bus-only facility, the last bit of which was finished last November. It features generous sidewalks, near-continuous awnings for shelter (a city requirement) and hardly any commercial vacancies. In fact, the whole thing appeared to be bustling throughout my stay the past week, with plenty of pedestrians and plenty of activity around the abundant street-level retail that lines the entire thing.

The pic above, of course, was taken by the City on a perfect sunny day. Having spent most of the last week in a conference room, I can offer only pics taken early in the morning:

Note the green paint. In Australia and New Zealand there is never any question about where bus lanes are, and zero excuse for not noticing them. Note also that the red bus is about to turn right from one green lane into another; the Golden Mile isn't entirely straight, but the green lines (and abundant buses) make it perfectly clear where it is, and how it works.

I'll come back to some of the interesting details of the Golden Mile, but meanwhile, next time someone tells you that North American cities can't emulate Europe, ask why they can't emulate New Zealand!

First photo: City of Wellington

new zealand’s san francisco

Posted on June 15, 2011 in Tourism, Wellington

Greetings from Wellington, New Zealand, where I'm working with the regional government on some transit planning. There are limits to how much blogging I can do while working 1.5 fulltime jobs and copyediting a book. More soon on Wellington's remarkable downtown transit spine and pedestrian malls, but for now, well, tourist pictures basically, with some interesting stuff encoded:

Not bad for the verge of Winter Solstice! But no, the weather's not always like this …