Quote:
Originally Posted by Future Mayor
It isn't only the SLC metro that this is occurring, it is happening in nearly every metro in the nation. I am however not defending it by any means. One issue is that, while yes there is a lot of sq footage out there, the need has come in waves and as that demand has occurred the need has been met. It is more affordable to build a 3-12 story office building and fill that space as opposed to building a 20+ story office building in downtown. Pre-leasing #'s have to be greater and the cost of land is greater. I agree that something needs to be done to attempt to curb it, however I think it will naturally take it's course. As transit increases in the metro, all leading to DT, and as housing continues to increase DT, there will be a greater desire and need for businesses to locate in the DT area, and that will increase the need for more office space. Businesses like to locate near their potential work base or as near to as possible. As transit increases and downtown residential numbers increase the amount of workers that can access downtown will increase. I honestly expect another 20+ story tower announcement in SLC within the next 2 years.
|
This is happening in almost every metro in the U.S. If you drive around Denver's beltways, you will see far more suburban mid-rise oasis-type developments than Salt Lake. In fact, they have one that has more combined office space than down town SLC as a whole - and it's 10-15 miles out from down town Denver!
I think this is inevitable and not necessarily a bad thing. Agreed, it should be limited. I think that places like down town Sandy, the Cottonwood Hights development, the Murray IHC complex and surrounding office complexes, Ft Union, Sugar House, West Valley near the airport, Daybreak, and Jordan Landing should have both height and acre limitations to keep them from sprawling too much as well as good connections. I don't have a problem with such developments if they are contained into a confined area with height limit requirements and easily accessible.
Seeing as only two of the afore mentioned developments are/will be walkable (Sugar House and Daybreak), I think that is something that could be better integrated into such developments, though not all. Areas like Jordan Landing and West Valley near the airport, and along I-15 are supposed to be auto-centric and are ok so far as growth limits are set. I encourage SLC to provide incentives (as I am sure they are already doing quite well) to bring businesses down town. As I have said on here before, the whole metro model is designed to accomidate all types of developments and building styles to attract the most businesses. Not all businesses can aford, or even need a down town-style tower. Some are attracted to an area adjacent to an airport, a freeway, and/or in a cheaper suburban location. This model makes the SLC area as a whole more competetive to other metros, which benefits all parties within the metro in the macro.
As to the view concerns with the Cottonwood Hieghts development, I recognize them as valid concerns, but don't think that the "view" should dictate how developments are planned and built. IMO, it is something that should be factored in and be on the "it-would-be-nice-if" list, but not the sole reason a development is able to develop or not. Traffic and accessability concerns are deffinately a much more important issue than obstructing the view. As Tangled put it, you shouldn't be admiring the view while you drive anyway. Sandy gets some heat on here for traffic problems, which I won't deny exsist, but with commuter rail on its way, light rail, two freeway exits, and four 4-6-lane surface streets (State, 7th E, 106th S, and 90th S), it has much more access than this Cottonwood Heights development has. I would have to agree that the Cottonwood Heights development as a whole was poorly planned and that building this tower will only aggrivate existing problems. I think it can get by as it is currently, but building this tower will really complicate things. I guess we'll see what happens