Quote:
Originally Posted by PITairport
The thing about airports is they are responsible for far more indirect jobs than they are direct jobs. So while PIT took a hit on direct jobs with the de-hubbing, it is still one of the regions largest economic engines. No airport? No Google. It really is that simple.
|
Well, no, actually, that is clearly an oversimplification.
Obviously decent airport service is a necessary condition for all sorts of job growth, but you are turning that rather obvious point into something much less true by then claiming the airport is "responsible" for those jobs or the "engine" for those jobs. Rather, the most you can say for most of those jobs is that it is one of many contributing factors.
In any event, all of that is beside the point when it comes to transportation policy. Every day, the hundreds of people who work at Google in Bakery Square need to get there from their homes. So do the almost 300,000 people who work at other jobs in the City. And so on.
On occasion, some of those people may also need to get to the airport, from home or their place of work, and so might visitors need to do the opposite. But for the vast, vast majority of jobs locations, the numbers of trips employees take to their place of work outweighs the number of trips those employees or visitors take to the airport, usually by orders of magnitude.
So even if in some vague conceptual sense you view the airport as being partly "responsible" for those jobs "indirectly", the crucial point is we just don't need the same sort of transportation infrastructure leading directly to the airport when those jobs are not in fact located there.
Honestly, this point should be utterly uncontroversial. The de-hubbing of PIT and resulting massive shortfall in expected "direct" jobs OBVIOUSLY should cause us to reconsider our airport-related transportation plans. It isn't rational to pretend that sort of change in expectations should have no impact at all.
Quote:
|
So while PIT is kinda out there in the sticks, it needs to be as viable a facility as possible, and that includes improving access from the south and east which is why I support the complete Southern Beltway.
|
Again, you are just not grappling with the need to do actual cost/benefit analysis or consider alternatives with higher priority. In other words, your "as possible" qualifier should include consideration of those factors before reaching your conclusion about whether any given airport-related transportation project is actually justifiable.
For example, I think it is obvious that at least as strong (I'd argue much stronger) argument can be made for the universities and hospitals in Oakland being "responsible" for a lot of regional jobs, the "economic engine" for a lot of regional jobs, and so on. Accordingly, by your logic it should also be a priority to provide Oakland with the best possible access, which because of road and parking constraints means we should be investing in robust rapid transit to Oakland.
I realize it is tempting to just say, "OK, let's do it all!" But again, in a world of budget constraints, you can't just do it all, certainly not right away.
So the question at hand is whether it makes sense to be spending $600+ million on the Southern Beltway now, and necessarily putting off many other possible transportation projects as a result. And that is a question that you have not yet come close to grappling with.
Quote:
|
Highway discussions get lost in talk about sprawl and transit priorities when the topic should be the original purpose - the movement of goods and services. Companies do not move manufactured goods on a subway or bus. Suburbanites commuting are only part of the picture wrt highways.
|
I absolutely agree we should be thinking about highways in terms of moving freight and not passengers, particularly between cities and not within urbanized areas.
The thing is, though, you can't justify the Southern Beltway as a freight-moving project--even less so, in fact. In large part that is because most freight traffic is less time-sensitive, and also more sensitive to things like tolls, than commuter traffic. And for the vast majority of possible freight users there are already alternative untolled routes that don't take much more time, particularly if you make a point of scheduling around commuting times.
Indeed, all this is already covered in the vehicle counts we have been discussing. Those are not necessarily limited to just personal vehicles, and at the end of the day the precise mix doesn't matter much--at those vehicle counts, it isn't going to be possible to justify the expenditure involved.
Quote:
|
My point with all those examples is that highways are integral to the overall transportation infrastructure, and in Pittsburgh the highways quite frankly 🞵🞵🞵🞵 compared to our peer cities. No amount of busways and light rail will fix that.
|
So suppose we grant that Pittsburgh is below global city standards in ALL major areas of surface transportation. Again, in a world without budget constraints, the conclusion would be obvious: Do it all!
But that is not our world, so we do have to prioritize. And blanket comparisons to other global cities won't help answer that question of priorities for Pittsburgh.