Posts Tagged ‘Project Connect’

h1

Capital Metro — Back to 1986?

30 November 2016
Ottawa Transitway (BRT) bus congestion in downtown, 2011. Bus congestion has persuaded Ottawa to launch LRT project, now under construction. The possibility of severe bus overcrowding in downtown Austin led Capital Metro board to reject a proposed BRT line in I-35 in favor of LRT in 1989.

Ottawa Transitway (BRT) bus congestion in downtown, 2011. Bus congestion has persuaded Ottawa to launch LRT project, now under construction. The possibility of severe bus overcrowding in downtown Austin (as warned by local community transit activists) led Capital Metro board to reject a proposed I-35 BRT line in favor of LRT in 1989. (Photo: Flickr.)

Austin’s Capital Metro seems determined to return to the thrilling days of yesteryear – at least in its longrange transit system planning.

That would appear to be the case, according to reports from participants in a meeting where representatives of Project Connect (unearthed from its grave by Capital Metro) presented the agency’s “priorities” for regional transit system planning.

The presentation, organized on the evening of November 15th by the Friends of Hyde Park neighborhood association, was reported by Austin community transit activist Mike Dahmus in Twitter messages and a posting on his blog. Mike’s report, with confirmation from other participants, makes it clear that some implementation of “bus rapid transit” (BRT) on I-35 is (in the words of one observer) a “foregone conclusion”. But this is a revival of a faulty 1986 plan from the agency’s past.

This proposal for “BRT” (i.e., express or limited-stop buses) on I-35 is basically a reversion to Capital Metro’s planning as of about 1986, at the start of the Transitway Corridor Analysis Project (TCAP). This early study effectively began with the premise that “BRT” was probably the desirable “rapid transit” mode for the region (although light rail was included in the TCAP study as a kind of whipping-boy target to be rejected). Just as with the agency’s current scheme, the 1980s-era “BRT” plans envisioned buses running in I-35. Feeding more buses into the I-35 alignment was to be the function of a northwestern branch; this was proposed as alternatives of running buses either in U.S. 183 or in a dedicated busway to be constructed along the new railway alignment (now the Red Line) that had been acquired by the City of Austin from the Southern Pacific Railroad.

Unfortunately for that “BRT” strategy, a number of savvy light rail transit (LRT) advocates were members of the TCAP Technical Group of Capital Metro’s then-very-active Citizens Advisory Committee, which met regularly (every two to three weeks or so) during the study process. Particularly knowledgeable about technical issues relating to the comparative evaluation of transit modes (e.g. issues from ridership forecasting to infrastructural, operational, and cost issues), community activist Dave Dobbs and public transportation planner Lyndon Henry were effective in responding to various claims and factual errors forthcoming from both Capital Metro staff members and consultants. The end result was a recommendation from the Technical Group for the Capital Metro board to approve LRT as the preferred mode, and subsequently (in 1989) the board did designate LRT as the agency’s Locally Preferred Alternative (LPA) for the central corridor.

What persuaded Capital Metro’s top decisionmakers to opt for LRT over the BRT plan? The most salient factors included:

• Evidence (plus intuition) that rail transit has greater public attractiveness and generates higher ridership than comparative bus systems …

• Unease over the difficulties and high investment cost of inserting BRT into a freeway alignment, and questions over the value per dollar spent compared with LRT …

• Perception and evidence that LRT tended to generate greater adjacent real estate and economic development than BRT …

• Overall perceptions that economic development plus total cost-effectiveness suggested a higher return on investment (ROI) for LRT …

• Concern over the possibility of bus overcrowding and even congestion on Central Area streets with the high-capacity BRT alternative …

• Conclusion that LRT would yield better compatibility (and fewer environmental impacts) with Austin’s urban environment than BRT.

Unfortunately, there’s no indication that any of these issues are being considered in the current Project Connect 2.0 study process, or emerging as a focus of attention on the part of today’s Capital Metro board.

And Capital Metro seems headed to repeat other past mistakes as well. Apparently, as related by Mike Dahmus’s blog report, the resuscitated “Project Connect 2.0” study process is also committing the same kinds of absurd, critical methodological errors that so thoroughly damaged the original “Project Connect 1.0” attempt to fashion a “High-Capacity Transit” (HCT) proposal in 2013. (See «The fraudulent “study” behind the misguided Highland-Riverside urban rail plan».)

For example, Mike reports:

The framework for discussion has been set in a way that heavily disfavors Guadalupe/Lamar rail. There are three ‘segments’ of travel they put up on the screen; as well as a slide which shows “previous HCT studies”. Guadalupe/Lamar is not in the top slide (most important service), nor is it listed in “previous HCT studies”. It is instead consigned to the second group, called “connector corridors”, implying that Capital Metro has already decided that it cannot be the spine of the transit network.

This kind of planning contortion – dissecting and severing major travel corridors into irrelevant “segments” – is exactly the kind of methodological butchery that in 2013 provided Project Connect 1.0 a rationale to dismiss the city’s most significant central urban travel corridor, Guadalupe-Lamar. Mike goes on to correctly explain that

… when the majority of your passengers on your theoretical ‘spine’ have to transfer, YOU HAVE A BAD SPINE, DAWG. Spines need to go down the middle and get to the good stuff. And especially on the ‘work end’ of the trip (not the ‘home end’): if a large percentage of your riders have to transfer off the spine, you’ve chosen poorly.

His blog post also quotes Houston urban planner and transit advocate Christof Spieler’s observation on the need to zero in on a city’s most important corridor:

For Houston, the strategy meant building a light rail through the city’s primary urban corridor, where lots of people already live and work.

Cities often shy away from that approach because it’s more expensive and disruptive to lay tracks in such populated locations. But the factors that make it difficult to build light rail there were exactly the things that made it the right place to have light rail.

Unfortunately, these key lessons seem lost on Capital Metro and its reanimated concoction Project Connect 2.0. Currently, the agency appears to be on course to once again disparage, downplay, and bypass the most important urban travel corridor in the city: Guadalupe-Lamar. ■

h1

Capital Metro: Let’s have 2 1/2 more years of analysis paralysis

27 February 2016
Title slide of Capital Metro's CCCTA presentation to Austin City Council Mobility Committee on Feb. 3rd. Screen capture: ARN.

Title slide of Capital Metro’s CCCTA presentation to Austin City Council Mobility Committee on Feb. 3rd. Screen capture: ARN.

After months of preparation, organizing, bidding, and selection, with lots of fanfare Capital Metro at last launched its $3 million, 30-month (2.5-years) Central Corridor Comprehensive Transit Analysis (CCCTA) study. In a Jan. 25th news release, Capital Metro announced that its board of directors had selected engineering firm AECOM as the lead consultant to conduct the Central Corridor analysis.

To the uninitiated, inexperienced, and uninformed, this latest study might seem some kind of step forward for Austin’s transit development. After all, its elements include impressive-sounding goals like “An in-depth study of a variety of transportation modes and their potential for creating improved transit options within the corridor”, “A multimodal transportation plan that improves the feasibility of transit in the Central Corridor while effectively maximizing connections with regional routes in surrounding communities”, and “A realistic cost analysis for building, operating and maintaining the proposed sustainable and connected transit system”.


Capital Metro's planning chief Todd Hemingson explains CCCTA study to Austin Mobility Committee on Feb. 3rd. Photo: ARN screenshot from official video.

Capital Metro’s planning chief Todd Hemingson explains CCCTA study to Austin City Council Mobility Committee on Feb. 3rd. Photo: ARN screenshot from official video.


Analysis Paralysis gold medal

But, among grassroots public transportation advocates in Austin, it’s hard to find a transit supporter who’s enthusiastic about this study. The reason: All of these issues have already been exhaustively studied, and plans prepared and re-prepared, over and over and over and over again, for more than two decades. For Austin transit supporters, we’ve “been there, done that” — multiple times. It’s just one more repetitive “re-study of the re-studies of the re-studies ….”

To get a breathtaking idea of the time, resources, energy, and money Austin has sunk into planning for “high-capacity” public transport, just check out our February 2015 chronicle of studies and re-studies of light rail transit (LRT) in the Guadalupe-Lamar corridor: «Long saga of Guadalupe-Lamar light rail planning told in maps». This central travel corridor’s high level of traffic, population and employment density, and crucial position accessing and connecting vital activity centers (like UT, the Capitol Complex, and downtown) with key established neighborhoods and extended commercial activity along the route have made it the focus of planning for rail transit for over three decades.

In terms of public transit, Austin clearly is a top contender for the Analysis Paralysis gold medal. And Capital Metro’s latest CCCTA study, as it’s currently designed, surely represents Exhibit A toward this dubious award. The confusion, misdirection, conflicting intentions, and lack of purpose underlying this “paralysis” were discussed in our March 2015 article «Austin’s urban transport planning seems struck by catastrophic case of amnesia and confusion».

Meanwhile, as meaningful public transport planning continues to languish, the Austin metro area is experiencing a veritable blitz of intensive highway development and construction, including at least three new tollways, massive projects on I-35, and assorted projects throughout the urban area. As the saying goes, “Roads get built, transit gets studied“.

Project Connect back from the dead?

But confusion and a continuation of “analysis paralysis” aren’t the only problems with the CCCTA study. As currently configured, the study seems little more than a rehash of Project Connect’s ill-fated “High-Capacity Transit Study” which elicited such intense community outrage beginning in 2013, the precursor to its ultimate resounding rejection by voters in November 2014. Indeed, the CCCTA project seems the first major effort to resuscitate Project Connect since its 2014 debacle.

Among the worst weaknesses of the Project Connect disinterment is the revival of the seriously flawed methodology of the earlier “analysis”. This includes ignoring actual, existing travel corridors — such as the pre-eminent Guadalupe-Lamar corridor — and instead mislabeling huge chunks and sectors of the city as “corridors”. (The methodology further subdivided the “Central Corridor” into “subcorridor” mini-sectors.) Thus, according to Capital Metro, per the CCCTA study, “The Central Corridor is defined as an area bordered on the south by Ben White (US-290), on the east by the Capital Metro’s Red Line, on the north by RM 2222/Koenig Lane, and on the west by MoPac Expressway, and includes downtown Austin.”

Not only is that vast glob of central Austin not a corridor, but (as in the 2013 activity) this approach slices and truncates actual travel corridors, particularly Guadalupe-Lamar, rather than analyzing them in terms of their suitability and potential for actually solving mobility problems with public transport (particularly urban rail). We analyzed the problems with this in our November 2013 article «Project Connect’s “corridor” study — without corridors!»


Infographic shows how Project Connect’s methodology segmented Guadalupe-Corridor into nonsensical pieces, and summarizes numerous other major problems. (Click to enlarge.)

Methodology of Project Connect study in 2013 labeled huge chunk of central city as a “corridor”, but severed actual intact travel corridors into meaningless pieces. Graphic: ARN. (Click to enlarge.)


Community skepticism about Capital Metro’s “corridor” methodology in the CCCTA study was illustrated as early as last September by Jace Deloney, a co-founder of the influential AURA group (involved with urban and transportation issues) and former chairman of the City’s Urban Transportation Commission and Capital Metro’s Customer Satisfaction Advisory Committee:

It’s very important that we advocate against using the previous subcorridor definitions for any future high capacity transit planning project. In my opinion, these subcorridor definitions were deliberately designed to end up with a Red River alignment recommendation.

Re-direct the CCCTA study!

Besides the exhaustive “saga” of studies of the Guadalupe-Lamar corridor detailed in the ARN article cited and linked above, Austin Rail Now and other community stakeholders have presented LRT alternative alignment and design proposals that provide more than enough basis for quickly reaching a decision for an urban rail starter line. The most recent proposals are described in several ARN articles:

Plan for galvanizing Austin’s public transport development: Light rail starter line in Guadalupe-Lamar (June 2015)

Another major Austin community recommendation for light rail transit in Guadalupe-Lamar (November 2015)

Another possible design for light rail in Guadalupe-Lamar corridor (January 2016)

So far, in the absence of any sense of direction toward a major urban rail investment, Austin’s top political and civic leadership is vulnerable to pressure by highway interests (such as TxDOT) for municipal general obligation bond funding for a heavy local investment in a massive I-35 overhaul and other huge highway projects. To this, a major rail transit starter line investment might be counter-proposed as a far more effective and desirable alternative for city bond funding.

It would definitely seem time to end Austin’s decades of “analysis paralysis” and move forward quickly toward finalizing an urban rail plan for public approval — a strategy that could be expedited by re-directing Capital Metro’s CCCTA study. There is certainly sufficient planning and design preparatory work already in place to provide the voting public a basis on which to make a decision for the Guadalupe-Lamar corridor. The AECOM consultant team (widely respected in the public transportation industry, with experience with LRT in Portland, Minneapolis, and elsewhere) could simply update and tweak the major engineering studies that have already been done (e.g., those in 1993 and 2000) for the Guadalupe-Lamar corridor.


Proposed 6.8-mile "Plan B" light rail transit line in Guadalupe-Lamar corridor would have 17 stations and connect  the North Lamar Transit Center at U.S> 183 with Crestview, the Triangle, UT and the West Campus, the Capitol Complex, the CBD, and the Seaholm-Amtrak area. It's projected to serve 3 times the ridership of the Prop. 1 Highland-Riverside rail line at slightly over half the capital cost.

Austin Rail Now proposal is one of several possible configurations already suggested for light rail starter line in Guadalupe-Lamar corridor. Graphic: ARN.


This would likely require a major intervention by Austin City Council members to request Capital Metro to negotiate with its consultant team for a modification of the CCCTA work plan — eliminating the proposed 30-month “slow track” study, and re-directing the project into planning, design, and engineering of LRT for the Guadalupe-Lamar corridor as suggested above. This would have the aim of placing a measure on the ballot for bond funding (to be kept in escrow till further planning and Preliminary Engineering/Environmental Impact Study tasks are completed). Adequate cost estimates are already on hand for such a ballot measure.

According to Surinder Marwah, the former Capital Metro Senior Planner who secured federal funding for the MetroRapid bus project, this can be “a reasonable plan if the elected officials, business leaders and major stakeholders can come to an agreement” for the general Guadalupe-Lamar alignment corridor. “AECOM can update the preliminary cost estimates quickly and perform fatal flaw analysis for the alignment corridor within few months — by mid-late August to get this into [a] November ballot measure.”

Capital Metro’s currently contrived CCCTA study seems little more than a “holding pattern” reflecting the indecisiveness and lack of will of key public officials in regard to public transport policy. Re-directing this study as proposed above would at long last move Austin’s rail public transport development into a widely supported action phase and head it expeditiously toward the mobility quantum leap Austinites have so long been denied. ■

h1

Austin’s urban transport planning seems struck by catastrophic case of amnesia and confusion

29 March 2015
Graphic: Rich's Management Blog

Graphic: Rich’s Management Blog

The devastating befuddlement of Austin’s official-level urban transportation planning over the past five months has been nothing short of jaw-dropping. Especially when you consider this in context.

For two and a half decades, local officials and planners have explained why urban rail — affordable light rail transit (LRT), in Austin’s case — has been an absolutely essential component of the metro area’s mobility future. As our recent article «Long saga of Guadalupe-Lamar light rail planning told in maps» describes, the logical starting point for an initial LRT route has been the central city’s heaviest-traveled central corridor, Guadalupe-Lamar.

Year after year, planning proceeded in some way for LRT. Even after 2003, while official planning was distracted and mis-directed toward potential routes more to the east of the central core city, the need for rail transit was still proclaimed. Austin had to have rail to maintain an adequate level of mobility into the future.

Beginning about 2006, an original streetcar “connector” rail transit concept emerged that gradually morphed into more ambitious “urban rail” — a full LRT system. An official blue-ribbon committee of civic leaders, the Transit Working Group (TWG), was hand-picked (first by State Sen. Kirk Watson, then by Austin Mayor Lee Leffingwell) to guide rail planning. Extensive planning documents were finalized for a route scheme linking the Core Area with Seaholm, East Riverside, the East Campus, and Mueller — a rather deranged route, in our view, but rail nonetheless. The City then launched a full-fledged NEPA (National Environmental Policy Act) process (required for federal funding), with a series of “open houses” and other public events.

Activities of the TWG continued to heat up, primarily focused on planning for the urban rail line to Mueller. Route alternatives, cost issues, funding issues, organizational and management arrangements, and all kinds of associated issues were discussed exhaustively. A new consortium of public agencies, called Project Connect, was formed, mainly to coordinate rail planning and to produce a massive regional plan criss-crossed with proposed rail lines. Remember all this?

By 2013, the official establishment apparently felt urban rail needed the scrutiny of a special High-Capacity Transit study. So a special Project Connect team, headed by consultant Kyle Keahey, was formed, and virtually the second half of 2013 was consumed with “studying” (translation: justifying) and finalizing the need, size, and shape of an officially preferred urban rail plan. Mueller was sidelined, replaced by a desperate quest for a rail line from East Riverside to the former Highland Mall site. “Gotta get to Mueller! Mueller! Mueller!” became “Gotta get to Highland! Highland! Highland!”


Urban rail has been on the official planning agenda for decades. Throughout the first 10 months of 2014, the Highland-Riverside plan (envisioned in this simulated scene) was hyped incessantly. Graphic: Project Connect.

Urban rail has been on the official planning agenda for decades. Throughout the first 10 months of 2014, the Highland-Riverside plan (envisioned in this simulated scene) was hyped incessantly. Graphic: Project Connect.


As this blog, and a sizable segment of local transit advocates, insisted, the plan was conceived for the wrong reasons and fundamentally flawed. But for about the last two months of 2013, and ten months of 2014, the City administration, plus Capital Metro, plus the prevailing faction of local civic leaders, all insisted over and over that rail was absolutely, positively essential (although it had to be the peculiar Highland-Riverside plan officials had concocted). An expensive ad campaign, much of it financed from federal funds channeled through Capital Metro, bombarded the public via the Internet and virtually all major media outlets — reiterating the message that traffic congestion was a growing threat to the metro area and rail (the official plan of course) was the essential remedy. Mayor Leffingwell’s familiar aphorism was suddenly appearing and being heard everywhere: “Rail or Fail!

And then, on Nov. 4th, it all hit a wall, as voters said No to the puzzling, nonsensical, controversial, and fabulously expensive Project Connect plan that had been offered.

And all of a sudden, rail was erased, scrubbed, from official discourse. Despite all the years, decades, of documentation of the need for a rail transit system for the city, the official vision of transit became refocused on “becoming the best bus system we can be”; after years of explanations that reliance on further highway development wasn’t a realistic solution for preserving the city’s mobility, regional highway and tollway development has suddenly received a new surge of energy in official policy.

Meanwhile, rail transit planning has basically vanished from official planning. It’s just gone “Poof”. As David Orr has reported in his recent commentary «Austin’s “shadow government” (CAMPO) disappears light rail from local planning», all reference to urban rail has been expunged from the 2040 Transportation Plan of CAMPO (Capital Area Metropolitan Planning Organization), and replaced by line items for “bus rapid transit” (i.e., expansion of the MetroRapid limited-stop bus service).

Affirmed, until last November, as an absolutely essential component of Austin’s future mobility, light rail has now disappeared from public discourse, from the mainstream media, from the lips of politicians and civic leaders. Is it some kind of collective amnesia? Have the local planning and decisionmaking establishment all been struck with a strange disability, like the global mass blindness in Day of the Triffids? Or is the obliteration of rail a calculated excision, like the Soviet Stalin regime’s air-brushing elimination of political undesirables from photos, or the “Photoshopping” of group photos by some misguided religious media to “disappear” women?


Evaporation of Austin's light rail planning resembles a catastrophe of collective affliction, like the mass blindness portrayed in Day of the Triffids. Movie poster: IMDb.com.

Evaporation of Austin’s light rail planning resembles a catastrophe of collective affliction, like the mass blindness portrayed in Day of the Triffids. Movie poster: IMDb.com.


One wonders whether any of these Austin-area leaders and planners have given a thought as to how this plays in public perceptions of their own credibility and integrity. Were all the assurances and explanations of the need for urban rail to maintain Austin’s future mobility and vitality just deceptive hype, a marketing ploy for some kind of alternative agenda?

Maybe, but we believe the fundamental case for LRT in Austin has been grounded in truth — the higher capacity, greater ridership attraction, cost-effectiveness, environmental benefits, unsurpassed magnetism to transit-oriented development and economic development, and other advantages of light rail are indeed essential for the future of this community. Mobility cannot be sustained of a continuing expansion of rivers of highways and tollways and a steadily rising flood of personal motor vehicles. Urban rail continues to be key to providing truly attractive public transit alternative, and shifting at least significant segments of the Austin metro to a sustainable alternative mobility lifestyle.


According data from Texas Transportation Institute, even with implementation of infrastructure expansion in CAMPO 2035 plan, Austin metro travel time would increase 80% due to traffic congestion. Graph: Austin Chamber of Commerce 2013 Mobility Report.

According to data from Texas Transportation Institute, even with implementation of infrastructure expansion in CAMPO 2035 plan, Austin metro travel time would increase 80% due to traffic congestion. Graph: Austin Chamber of Commerce 2013 Mobility Report. (Click to enlarge.)


And we have a strong suspicion that a preponderant number of local planners and officials actually continue to agree with this perspective. If so, they need to realize there’s a lot of community support for urban rail — from voters on both sides of last year’s debate — and they need to start stepping forward. They need to heed their sense of responsibility, find their mojo, or whatever it takes, to take the lead to get LRT planning back on track.

The groundwork, in terms of preliminary planning, is already there — and, in recent articles and other public information, Austin Rail Now along with other mass transit advocates have expanded on it.

Austin is waiting. We’re wondering who’ll take the first step. ■


LRT train on Portland's 5th Ave. transit mall swings to the curbside station to pick up waiting passengers. Photo: L. Henry.

Portland’s light rail trains (in dedicated lanes) share 5th and 6th Avenue transit mall with buses as well as cars — a potential transit design model for Austin? Photo: L. Henry.

h1

The fraudulent “study” behind the misguided Highland-Riverside urban rail plan

4 November 2014
Infographic shows how Project Connect’s methodology segmented Guadalupe-Corridor into nonsensical pieces, and summarizes numerous other major problems. (Click to enlarge.)

Infographic map shows several major flaws of Project Connect methodology, applied to a portion of “study” area. Result was to skew results (and urban rail route) toward desired sectors of central city. Graphic: ARN. (Click to enlarge.)

Few local issues have been more divisive than the City of Austin’s 9.5-mile, $1.4 billion urban rail plan. Envisioned for a route that meanders from the Highland ACC area on the north to the East Riverside area on the southeast, the proposal is now on the Nov. 4th ballot as a $600 million municipal General Obligation bonds measure that would help fund slightly less than half of the projected investment cost.

Community skepticism — and puzzlement — about this rail project is widespread, but sponsors and supporters of it have repeatedly endeavored to bolster its credibility by describing it as the product of a “scientific”, “data-driven”, or “data-based” effort, a “high-capacity transit study” pursued by the Project Connect transportation agency consortium roughly between June and December 2013. However, as this website and numerous other critical sources have exhaustively documented, that “study” was basically a fraud.

It’s useful to review and summarize the origins of this seriously flawed rail plan as election day has come upon us. In particular, it’s important to keep in mind that the Project Connect “study” represents an object lesson in how not to conduct a study for a New Start rail transit project. This review will rely primarily on previous articles published contemporaneously on this website during the “study” exercise.

From Mueller to Riverside to Highland

As our recent article Derailing the Mueller urban rail express — Preamble to Project Connect’s 2013 “High-Capacity Transit Study” recounted, for years, local streetcar and then “urban rail” planning had focused on a starter line to the Mueller redevelopment project. There, the major urban development enterprise Catellus had been promised a rail transit link to help raise density limits, attract more property investors and homebuyers, and thus boost profits. Important also were the desires of the small but growing community of Mueller residents who expected a rail connection to jobs and other destinations.

However, for years the question had been repeatedly raised: Since the North Lamar-Guadalupe corridor was recognized as the city’s heaviest local arterial corridor, with the heaviest congestion — even used to justify the very need for urban rail in official presentations and documents — why was out-of-the-way Mueller targeted for the initial starter line investment? This inconsistency was the focus of our March 2013 article Why abandon Austin’s major corridor and congestion problem? which presented the following graphic, originally contained in a 27 January 2012 commentary by Lyndon Henry (now a contributing editor to this website):


xxxxxxx

Graphic from 2012 suggested official emphasis on urban rail line to Mueller was misplaced, when real mobility need was in Guadalupe-Lamar corridor. Infographic: L. Henry.


As our “Derailing…” article, cited above, further recounts, the City of Austin/Project Connect pretext for continuing to plan an easterly, East Campus urban rail starter line to Mueller began to fall apart when the competency of a 2010 “Route Alternatives Evaluation” — the nominal basis for the plan then current — was questioned. Possibly other factors may also have begun to come into play (such as business community interest in exploring other development opportunities that could affect urban rail route planning).

In any case, the direction of rail planning shifted significantly. As our article noted,

In early 2013, Kyle Keahey was hired as Urban Rail Lead to head a new “High-Capacity Transit Study”, tasked with supposedly re-evaluating everything, racing through a process (with a presumably more competent and defensible methodology) that would result in a recommendation by the end of 2013.

Summary assessments of Project Connect “study”

Personnel associated with Austin Rail Now, the Light Rail Now Project, and other pro-rail organizations were involved intimately in following the planning activities of the “high-capacity transit” exercise from midsummer through the early winter of 2013. A number of our articles, particularly beginning in early November, chronicled revelations and realizations about the planning process as they emerged at the time.

However, a reasonable overview of the fundamental problems with the Project Connect exercise is provided in two of our articles in particular, each of them based on major commentaries by Lyndon Henry addressed to the Central Corridor Advisory Council (a group of community leaders hand-picked by Mayor Lee Leffingwell to review and approve work of the “study” team). These two articles, from early December 2013, together represent in essence an indictment of the competency and indeed the very legitimacy of the Project Connect exercise:

Memo to CCAG: “Pause” study or include “Lamar” sector

Project Connect Needs an Overhaul

What emerges is the sense of a process that was corrupted and skewed to render what, in hindsight, appears to be predetermined results — results seemingly contrived to justify a routing scheme for the proposed urban rail starter line project contrived to fulfill the aims and desires of City of Austin policy and various special interests. As our article Surprise! Mayor and Project Connect select same routes they wanted in the first place (17 November 2013) assessed the process, Project Connect’s “study” seemed to have

… numerous hallmarks of having been rigged, from a peculiarly contrived methodology that departs from longstanding professional practice, to cherry-picking of a highly questionable set of data elements and the exclusion of data indicators far more appropriate for such an ostensible “corridor study”. (And, one might add, a highly secretive and insular process that immunized the ProCon team and their study procedures from public scrutiny and oversight.)

Thus the basic flaw in ProCon’s data analysis can be boiled down to one word: GIGO (“Garbage In, Garbage Out”). In effect, this appears to have been a process that involved limiting the focus to gerrymandered data sources, and then playing games with gerrymandered data.

The task facing Kyle Keahey and the Project Connect team was daunting. The prevalent public sentiment strongly favored the Guadalupe-Lamar corridor for the urban rail starter line. Most Austinites sensed that Guadalupe-Lamar carried the heaviest traffic, served the highest density, and accessed the most key activity centers in the central city. Yet the City of Austin administration, Project Connect political leadership, and a major segment of local political and civic leaders desired a “study” outcome that would validate their economic and real estate development objectives. Project Connect’s effort would therefore have to try to convince the community, “Don’t believe your lying eyes.”


PowerPoint slide in Nov. 2013 Project Connect public presentation shows audience's overwhelming preference for "Lamar" — a proxy for the Guadalupe-Lamar travel corridor. Photo: Workingbird Blog.

PowerPoint slide in Nov. 2013 Project Connect public presentation shows audience’s overwhelming preference for “Lamar” — a proxy for the Guadalupe-Lamar travel corridor. Photo: Workingbird Blog.


Critical failings of the Project Connect “study” charade can be grouped into categories of practices. The following summaries of these practices include references to various ARN articles that may further illuminate these issues.

► Failure to examine travel corridors

Rather than zooming in on, and analyzing, actual travel patterns and density of travel in actual travel corridors within central Austin, the “study” instead carved out a great square of the central city, dubbed it the “Central Corridor” (although it contained multiple corridors in every direction), and then further subdivided this into a series of ten component sectors, some sprawling over considerable expanses of urban real estate. Since virtually the entire central city had been designated a “corridor”, these sectors were then dubbed “sub-corridors” — a kind of camouflage verbiage that masked the actual nature of what were in effect city neighborhoods or districts, not travel corridors. The “sub-corridor” designation also imparted a veneer of “transportation study” truthiness.

Our first analysis of this methodological problem, Project Connect’s “corridor” study — without corridors! noted that Project Connect’s subdivision of the study area in this way thus

… created an array of balkanized sectors that are analyzed more as autonomous geographic-demographic “islands” than as components essential to work together as a whole. As a result, actual, realistic, workable travel corridors have been obscured by all this.

Our article included a detailed explanation, with examples, of what urban travel corridors actually are, and how they should be treated and evaluated in a bona fide transportation corridor study. But, rather than corridors, Project Connect’s sectors (“sub-corridors”), we pointed out at the time, “resemble, to some extent, rather large travel analysis zones (TAZs, also called traffic analysis zones or transportation analysis zones).”

But, rather than TAZs for legitimate analysis purposes, we pointed out,

Project Connect’s sectors, in contrast, seem more designed to pit one part of the city against another — to function more as neighborhood enclaves to be assessed for their isolated demographics and “level of misery” (poverty, congestion, etc.) in a competitive showdown within a game of “Which sector deserves the urban rail prize?” It’s astounding that this charade is presented as a form of officially sponsored urban transportation planning.

Together with the agency team’s “seemingly heedless” segmentation of travel routes, their “treatment of adjacent sectors as insular, isolated enclaves, whose demographics and other characteristics apply only to themselves” was equally harmful to proper analysis. “Likewise travel characteristics are treated in isolation, as if the population in all these different ‘enclaves’ confine themselves to the sector boundaries that ProCon planners have established for them.”

Throughout the “study” process, we repeatedly returned to this problem. Our article Questions for Project Connect (3 December 2013), publishing questions which we raised in a “data dig” with Project Connect team members, asked “Why has this study avoided performing an actual corridor study, and instead spent its time (and taxpayers’ dollars) confined to undertaking a de facto inventory (and ‘beauty contest’) of various urban sectors in isolation?”

In our Memo to CCAG: “Pause” study or include “Lamar” sector (5 December 2013) we noted that “The basic methodology of focusing on sectors (so-called ‘sub-corridors’) meant that the study failed to study a single actual potential travel corridor in the study area.”

► Gerrymandered “study” sectors

Our Project Connect’s “corridor” study — without corridors! article, pointing out the peculiar boundaries applied to Project Connect’s weirdly sprawling sectors, described them as “gerrymandered”, and further experience confirmed this assessment. Our 17 November 2013 article Surprise! Mayor and Project Connect select same routes they wanted in the first place observed that

rather than performing a bona fide study of actual alternative corridors, ProCon embarked on what amounted to an inventory of highly filtered attributes of basically gerrymandered sectors, dubbed “sub-corridors”, devolving into a kind of “beauty contest” among sectors of the city, while distorting as well as ignoring the actual travel corridors that should have been the focus.

The article provides the example of the highly contrived “Highland” sector:

It should be noted that the “Highland” sector bears very little resemblance to the actual Highland neighborhood, delineated by both the Highland Neighborhood Association (see Highland Neighborhood Association endorses Guadalupe-Lamar for urban rail) and the Highland Neighborhood Planning Area defined by the City of Austin (COA). While the actual Highland neighborhood and planning district includes North Lamar Blvd. (mostly as its western boundary) all the way from Denson Drive to U.S. 183, ProCon’s “Highland” sector studiously avoids Lamar, and never reaches U.S. 183; instead, the sector incorporates I-35 (never even touched by the real Highland), and droops down far south of the actual neighborhood to include Hancock Center and the northern edge of the UT campus — thus overlapping the long-proposed Mueller route for urban rail. In this sense, “Highland” appears to be manipulated here as a kind of “proxy” for the COA’s original plan, functioning as a precursor of a full route to Mueller.

► Severed and segmented travel corridors

This was perhaps the single most serious fault of the Project Connect exercise — not only failing to examine actual corridor travel patterns, but essentially destroying intact corridors, such as Guadalupe-Lamar, simply because they crossed boundaries of the arbitrary sectors. As we first noted in Project Connect’s “corridor” study — without corridors!

Perhaps the most serious flaw in ProCon’s urban rail study methodology — actually, catastrophic, because it fundamentally impairs the integrity of the whole process — is that the actual travel corridors are not only basically ignored as workable corridors, but also are truncated and segmented by ProCon’s arbitrary slicing up of the urban area.

If you’re evaluating a travel corridor, you must evaluate the corridor as a whole — what it connects from, to, and in between; what the populations and densities along the corridor are; what activity centers it connects; and so on. All those are important, because they’re critical to what makes a transit line in that corridor actually feasible and worth investing in.

The results for the Guadalupe-Lamar travel corridor were basically fatal, as we pointed out:

the Guadalupe-Lamar route is severed just north of the UT-West Campus area at W. 29th St. In other words, most of this potential route is cut off from its highest-density population district as well as its most productive destinations in the core of the city!

What’s left is a “rump” route, from a few blocks south of U.S. 183 to W. 29th St., that seems to have little purpose beyond perhaps some kind of “shuttle” along this isolated route segment. If there were a prize for idiotic public transport planning, surely Project Connect would be very high on the candidate list.

This problem also was repeatedly underscored. In our article Memo to CCAG: “Pause” study or include “Lamar” sector (5 December 2013) we warned that “The basic methodology of focusing on sectors (so-called ‘sub-corridors’) meant that the study failed to study a single actual potential travel corridor in the study area”, and added:

This methodology also segmented an otherwise viable corridor such as Guadalupe-Lamar into nonsensical pieces, severing the corridor from its most logical destination (West Campus and core area), and thus creating an arbitrary “rump” route (29th St. to south of U.S. 183) that goes from nowhere to nowhere.

Likewise, in Project Connect Needs an Overhaul (7 December 2013), we reiterated: “Project Connect’s methodology segmented the outstanding Guadalupe-Lamar corridor into nonsensical pieces, severing it from its most logical destination (the West Campus and core area), thus creating an arbitrary ‘rump’ route that goes from nowhere to nowhere.” These warnings, of course, were ignored.

► Excluding student and other nonwork travel patterns

While specific travel corridor trips were not examined in the “study”, Project Connect did include tabulations of total travel in each sector and estimates of trips between sectors and the Core Area. However, a particularly breathtaking aspect of the project’s Evaluation Matrix (also called the Comparison Matrix) was the exclusion of all trips except home-based work trips. In other words, non-work trips — including student trips — were omitted from consideration.

As we asked in our “data dig” Questions for Project Connect, “Why has this study’s assessment of “travel demand” from each sector to the core ignored home-based non-work (HBNW) trips — including UT student trips and recreational trips — in a college city with the largest university in Texas in its core area?”

This omission was repeatedly emphasized in subsequent articles. In our Memo to CCAG: “Pause” study or include “Lamar” sector, we pointed out:

As a measure of “Travel Demand” from each sector to the core, non-work trips such as UT student trips and recreational trips (e.g., to restaurants, bars, etc.) have been EXCLUDED — dismissing not only the enormous importance of non-work trips (which are heavy in the off-peak) for more cost-effective transit service, but especially the huge significance of student and recreational trips in a city with the largest university in the state (and located in its core).


Student travel was omitted from Project Connect's evaluation process, although their ultimately recommended route connected UT, the state's largest university, with ACC, the city's major community college. Photo via UTRugby.com.

Student travel was omitted from Project Connect’s evaluation process, although their ultimately recommended route connected UT, the state’s largest university, with ACC, the city’s major community college. Photo via UTRugby.com.


And similarly, in Project Connect Needs an Overhaul, we asked:

Extremely important non-work trips such as UT student trips and recreational trips have been EXCLUDED as a measure of “Travel Demand” from each sector to the core. How could they do this in a city whose core contains the largest university in the state?

In hindsight, the omission of student travel from the Evaluation Matrix is especially ironic in light of the fact that travel between UT and ACC would ultimately be a major component of the purported ridership of the final route presented by Project Connect.

► Manipulation of implausible projections

Skepticism about Project Connect’s heavy reliance on dubious projections began to emerge as the pace quickened toward a “recommendation” from the project team. In our 3 December 2013 article related to the “data dig”, Questions for Project Connect, we asked: “Why has this study used such speculative projections based on procedures that maximize all possible development for targeted areas (such as ‘ERC’, ‘Mueller’, and ‘Highland’), rather than using conservative projections based on conditions closer to reality?”

Local researchers and analysts such as software developer and research analyst Dan Keshet and management consultant Julio Gonzalez Altamirano had exposed serious weaknesses in the array of data projections being deployed by the project team — especially the conversion of what were in effect development “wish lists” into hard projections of future development, population, and employment that were being plugged into Project Connect’s model (an Excel-based “Evaluation Matrix” designed to competitively score the various sectors and render a winner). Their conclusions and other problems of the project’s data projections are discussed in our article What’s with Project Connect’s “2.9 million daily ridership” projection? (16 December 2013). As this article noted,

The question of projections has been an extremely contentious issue in Project Connect’s urban rail “study”. For many critics, the agency’s “projections” have represented de facto fantasies about what they would like to see, rather than the solidly reliable output of competent predictive analytics.

While projections were critical in any process of forecasting future developments and especially public transit ridership, we explained, “…there’s a vast distinction between developing conservative, reliable, and plausible forecasts, and producing exaggerated, fantasy-like projections, as Project Connect has done, heavily skewed toward certain geographical areas.”


Many of Project Connect's "data projections" for 2030 were based on "wish lists" of development, population, employment, and other demographic features — leading critics to ridicule them as "fantasy". Graphic via ARN.

Many of Project Connect’s “data projections” for 2030 were based on “wish lists” of development, population, employment, and other demographic features — leading critics to ridicule them as “fantasy”. Graphic via ARN.


In the 17 November 2013 article Surprise! Mayor and Project Connect select same routes they wanted in the first place, we expressed skepticism about “the selection of a predominantly questionable array of data elements as the basis for ‘evaluation’ of the various sectors. Leaving their ‘weighting’ aside, in the aggregate the evaluatory elements themselves are inappropriate.”

As the article explained,

ProCon relies very heavily on projections of future conditions for their basic measures. As the rail advocacy group AURA (Austinites for Urban Rail Action) has explained in its evaluation guide, projections themselves are basically unreliable, risky, flaky, whereas, in contrast, “We believe use of the real-world, recently-observed data gives the more accurate and reliable picture of potential ridership, as well as the greatest viability for federal funding.”

… Beyond a roughly five-year horizon, projections for specific neighborhoods and similar chunks of real estate basically become unreliably speculative — which seems to be what we’ve actually been dealing with … a significant dollop of real estate speculation, given a kind of veneer of “techiness” by CAMPO and their land use/travel demand model package.

For decades, public transportation advocates have warned repeatedly about the “self-fulfilling prophecy” syndrome in this kind of transportation planning process. In the past, it’s been applied mainly to highway development — justifying “future growth” in just the right places where developers want to build, so as to rationalize huge investments in new freeways and other roads. And, lo and behold, these very projections somehow materialize after the transportation facilities are built, thus “proving” the “validity” of the projections!

Today, in Austin, this process may be at work justifying speculative land development in certain areas of the central city (i.e., the central study area — “Central Corridor”), this time with the added drawback of ignoring or dismissing opportunities for redevelopment of areas in the heart of the core city, particularly centered along the Guadalupe-Lamar corridor.

As an example, in our article “Highland” sector favored by Project Connect — but where’s the travel demand? (19 November 2013) we noted that Project Connect’s presentation of CAMPO travel demand data in their own Map Book contradicted the claims of high travel demand in the “Highland” sector — one of the key underpinnings for their “recommendation” of a route to serve this fabricated sector. Thus, we warned, “since Project Connect based its assessment significantly on this data, the results presented, and the contrary evidence of very strong travel demand in the Guadalupe-Lamar corridor, contradicting Project Connect’s own stated conclusions, should at the very least raise questions about the competency and integrity of the study process.”

As we summarized the pattern in What’s with Project Connect’s “2.9 million daily ridership” projection?

Another way of saying this is that Project Connect’s planners have converted their own wishful thinking into actual data inputs, that are then deployed to make their evaluation. Wishes are used to try to make the wishes come true.

► Applying subjectively derived scores

Despite the characterization by supporters that Project Connect’s efforts were thoroughly “data-driven” and “scientific”, some components of their “study” were not even camouflaged as “projections” or externally derived data, but instead were presented merely as subjective judgements of the project team. In our 3 December 2013 “data dig” Questions for Project Connect, we asked

Project Connect’s “Physical Constraints” metric appears to be based on totally subjective value assessments, and no information has been given as to how these value judgements have been developed. Where’s the factual basis for this?

The response was that these scores were based purely on the team’s “professional judgement”. We highlighted this on our article Memo to CCAG: “Pause” study or include “Lamar” sector:

The study has assigned an extremely high “Constrained Right-of-Way” penalty to the “Lamar” sector, but not to the “Highland”, “Mueller”, “ERC” sectors — apparently implying that Project Connect considers there to be no “Constrained Right-of-Way” problems for “Highland”, “Mueller”, and “ERC”. This also is implausible, and this penalty seems to be arbitrarily applied to sectors (“sub-corridors”) that the Project Connect team dislikes (e.g., “Lamar”), but withheld from sectors they seem to prefer (e.g., “ERC”, “Highland”, “Mueller”).

► Selective manipulation of data

Another practice skewing Project Connect’s “study” results was their “cherry-picking” of data categories and their selective manipulation of their own methodology — pre-eminently, the Transit Orientation Index model they appropriated from Portland. As we explained in our analysis What’s with Project Connect’s “2.9 million daily ridership” projection? (16 December 2013):

Apparently in an attempt at a gesture toward some kind of prediction of future transit ridership, one of the metrics Project Connect decided to use in their Comparison Matrix is a “Transit Orientation Index” (TOI), a ridership demand assessment model developed in 1997 by consultants for Portland, Oregon’s TriMet transit agency. …

According to the documentation, the TOI metric is envisioned to assess transit ridership demand at the level of a small analysis zone …. Project Connect planners, however, have applied the model to considerably larger sectors covering several square miles with hundreds and even thousands of acres.

We’d previously summarized the astounding problem with the TOI model in our Memo to CCAG: “Pause” study or include “Lamar” sector, which warned that, when key projections, already embedded in the Evaluation Matrix, were plugged into the TOI,

… the results are extremely implausible — e.g., for the “ERC” (East Riverside) sector, Project Connect calculates high total daily transit ridership of 2.9 million, about equal to the total citywide daily ridership of Chicago and Philadelphia combined. (Their “low estimate” for that single sector is higher than the total citywide ridership of entire cities like Denver and Seattle.) This strongly tends to corroborate other evidence that Project Connect’s projections have been seriously exaggerated and are utterly implausible.

Likewise, in Project Connect Needs an Overhaul we observed:

Rather than developing conservative, reliable, and plausible forecasts, Project Connect has produced exaggerated, highly questionable projections, heavily skewed toward certain geographical areas. When these same projections are plugged into Project Connect’s own Transit Orientation Index (TOI), the results are ridiculously unbelievable. For the single “ERC” sector, the low-end prediction of daily transit ridership is higher than the total system daily ridership of entire cities like Denver and Seattle. On the high end, it’s about equal to the total system daily ridership of Chicago and Philadelphia combined.

These implausible outputs from the TOI were jaw-dropping. When the projections of Year-2030 population, employment, and other data items that were mainstays of their Evaluation Matrix were fed into the model, even the low-end results were absurd. For the “ERC” (East Riverside) sector, for example, as we pointed out in our What’s with Project Connect’s “2.9 million daily ridership” projection? analysis, “… the low-end figure — daily ridership of 492,682 (493K) — is equally preposterous, exceeding the total system daily ridership of entire large cities.” These cities included Portland, Seattle, Denver, and Atlanta.

As for the Highland sector, TOI results were likewise other-worldly. As we noted,

…the TOI model results for 2030 are similarly off the scale. Whereas current 2013 ridership is about 5K (5100/day), the “low” TOI prediction for 2030 is about 127K — an increase of 2,440%. The “high” prediction (no need for upper-bound substitution in this case) is 279K — a predicted increase of 5,480%.

Put another way, to meet the lower-end ridership suggested by the demographic and economic projections, average daily ridership in the “Highland” sector would have to exhibit sustained average daily ridership growth of about 7,200 each year for 17 years.

Curiously, while the project team excluded such embarrassing outputs from the TOI model from their matrix, they were selectively using other aspects of the TOI as inputs for the same matrix. As we noted,

… Project Connect’s matrix does use the TOI, itself based on the same dubious projection inputs, to render a metric score to bolster their preferred sectors (“sub-corridors”) in the competition they’ve set up. …

But, even more importantly, the TOI for 2030, dependent as it is upon Project Connect’s “projections” (de facto fantasies), exposes their absurdity. No wonder Project Connect and its entourage don’t want these used … no wonder they attempt to distance themselves from them!

It’s very simple — plug Project Connect’s own projections into this otherwise fairly realistic model, and you get bizarrely, unbelievably exaggerated results. Maybe a hint that the original projections are bizarrely unbelievable?

In effect, the TOI is performing here somewhat like a “canary in the coalmine” — telling Project Connect, and all of us, that something is terribly wrong with their demographic and economic projections for 2030.

Big Picture: Fraud

The impact of all these seemingly disconnected errors, missteps, omissions, and methodological shenanigans on a single portion of the “study” area is illustrated by the infographic at the top of this post, which focuses on several of the sectors surrounding the Guadalupe-Lamar travel corridor. (The so-called “Lamar” sector was widely misinterpreted as this corridor itself, but it was actually just a wide swath of urban real estate, stretching as far west as Shoal Creek Blvd., and embracing Burnet Road to the west as well as a segment of Guadalupe-Lamar in its eastern half — and neither of these two major travel corridors was examined.) As this graphic makes clear, the ground rules and methodology of Project Connect’s “study” very effectively prevented meaningful evaluation of this key, heavily traveled, central corridor.

From this grab-bag of colossal problems, your first assessment might be that Project Connect’s team was the rail planning equivalent of The Gang That Couldn’t Shoot Straight. Unfortunately, it’s worse. What actually emerges out of all this, from the vantage point of a year of hindsight, is a much more troubling image than mere ineptitude — by connecting the dots, the outline of a deliberate effort to deceive and to manipulate the “study” becomes unmistakable.


Kyle Keahey promoting "high-capacity transit" route selected by Project Connect, Nov. 2013. Photo: YouTube screengrab.

Project Connect Urban Rail Lead Kyle Keahey presenting “recommendation” of Highland-Riverside urban rail route, Nov. 2013. Photo: YouTube screengrab.


Contradictory as it might seem, it’s entirely plausible that otherwise technically competent members of the Project Connect team, drawn into the “trees” of the exercise, were unaware of the implications of the larger “forest”. Also the mind, with its ability to rationalize, justify, and alibi, can be a very mysterious apparatus.

In any case, the motives for tailoring the proposed urban rail route to the needs of development policies and interests are also very clear. These are described particularly in three of our articles:

Who are those guys? Real estate development interests and Austin’s urban rail boondoggle

UT should pay for East Campus urban rail — not Austin taxpayers

Derailing the Mueller urban rail express — Preamble to Project Connect’s 2013 “High-Capacity Transit Study”

So there’s motivation. There’s an amazing assortment of jaw-dropping methodological botch-ups. And it all fits together to promote the desires of the sponsors of the exercise.

The Big Picture we see of this whole process is dominated by a bright red fluorescent flashing sign. The sign says: Fraud. This is definitely a model of rail planning for other communities — a model to avoid at all costs. ■

h1

Derailing the Mueller urban rail express — Preamble to Project Connect’s 2013 “High-Capacity Transit Study”

2 November 2014
Urban rail concept started as a plan for a streetcar "circulator" system, shown in this early map from 2006. Map adapted from Austin Chronicle.

Urban rail concept started as a plan for a streetcar “circulator” system, shown in this early map from 2006. Map adapted from Austin Chronicle.

To understand the roots of the Highland-Riverside urban rail plan on the ballot today, you need to understand how an official “express train” planning process, aiming to lock in an urban rail line to the Mueller redevelopment site, got derailed and sidetracked by community intervention. Here’s a very abbreviated version of the story.

Austin’s current “urban rail” planning arose ca. 2005-2006 following the November 2004 voter approval of Capital Metro’s “urban commuter rail” project, in a package (including “rapid bus” service) called All Systems Go proposing the operation of DMU (diesel multiple-unit) railcars between downtown and the suburb of Leander. The previous light rail (i.e., urban rail) plan for a line on Guadalupe, North Lamar, and the railway alignment northwest as far as McNeil had been shelved in mid-2003 in favor of the cheaper, but very bare-bones, DMU plan.

Since the newly approved DMU line ran on a railway alignment that bypassed most of the heart of the city, ending only at the southeast corner of the CBD, officials and planners realized they needed some way to connect passengers with key activity points, including UT and the Capitol Complex. The answer they devised was a “circulator” system using streetcar technology, which would intersect with the DMU line (eventually rebranded as MetroRail) and connect to downtown Austin, the east side of the Capitol Complex, the East Campus of UT, and the Mueller development site. (See map at top of post.)

But, critics asked, what about the dense West Campus neighborhood and the busy commercial district on The Drag? What about the original plan for light rail along Guadalupe and Lamar? The “rapid bus” service included in the All Systems Go package, intended as a precursor to rail in the Guadalupe-Lamar corridor, was then viewed only as a temporary “fix”, and it seemed clear that rail needed to be planned for that corridor as well.

Within Capital Metro, Lyndon Henry (then a Data Analyst with the transit agency) pressed the case for at least an initial rail line to serve The Drag and West Campus, and at public meetings on the proposed “circulator” Henry and others continued to raise the issue. In this period, as problems emerged with the MetroRail project, Capital Metro’s involvement in the streetcar project was superseded by the City, which assumed control. When Henry’s supervisor Matt Curtis left Metro to become an aide to Mayor Lee Leffingwell, for a brief period a West Campus spur did appear in City of Austin planning maps for the proposed streetcar. (Henry is currently a contributing editor to this website.)

In 2008, as a line on East Riverside to ABIA, with a bridge over the river into the CBD, was proposed, planners became convinced that capacity and speed required fullsize light rail transit (LRT) rolling stock. However, apparently to distinguish the emerging plan from the original, centrally routed Guadalupe-Lamar line, and to retain some of the supposed lower-cost ambience of streetcar technology, the expanded system was dubbed “urban rail”, supposedly a hybrid between a streetcar and a rapid LRT system. By 2010, the Central Austin Transit Study (CATS), prepared by a consortium headed by URS Corporation, recommended a system that stretched from the Mueller site, down Manor Rd. and Dean Keeton to San Jacinto, then south through the East Campus, across the river, and out East Riverside to ABIA. Alternative alignments were suggested, and spurs to Seaholm and the Palmer Auditorium area were also proposed as later extensions.

As the project made its way through the National Environmental Protection Act (NEPA) process, and afterward, the route structure gradually solidified; for a connection to Mueller, a preference was emerging to move the alignment from Manor Rd. to a route via Red River and Airport Blvd. But even the gesture of a spur connection to the West Campus began to vanish, prompting Lyndon Henry and the Light Rail Now Project to call attention to the need for urban rail in the “Missing Link” — the gap between MetroRail’s station at Crestview and North Lamar, and its terminus downtown. Because of that gap, not only were passengers inconvenienced by having to transfer to buses to access their destinations along the Guadalupe-Lamar corridor, but also Capital Metro was running costly bus shuttles to connect MetroRail stations on the east side to the UT campus and the Capitol Complex. See: Give priority to “Missing Link”.


MetroRail Red Line (red) skirts entire heart of central Austin, illustrated by "Missing Link" through Guadalupe-Lamar corridor. Urban rail would provide the crucial connections to core neighborhoods, UT West Campus, and Capitol Complex missed by MetroRail. Infographic Map by Light Rail Now.

“Missing Link” urban rail (green), in Guadalupe-Lamar corridor, would provide the crucial connections to core neighborhoods, UT West Campus, and Capitol Complex missed by MetroRail (dashed red line). Infographic Map by Light Rail Now.


But why had the West Campus, and Guadalupe-Lamar, disappeared from the official urban rail plan? As Henry, Dave Dobbs, Andrew Clements, Roger Baker, and others persistently raised this issue, mainly at meetings of the Transit Working Group (a blue-ribbon committee of civil leaders nominally attached to CAMPO, the Capital Area Metropolitan Planning Organization), planners and officials under the aegis of the Project Connect public agency consortium pointed to a Route Alternatives Evaluation Process included in the 2010 CATS project that had supposedly ruled out a “University of Texas (UT) to North Central Austin (Hyde Park)” route, instead giving top scores to routes serving Mueller, East Riverside, and Seaholm — basically, what City policy actually wanted.

Scrutinizing the “Route Alternatives Evaluation”, Henry identified serious methodological drawbacks and summarized these in a commentary, City’s Urban Rail “alternatives analysis” omitted crucial Lamar-Guadalupe corridor! presented to the TWG on 27 April 2012. These problems are also discussed in our article City’s 2010 urban rail study actually examined corridors! But botched the analysis… (26 November 2013). Basically, the 2010 “evaluation” totally ignored the Guadalupe-Lamar corridor, and “evaluated” an array of alternatives with subjective ratings of 1, 2, or 3. Thus, voila! The preferred official routes, including the route to Mueller, won the “competition”!


CATS map of actual potential rail corridors studied. Map: COA and URS.

CATS map of potential rail corridors studied — but Guadalupe-Lamar was omitted! And subjective scoring system facilitated ratings that favored City’s desired route plan. Map: COA and URS.


In what seemed like an Urban Rail Express to Mueller, by May 2012, the official urban rail proposal had gelled into a Phase 1 project running 5.5 miles from downtown, through UT’s East Campus via San Jacinto, then northeast via Red River St., 41st St., and Airport Blvd. into the Mueller site. The total investment cost was estimated to be $550 million.


Finalized in May 2012, 5.5-mile, $550-million Phase 1 urban rail starter line was proposed to connect downtown, UT East Campus, Hancock Center, and Mueller site. Graphic: Project Connect.

Finalized in May 2012, 5.5-mile, $550-million Phase 1 urban rail starter line was proposed to connect downtown, UT East Campus, Hancock Center, and Mueller site. Graphic: Project Connect.


But the constant pounding by community critics — especially Lyndon Henry’s exposé of the outrageously dubious Route Alternatives Evaluation from 2010 — was taking its toll. The result was that Project Connect placed the Mueller Phase 1 plan on hold and shifted course dramatically. In early 2013, Kyle Keahey was hired as Urban Rail Lead to head a new “High-Capacity Transit Study”, tasked with supposedly re-evaluating everything, racing through a process (with a presumably more competent and defensible methodology) that would result in a recommendation by the end of 2013.

To some, it seemed a new beginning and a possibly more hopeful and fair approach to analyzing travel corridors, particularly the heavily traveled, high-density, and widely popular Guadalupe-Lamar corridor. Unfortunately, that was not to happen. As it proceeded, it became increasingly clear that the much-vaunted “High-Capacity Transit Study” was actually a fraud. The highlights of this process will be summarized in a subsequent report. ■

h1

UT should pay for East Campus urban rail — not Austin taxpayers

2 September 2014
Project Connect map showing half-mile radius from proposed urban rail stations. Except for a mainly commercial and retail sliver along the Drag, most of high-density West Campus residential neighborhood is beyond station access radius.

Project Connect map (annotated by ARN) showing half-mile radius from proposed urban rail stations. Except for a mainly commercial and retail sliver along the Drag, most of high-density West Campus residential neighborhood is beyond station access radius.

By Lyndon Henry

The following comments were made during Citizen Communications to Project Comnnect’s Central Corridor Advisory Group (CCAG) on 13 June 2014 regarding Project Connect’s proposed 9.5-mile, $1.4 billion urban rail starter line connecting East Riverside (southeast) with the Highland ACC site now under development (north). Ultimately, the group voted to recommend Project Connect’s proposal to the City Council.

Since 2006, UT has insisted on a San Jacinto route that would bolster its development aims for the East Campus. However, the West Campus is where the people are, with the third-highest residential density in Texas. It’s where the heavy travel flow is, and where most activity is clustered. And the FTA-required half-mile demographic “watershed” around proposed urban rail stations on San Jacinto barely touches the eastern edge of the West Campus. (See map at top of this post.)

Meanwhile, although insisting that its East Campus development program must be served by Austin’s urban rail, the UT administration has not offered a dime to fund it. Instead, they’ve happily assumed that Austin taxpayers can obligingly be squeezed with higher property taxes to pay for this amenity.

There’s a “reverse-Robin-Hood” aspect to this. Because of shale oil extraction on Permanent University Fund lands, according to a San Antonio Express-News report last year, “The University of Texas System is rich. … Oil is the reason why.”

The UT system is awash in money to the tune of a billion dollars a year, boosting UT Austin’s share to a total of nearly $200 million. Profits from football and other athletic entertainment bring in another $78 million a year.

While there are certainly various needs for this money — particularly the need to keep tuition costs affordable — and some constraints on how it’s used, it would seem logical and fair that, if UT desperately wants urban rail in the relatively less dense, less active San Jacinto route, UT should dip into its own resources to pay for it.

An East Campus-Medical School alignment could be installed as a branch from the Guadalupe-Lamar alignment proposed as an alternative to Project Connect’s plan. UT could cover the $45 million local cost in five years by modest annual dollops of $9 million from its abundant revenues.

This compromise alternative could buttress the feasibility of urban rail and increase the benefit to the entire Austin community. But UT’s administration needs to stop trying to soak Austin taxpayers, and take responsibility for funding its fair share of what it wants.

h1

Reality Check: How plausible are Project Connect’s time/speed claims for Highland-Riverside urban rail plan?

24 August 2014
LEFT: Phoenix's Metro LRT — similar to Project Connect's proposed Highland-Riverside line — runs almost entirely in street and arterial alignments, with maximum speed limits, traffic signal interruptions, and sharp turning movements that slow running speed. Average schedule speed: 18.0 mph. (Photo: OldTrails.com)  RIGHT: Charlotte's Lynx LRT runs entirely in an exclusive alignment following a former railway right-of-way. Average schedule speed: 23.0 mph. (Photo: RailFanGuides.us)

LEFT: Phoenix’s Metro LRT — similar to Project Connect’s proposed Highland-Riverside line — runs almost entirely in street and arterial alignments, with maximum speed limits, traffic signal interruptions, and sharp turning movements that slow running speed. Average schedule speed: 18.0 mph. (Photo: OldTrails.com) RIGHT: Charlotte’s Lynx LRT runs entirely in an exclusive alignment following a former railway right-of-way. Average schedule speed: 23.0 mph. (Photo: RailFanGuides.us)

In a Blitzkrieg of promotional presentations over the past several months, Project Connect leaders and team members have been touting ambitious travel time and average speed projections for their urban rail project proposed to connect the Highland ACC site with the East Riverside development area. In various presentations, the agency’s Urban Rail Lead, Kyle Keahey, has claimed that the line would provide an average speed of “21 to 22 miles per hour” (impressive, compared to an average of about 25 mph for motor vehicles in urban traffic, and typical local bus transit averages of about 12 mph generally and 4-8 mph running through a in a CBD).

In terms of travel time on Project Connect’s proposed line, the agency has detailed the following:

• From the East Riverside terminus at Grove to the Convention Center downtown (3.9 miles) — 11 minutes

• From the Convention Center to the ACC Highland campus (5.6 miles) — 17 minutes


Screenshot from Project Connect's June 23rd presentation to Capital Metro board, showing travel time claims for proposed urban rail project.

Screenshot from Project Connect’s June 23rd presentation to Capital Metro board, showing travel time claims for proposed urban rail project. (Click to enlarge.)


However, several anomalies immediately leap out to experienced public transit analysts. First, the distance and time projections provided by the agency — totaling 9.5 miles in 28 minutes — imply an average speed of 20.4 mph, not the “21-22” claimed by Kyle Keahey and other representatives. Second, even an average speed of 20.4 for this type of light rail transit (LRT) service in this kind of application raises professional eyebrows (and considerable skepticism) — mainly because it’s significantly higher than what is commonly characteristic of peer systems.

Light rail transit planners commonly know that lines routes in street and arterial alignments, even reservations, face substantially more constraints to speed than do systems routed in exclusive, private right-of-way (ROW) alignments such as railway corridors, tunnels, viaducts, etc. (This is illustrated in the photo composite at the top of this post.) Some major constraints include: maximum speed limited to traffic maximum speed; operation constrained by traffic signals and cross-traffic; sharper curves and turning movements as route follows street grid. Compared with routes in exclusive alignments, the differentials usually aren’t tremendous, but enough to make a difference in schedule speeds, travel times, and other performance factors.

To illustrate this, and perform a rough comparative analysis, we’ve compiled average speeds from two sources. The first is a comparison on the Light Rail Now website, in an article titled Light Rail Schedule Speed – Faster Than Bus, Competitive With Car, with speeds summarized in the following table:


Table of LRT average schedule speeds from Light Rail Now website.

Table of LRT average schedule speeds from Light Rail Now website.


The second source is a recent compilation by Light Rail Now publisher Dave Dobbs, summarized with route lengths, average stop spacing, travel times, and average speeds, in the table below:


Table of LRT average schedule speeds and other data compiled by Dave Dobbs.

Table of LRT average schedule speeds and other data compiled by Dave Dobbs. (Click to enlarge.)


Dave notes that he included the lines he did “because they were examples from Project Connect slides.” He also points out that Project Connect’s East Riverside-to-Highland line “is virtually all street running save for the tunnels and the bridge and I don’t see that much time saving there.”

Indeed, Project Connect’s proposed line is far more of a winding, meandering route, with more traffic speed constraints and sharper turning movements, than any of the comparative peer street-running systems. It includes running in mixed traffic (Red River St.) as well as a segment through the UT campus (San Jacinto Blvd.) with heavy student pedestrian traffic crossing the alignment.

LRT systems are identified with the following designations:

BAL — Baltimore
CHA — Charlotte Lynx
DAL — Dallas DART
HOU — Houston MetroRail Red Line
LA — Los Angeles
MIN — Minneapolis-St. Paul Metro
NFK — Norfolk Tide (Hampton Roads Transit)
PHX — Phoenix Metro
SEA — Seattle Link
SLC — Salt Lake City TRAX

To simplify this comparison, we’ve included clearly identifiable route segments from both table sources, and differentiated them into Predominately Street Alignment and Predominantly Exclusive Alignment categories. For several individual systems, segments are identified in our charts as follow:

Dallas
CBD — West End to Pearl/Arts
Green Line A — West End to Fair Park
Blue Line A — West End to Ledbetter
Blue Line B — West End to Corinth
Blue Line C — Corinth to Illinois
Red Line A — CBD to Plano

Denver
Littleton — CBD to suburb of Littleton

Houston
Red — Red Line

Los Angeles
Blue — Blue Line, CBD to Long Beach

Minneapolis
Blue — Blue Line, Hiawatha
Green — Green Line, Minneapolis-St. Paul

Salt Lake City
701 — Medical Center to Ball Park
704 — West Valley Central to Airport
Sandy — CBD to suburb of Sandy

Using the data from these tabular compilations, we’ve presented a comparative summary of average schedule speeds in the following two graphs. Speed data values (mph) have been rounded to a single decimal point. The first graph presents a comparison of various predominantly street-running lines, similar to Project Connect’s proposed project. This includes an average for the actual, operating peer systems. The second graph presents average speeds for various lines and line segments in exclusive (mostly railway right-of-way) alignments. (Click either graph to enlarge.)


5_ARN_Chart-LRT-mph-street


6_ARN_Chart-LRT-mph-exclusive-rev


From this comparison, it can be seen that the average speed for Project Connect’s Highland-Riverside line, based on the projected travel time presented by the agency, is significantly above all of the peer systems running predominantly in street right-of-way. Not only does Project Connect’s line show a higher average schedule speed than any of its peer systems, but it’s a full 6.4 mph — nearly 46% — above the peer average. This seems highly implausible, particularly in view of the more convoluted, tortuous profile of the proposed alignment and the other encumbrances we’ve cited. Indeed, the travel time (and implicitly schedule speed) assumptions of Project Connect planners seem more appropriate for the operating characteristics of a route in predominantly exclusive right-of-way rather than running on streets and arterials, as they’ve designed it.

Projecting reasonably accurate travel times and speeds is important to planning any rail transit project, and not just because of plausibility with respect to public scrutiny. Travel time constitutes one of the key inputs into the ridership modeling process. Underestimating travel time, by reducing what’s called the “impedance” to the process of calculating trip generation and modal split, can readily lead to overestimation of ridership. In addition, slow travel speeds also raise the possible need for additional rolling stock to fulfill train frequency and passenger capacity requirements.

Bottom line: Project Connect planners may be estimating faster train travel speeds and shorter travel times than is realistically plausible, and the implications may be lower ridership, greater rolling stock requirements, and possibly higher operating costs than they’ve originally projected.