PropertyValue
?:author
?:datePublished
  • 2010-11-15 (xsd:date)
?:headline
  • Sierra Club says killing high-speed rail project will cost almost 10,000 permanent jobs in Wisconsin (en)
?:inLanguage
?:itemReviewed
?:mentions
?:reviewBody
  • The debate over the proposed high-speed rail line from Milwaukee to Madison percolated during the campaign for governor. It flared up on the eve of the election, and has raged since Republican Scott Walker was elected Nov. 2, 2010. Walker wants the project stopped, even if it means rejecting $810 million in already-approved federal money. After state officials signed contracts in a pre-election push to ensure the project moves forward, outgoing Gov. Jim Doyle has backed off -- but argues ending the project will cost taxpayers $100 million. Milwaukee Mayor Tom Barrett, who lost to Walker, has said the city will consider legal options if the train is killed. Virtually everyone has entered the fight, often wielding statistics to argue their point. That includes the Sierra Club’s Wisconsin chapter. Weapon of choice: Jobs. In a news release and a petition , the Sierra Club argues if the state turns down money for high speed rail, it will kill nearly 10,000 permanent Wisconsin jobs. If PolitiFact had sound effects, we’d add a loud whistle here. As in, that’s a lot of jobs. And as in, let’s have a timeout and get to the bottom of this. Many different job-related statistics have been bandied about in the debate. The state Department of Transportation estimates there are the 13,719 jobs involved in construction, engineering, design and train manufacturing tied to the project. On the campaign trail, Walker argued the project would create only 55 permanent jobs, declaring in an open letter to President Barack Obama on his notrain.com web site: That’s $14.5 million per job, not including any hidden costs! There, Walker is talking about jobs on the train line itself -- conductors, engineers, ticket-takers and the like. In making the claim, he is purposely choosing the smallest possible number to make his point. But what of the nearly 10,000 permanent jobs claimed by the Sierra Club and others, some of whom are now citing the Sierra Club as the source of the number? These are jobs not tied directly to the project and as such are hardest to measure hardest to quantify. Yet the group offers a very specific number: 9,572. The number comes from a 2006 economic analysis prepared for Amtrak and nine states, including Wisconsin, a group called the Midwest Regional Rail Initiative. The study, prepared by Transportation & Economics Management Systems, became part of the state’s application for the train funding. The study says: The development of the system integrates so many communities, and provides such a wide reaching impact that it will generate on its own a 0.1 percent growth to the region’s economy. The sweeping conclusion: It will support existing manufacturing and service industries and will foster the growth of new small businesses across the Midwest because of the improved access between communities. It will encourage large businesses to distribute their operations more widely across the Midwest and reap the benefit of providing more efficient ‘back shop’ operations in the highly accessible smaller communities. OK, but how do you quantify all that? If you dig into the study, you find it is based on numerous assumptions and applies multipliers and other formulas to come up with a bottom line: Expanded train service would create 58,000 jobs in the nine states, boost property values by $5 billion and increase urban household income by $1 billion. Let’s look at some of the factors and underlying assumptions, with an eye toward how the Sierra Club and others are using them when they claim 10,000 permanent jobs are at stake with the Milwaukee to Madison line. Size of the system The numbers are based on the prospect of a fully-built system throughout the Midwest. That is, it’s not just high-speed rail from Milwaukee to Madison, but Chicago all the way to Minneapolis. And Chicago to St. Louis. And ultimately connections to Omaha, Kansas City, Indianapolis, Detroit, Cleveland and more. It even includes a spur to Green Bay, with proposed stations in Menomonee Falls, Fond du Lac, Neenah and Appleton. That piece alone accounts for 3,200 jobs in the study, some of which overlap with the Milwaukee jobs. But the federal funds allocated so far only cover some pieces of the plan. And there is no certainty the full system will ever be built -- in Ohio, Governor-elect John Kasich has vowed to block the Cleveland to Cincinnati to Columbus piece. So, even if Walker were to have a change of heart, the system may be smaller and have fewer connections, which could mean its jobs impact is smaller as well. Jobs gained, jobs lost The study suggests that new jobs and opportunities will develop around the new route, as more people take advantage of the high-speed connections. However, as people board the train they are taken off the highways and don’t as often take to the skies. But the study counts only the new jobs, not any lost ones. How many airline pilots or contractors renovating terminals will not be needed? said Steven E. Polzin, of the Center for Urban Transportation Research at the University of South Florida, an expert on rail proposals, whose group has been criticized for favoring cars and roads. How many auto workers, gas station attendants, road contractors, etc. So, part of the equation is missing. Stations as economic hubs The study assumes that stations will become economic hubs, prompting other businesses to create jobs nearby. But the stations envisioned are no sure thing. For instance, the initial Madison station was to be near the airport -- not ideal for someone headed to the Capitol. Now it’ll be in the city center, but going into the city slows down a traveler from Milwaukee to Minneapolis. Leaders of some cities, including Brookfield and Wauwatosa, have said they don’t even want a proposed station. So, more uncertainty. Other travel options If the price of gas remains relatively low, there will be less incentive for travelers to get out of their cars and board the train. Indeed, cars may be able to make the trip faster -- assuming there’s no traffic congestion. Initial train speeds are planned to be 79 miles an hour, not including stops; the train would run at higher speeds later. Whats more, Mitchell International Airport is enjoying an air carrier -- and airfare -- war, which has helped it attract more passengers than ever. There is no telling how long that will last, but low air fares could have an impact on who grabs the train. Polzin, who reviewed the study at the request of PolitiFact Wisconsin, said it appeared to be professionally done, using methods that are generally accepted. He noted that such studies are usually done to build support for a project and look exclusively at the benefits of the specific option, not the comparative benefits of other options or directing those resources to others purposes. Indeed, the state Department of Transportation has not highlighted the 10,000 permanent jobs figure, focusing instead on construction-related jobs for the Milwaukee-to-Madison line. That’s work that we did ourselves, said Cari Anne Renlund, executive assistant for the state DOT. We need to talk about what we know is real. We’ll leave Projection Land and return to reality as well. The Sierra Club’s Wisconsin chapter and others say killing the high-speed train will kill jobs, specifically 9,572 permanent ones. Their number is taken from a professional analysis, but that analysis is based on a host of assumptions -- including that an entire Midwest network is built -- many of which could change. And while the Sierra Club suggests the jobs are an immediate loss, the report itself puts them years into the future. The Truth-O-Meter isn’t a crystal ball. But it’s got a present-day rating that fits this claim: Barely True. ( Note : Paragraph three of this item was changed on Nov. 16, 2010 to more closely reflect what Mayor Barrett has said in regard to the train and the city's options.) Editor's note: This statement was rated Barely True when it was published. On July 27, 2011, we changed the name for the rating to Mostly False. (en)
?:reviewRating
rdf:type
?:url