Skip to content
Michael Reilly edited this page Jun 14, 2018 · 3 revisions

Try out some policy levers. Do this in a branch. Recall that BAUS has scenarios. By default BAUS.py runs scenario 4 if you don't specify (you can change the default in settings.yaml). You can change any scenario you want but make sure you are running and changing the same one or it will get dull :) (you can also double check the scenario number in the log file).

Change Zoning

  • Edit bayarea_urbansim/data/zoning_mods_4.csv on GitHub or locally (using a text editor or open the csv in the excel and resave
  • Each zoningmodcat is a combo of the things in the columns that follow it (jurisdiction, pda, tpp, exp, opp). Focus on just first 3. So if you change a row that has a particular combo of these it changes the zoning for thsoe parcels. For instance, 06000BER3brt1NANA is the city of Berkeley (sadly, that is the FIPS number--you can look these up quickly online or find a list), it is Berkeley's PDA #3, and it has top quality BRT access. You could change dua_up to a new value and that will increase the allowable dwelling units per acre which may spur the developer model to build more there. There are some existing values in this table that were need to get the Plan to work. Try your own. Get used to typical DUAs. There are some guides online. 16 is the rule of thumb minimum for transit to "work" but you need more than 50 for heavy rail.
  • After running look for shifts in where things get built in the 2040 topsheet or in the 2040 superdistricts summary

Change Inclusionary Zoning

Jobs-Housing Linkage Fee

Clone this wiki locally