slack channel: #datasci-housingreport

This is a project of the Data Science Working Group at Code for San Francisco

The original ask, or how this project got started.

These DSWG members are contributors to this project, and how to get in touch with us on slack:

1. Create a data model that can span several quarters, adjusting for the name mismatch
2. draw data from the Socrata API dynamically
3. come up with detailed UI design
4. questions to explore:

• how many units are being built per neighborhood per time period?
  • how many of those are affordable?
• how many projects are being built per neighbood
• how much space designated as "light industrial" is being gained/lost per neighboorhood?
• projects approved and filed over time:
  • what happens to the planning process per neighborhood
  • when were projects filed/approved/started/completed?
• size of project vs speed of getting on market?
• a way to gauge compliance with Nov 2016's Measure X

The pipeline dataset
The pipeline website
An old report
an obsolete column mapping google doc

See data/README.MD for details about the data

• 2011
• 2012
• 2013
• 2014
• 2015

• https://data.sfgov.org/Housing-and-Buildings/Mayor-s-Office-of-Housing-and-Community-Developmen/9rdx-httc
• https://data.sfgov.org/Housing-and-Buildings/Affordable-Housing-Pipeline/aaxw-2cb8

Entitlement Status: 0 = Under Planning Review, -1 = Approved By Planning
APN: Assessor Parcel Number (blocklot, blklot)
MIPS: Managerial, Information, Professional Services. (Same as Office)
CIE: Cultural, Institutional, Educational
PDR: Production, Distribution, Repair