Cornell Showcase (NYC): Difference between revisions

From Tygron Preview Support Wiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 217: Line 217:
File:TransOfDevRights26.jpeg|Choose a Stakeholder
File:TransOfDevRights26.jpeg|Choose a Stakeholder
</gallery>
</gallery>
<pre style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
"We played a session to explore the topic of TDR in one scenario area in the Lower East Side. Kushan Dave (MRP, Cornell), Nicolas Grefenstette (MRP, Cornell), Swati Sachdeva (Urban Designer, UC Berkeley) played each as one of three stakeholders (Respectively the developer, city & NYCHA). The session lasted 40 minutes, and we focused on the Scenario 4 area (around Houston Street). As a reminder, the scenario overlay should be treated as a guideline, but it doesn't need to be enforced. The decision for these four areas comes from our previous research looking at land use, economic and transportation corridors, as well as from comments from various professors and professionals in NYC.
What you will see below is the narrative for this session, followed by detailed screenshots depicting each stakeholders' actions. We encourage you to explore the game yourself, as scenarios can greatly differ in length & size (depending on the choice of buildings)".
</pre>
<gallery>
File:TransOfDevRights27.jpeg|Starting Cinematic
File:TransOfDevRights28.jpeg|
File:TransOfDevRights29.jpeg|
</gallery>
The developer initiates the gameplay, by looking at the zoning/soft-site layer, identifying sites he might be interested in. By choosing to place a certain block, a prompt appears on the city's screen, asking him whether or not he will approve of the development (via permits). All stakeholders are aware of the impact of this building on various indicators (livability, affordability units, the quantity of air rights transferred and so on). At this point, the city should also be aware of the physical impact the developer's decision will have on the neighborhood. Before approving this building, stakeholders need to discuss the impact.
The first building is approved, and the developer chooses to look at a different site. This time, the site is already built, so he needs to demolish the existing building first. The first two actions are repeated, as different stakeholders discuss the suitability of each building development. In the end, the city had approved the maximum allowed number of developments (effectively using all 800,000 sq ft of underused development rights from Baruch Campus). Please note that at all times, NYCHA can match the profits made from the sell of development rights to the costs of building community & ecological infrastructure on campus, suggesting that the profits made should be reinvested into NYCHA campuses (i.e. we could have also looked at maintenance).
At the end of the session, each stakeholder can look at his performance metrics for different indicators. This stage is crucial in determining whether or not different goals were satisfactory. We choose not to beam a comparison chart at the end, since the focus needs to remain on the topic of TDR, rather than focusing on an arbitrarily set score for stakeholders.
''Developer''
<gallery>
File:TransOfDevRights30.jpeg|Start screen
File:TransOfDevRights31.jpeg|Zoning
</gallery>
Analysis of potential receiver sites
<gallery>
File:TransOfDevRights32.jpeg|Building zone 13
File:TransOfDevRights33.jpeg|Applying for a permit
File:TransOfDevRights34.jpeg|Buying air rights from NYCHA
File:TransOfDevRights35.jpeg|Approved!
</gallery>
Closer study of the site
<gallery>
File:TransOfDevRights36.jpeg|Demolishing
File:TransOfDevRights37.jpeg|Deciding on placement
File:TransOfDevRights38.jpeg|Prepare for Development, Permit has been granted
</gallery>
Again, the city approves!
Eventually, several sites are proposed, and intra-stakeholder conversations start.
<gallery>
File:TransOfDevRights39.jpeg|Planning for Affordable and Market housing, waiting on a zoning permit.
</gallery>
Summary of tables shows the progress
<gallery>
File:TransOfDevRights40.jpeg|Total affordable and market housing built
</gallery>
We can see how different actions affected indicators throughout the game - for instance, the dip in the total units built curve above is due to the demolition of old housing, which inevitably affects the market/affordable housing quantity & mix.
<gallery>
File:TransOfDevRights41.jpeg|Progress in Livability
File:TransOfDevRights42.jpeg|Developer's total score, including shared indicators
</gallery>
''City of New York''
As you can picture, from the city's perspective, the role is mainly about regulation. Below, you will see what happens when the developer wanted to build a 15-storey building in a zone that only allows 13 floors (link to action from the developer's perspective, above)

Revision as of 12:44, 14 January 2016

Please note: This page is currently being updated.

Cornell Showcase

Introduction

Cornell small.png

The Cornell Masters in Urban Planning Studio focused on policy approaches that would allow the New York City Housing Authority (NYCHA) to raise revenues in order to repair buildings and address their residents’ needs.

Cornell students Kushan and Nico examined an innovative policy approach that would permit NYCHA to transfer the development rights to property within their ownership to adjacent areas. This approach has been used to support new parks but has never been used as a way of supporting affordable housing. They then created an innovative game in the Tygron Engine that tested the potential gains and acceptability of building up developing different surrounding areas. Several architects, planners and city officials who reviewed their work were impressed by their ability to show the key trade-offs involved through the Tygron platform. They have made their study open to the public. It is a great example of how the Tygron Engine can be used in major studies.

January 7th, 2015
Hi all,

We are two students studying City & Regional Planning at Cornell University in Ithaca, NY. As part of a semester-long urban design studio in NYC, we had the opportunity to engage with Tygron's tool for scenario planning. We explored various uses for the software on the topic of affordable housing and livability, looking at Tygron's potential for sparking key conversations in decision-making negotiations.

We then chose to see how we could use the software in a different way: moving away from its traditional purpose (which is to explore trade-off relationships, inform decision-making negotiations, and spark conversations over ownership and zoning, amongst other possibilities), we chose ‘simplify’ its use by exploiting its real-time modelling abilities on a specific topic: the impact of transferring development rights on the urban fabric.

In the following posts and over the next couple of days, we will showcase and summarize our study, and detail our use of the Tygron software.

Nicolas / Kushan
MRP

Preliminary Research

Premise

- In NYC, shortage of housing (market & affordable). - Since 2005, median rent increased by 11%, while median household income has slightly decreased. As a result, 47% of low-income renters heavily rent burdened. - Mayor De Blasio’s housing policies focus on the construction of new affordable units. - Our focus is on Baruch Houses, an affordable housing project in the lower east side, from which we want to potentially transfer unused development rights.

Challenge

- Challenge for developers: building market rate (and/or affordable housing) in a city where building sites are rare and costly. Little vacant land overall, and high cost of demolition – a limited number of smaller, older buildings that can be profitably demolished.

- Challenge for NYCHA: increasing profits to reinvest into capital projects and maintenance.

- Challenge for the city: historic preservation, maintaining urban fabric and neighborhood desirability. In addition, creating areas which are consistent in size and scale to define markets for the transfer of development rights.

Transfer of development rights (TDR)

- Baruch campus has 1.2 million sq. ft. of underbuilt land. - However, previous studies of the site lead us to estimate that 400,000 sq ft. of land will be developed via various infill interventions. - We make the assumption that the remaining 800,000 sq ft. can be used for TDR from NYCHA to LES.

Qualifying Sites

When identifying sites for TDR, different restrictions can be applied, for instance: - Location: o For Hudson River Park, TDR requirement to happen one block east of the park. o Historic districts o Special purpose districts: i.e. Hudson Yards, South Street Seaport - Age of buildings (i.e. only consider buildings built prior to 1970). i.e. East Midtown - Vacancy rates - Government Ownership, landmarks - Site Size: in the Theater District, sites had to be >25000 sq ft to be considered qualifying. In our example, we identify potential sites as being: - 50% or more under built (0-50% FAR) - Location: along main corridors of activity (used commercial overlay + nature of the street) - Site size: over 5000 sq ft. The recent zoning change of 2008 that increased maximum FAR in certain areas of LES partially explains a higher proportion of under built sites.

Receiver Sites
Neighborhood Transit Connectivity, Bus + Metro lines
Urban Fabric / Scale
Zoning


Introduction to the Game

Tdr1.png

The definition of Transferring Development Rights (TDR)

A transfer of development rights (TDR) allows for the transfer of unused development rights from one zoning lot to another in limited circumstances, usually to promote the preservation of historic build­ings, open space or unique cultural resources. For such purposes, a TDR may be permitted where the transfer could not be accomplished through a zon­ing lot merger. In the case of a landmark building, for example, a transfer may be made by CPC special permit from the zoning lot containing the designated landmark to an adjacent zoning lot or one that is directly across a street or, for a corner lot, another corner lot on the same intersection.

Source: NYC Department of City Planning http://www.nyc.gov/html/dcp/html/zone/glossary.shtml


DESIGN

Based on our previous research on the issue of TDR in the Lower East Side, we model LES + NYCHA campuses, taking into account the various zoning restrictions.

Introduction

Stakeholder Selection
Example NYCYA Stakeholder Information: in-game example
Starting Cinematic
Brooklyn Bridge

The game you are about to play explores the impact of the Transfer of Development Rights on the urban fabric. Tygron has been modified from its original use as a more holistic decision-making and negotiation tool to fit this purpose.

Please take a minute to read the context and gameplay below.

New York City has an acute shortage of affordable housing. The mayor of NYC has promised to preserve and build 2500 affordable units in the city. In the larger context of the city, the Lower East Side (LES) neighborhood provides an interesting potential that can absorb a large chunk of the city's housing needs - affordable as well as market rate.

LES has many under built sites (Built FAR < 50% Zoning FAR) which can potentially be densified to accommodate for new affordable as well as market housing. NYCHA (New York City Housing Authority) owns over 3 billion sq ft of land within the LES, on several housing projects along the waterfront. Almost all the NYCHA-owned sites are underbuilt, meaning they have additional building rights that can be transferred or sold through TDR (Transfer of Development Rights). In addition, NYCHA's current financial problem prohibits it from restoring their existing housing stock or build new affordable units - they would highly benefit from the profit generated from TDR.

In addition to the above mentioned premise, the game focuses on the sell of Baruch Houses' underused development rights: Baruch Houses is an affordable housing complex within the LES that has about 1.2 million air rights that can be sold to potential developers. Based on previous modelling exercises, an assumption made is that NYCHA would be willing to sell about 800,000 sqft of these development rights.

For the purpose of this game, the available building typologies are designed to borrow a certain amount of air rights from NYCHA every time they are built and depend on the existing height restrictions for a particular site. For example, a 15 story building built on a site that is zoned to allow only 8 story buildings will borrow 7 floors' worth of sq footage from NYCHA's underused stock (up to a maximum of 800,000 sqft). All the relevant profit numbers are derived from a real estate pro-forma tailored specifically to the LES.

Gameplay

The game consists of three primary stakeholders who partake in this entire urban design process - The City, NYCHA and the Private Developer - each with their own objectives and goals. However, the overarching goal of the game is to increase density in the LES while increasing affordability and being considerate of the urban fabric. The City should only approve buildings in zoned areas. Zoning is used here as a mock indicator of the existing maximum number of floors (before upzoning).

Building blocks are all coded A/B where:

A: # allocated to current zoning (i.e. 8, 13, 15, 22) B: # allocated to the new desired building height.

All Buildings contain 20% affordable units ('80/20' is a popular real estate choice in NYC, allowing for a mix for market rate and affordability in housing).

The game has four scenarios (or focus areas) where transfer of development rights can potentially happen. The four different focus areas have been identified based on the existing real estate dynamics at play in the LES, and as such the 'Scenario Zone' overlay should be used as a guideline for areas of intervention.

For the sake of simplicity, all land is under private developer ownership, other than the Baruch Campus (where NYCHA can exercise certain actions). In reality, it would belong to a variety of private and public owners.

Stakeholders

New York City Housing Authority (NYCHA)

Primary Objective: Sell air rights to developers who need it at $125 per sq ft. NYCHA is also responsible for maintaining atleast 20% affordability in the new/proposed developments.

Actions: Communicate with the city regarding the developer's building choices. Add infrastructure such as parks, community centers, etc. that can enhance Baruch Housing Campus.

Goals/Targets: Sell as many sq ft of air rights as possible. Maximum underused sale-able land = 800,000 sqft Maintain at least 20% of affordable units in the new/proposed construction. Improve the existing Baruch Housing stock and thereby increase the general livability in the area.

City of New York

Primary Objective: Allow for increased density in the area by issuing rezoning permits where required without decreasing the livability conditions in the neighborhood. Secondary objective is to maintain at least 20% of affordable units in the new developments.

Actions: Approve proposed development Approve for rezoning when proposed by the developer

Goals/Targets: Increase Density in LES, but do so with consideration for the nature of the neighborhood's urban fabric Increase affordability in LES

Private Developer

Primary Objective: To make profitable investments in Lower East Side.

Actions: Build profitable buildings Buy air rights from NYCHA Apply for re-zoning to the City/Municipality

Goals/Targets: Increase Density in LES, but do so with consideration for the nature of the neighborhood's urban fabric Increase affordability in LES.

Overlay: Zoning for receiver sites

As described above, receiver sites are considered when Built FAR < 50% Zoning FAR. We then add a color coding overlay to show the current maximum allowed building height (simplified as # of floors), that can be turned on and off in the game.

Overlay: Ownership

Note: For the sake of simplicity, all land is under private developer ownership, other than the Baruch Campus (where NYCHA can exercise certain actions). In reality, it would belong to a variety of private and public owners

Actions: Examples

The private developer, for instance, has various menus offering different building types, that are only appropriate to build in certain zones. The deploy session below will go through this process in more depth, but you can already see that each building has been coded as A/B where:

A: # allocated to current zoning (i.e. 8, 13, 15, 22) B: # allocated to the new desired building height.

Pictures 2 & 3 show a building that should not be built, because the current zoning does not allow it.

Function Values & Custom Function Values: screenshots

Indicators: screenshots

Private Developer's Budget

Summary

Stakeholder Score and Indicator Progress

The Showcase: Deployment Narrative by Kushan and Nico

"We played a session to explore the topic of TDR in one scenario area in the Lower East Side. Kushan Dave (MRP, Cornell), Nicolas Grefenstette (MRP, Cornell), Swati Sachdeva (Urban Designer, UC Berkeley) played each as one of three stakeholders (Respectively the developer, city & NYCHA). The session lasted 40 minutes, and we focused on the Scenario 4 area (around Houston Street). As a reminder, the scenario overlay should be treated as a guideline, but it doesn't need to be enforced. The decision for these four areas comes from our previous research looking at land use, economic and transportation corridors, as well as from comments from various professors and professionals in NYC.

What you will see below is the narrative for this session, followed by detailed screenshots depicting each stakeholders' actions. We encourage you to explore the game yourself, as scenarios can greatly differ in length & size (depending on the choice of buildings)".

The developer initiates the gameplay, by looking at the zoning/soft-site layer, identifying sites he might be interested in. By choosing to place a certain block, a prompt appears on the city's screen, asking him whether or not he will approve of the development (via permits). All stakeholders are aware of the impact of this building on various indicators (livability, affordability units, the quantity of air rights transferred and so on). At this point, the city should also be aware of the physical impact the developer's decision will have on the neighborhood. Before approving this building, stakeholders need to discuss the impact.

The first building is approved, and the developer chooses to look at a different site. This time, the site is already built, so he needs to demolish the existing building first. The first two actions are repeated, as different stakeholders discuss the suitability of each building development. In the end, the city had approved the maximum allowed number of developments (effectively using all 800,000 sq ft of underused development rights from Baruch Campus). Please note that at all times, NYCHA can match the profits made from the sell of development rights to the costs of building community & ecological infrastructure on campus, suggesting that the profits made should be reinvested into NYCHA campuses (i.e. we could have also looked at maintenance).

At the end of the session, each stakeholder can look at his performance metrics for different indicators. This stage is crucial in determining whether or not different goals were satisfactory. We choose not to beam a comparison chart at the end, since the focus needs to remain on the topic of TDR, rather than focusing on an arbitrarily set score for stakeholders.

Developer

Analysis of potential receiver sites

Closer study of the site

Again, the city approves! Eventually, several sites are proposed, and intra-stakeholder conversations start.

Summary of tables shows the progress

We can see how different actions affected indicators throughout the game - for instance, the dip in the total units built curve above is due to the demolition of old housing, which inevitably affects the market/affordable housing quantity & mix.

City of New York As you can picture, from the city's perspective, the role is mainly about regulation. Below, you will see what happens when the developer wanted to build a 15-storey building in a zone that only allows 13 floors (link to action from the developer's perspective, above)