Intro

Produce a CSV with a generic zoning code assigned to every parcel in the SF Bay Area in 2010.

In the process, set up a database of Bay Area land use regulation.

Requirements

GNU Make, PostGIS 2.1, Postgres 9.3, GDAL 1.11 or >, Amazon CLI

Setting up PostgreSQL--Example

sudo -u postgres createdb sf_bayarea_landuse
sudo -u postgres psql sf_bayarea_landuse -c "CREATE USER ****** WITH PASSWORD '******';"
sudo -u postgres psql sf_bayarea_landuse -c "GRANT ALL PRIVILEGES ON DATABASE sf_bayarea_landuse to ******;
sudo -u postgres psql sf_bayarea_landuse -c "CREATE EXTENSION postgis;"
sudo -u postgres psql sf_bayarea_landuse -c "CREATE EXTENSION postgis_topology;"
sudo -u postgres psql sf_bayarea_landuse -c "GRANT ALL PRIVILEGES ON DATABASE sf_bayarea_landuse to ******;

Usage

The Makefile contains pointers to what data is needed, where to get it, scripts to load it into Postgres, and scripts to join source parcel and zoning data.

In general we have treated the Makefile as the documentation of the data process. So start there if you need to change something. It will be closer to the data/process than this readme.

If you already have the environment set up, then you can simply type:

make zoning_parcels.csv

This will download and load the necessary data (excepting parcels) into Postgres, and then assign a Zoning ID to the parcels. Parcels are now expected to be in the database, as output by the script here.

Fields in the zoning_parcels table:

column name	description
geom_id	the geometry based identifier for a parcel as output by Spandex
zoning_id	the zoning id for a parcel as found in the zoning_lookup.csv
proportion	coverage/overlap with zoning code for parcel
tablename	which source zoning file/tablename was assigned to this parcel
no_dev	site will not be developed in urbansim

The zoning_id column in this table can be used to look up the qualities of zoning relevant to UrbanSim, such as those in the table below. See the lookup table for more details.