Analysis of Your Choice
Choose one of the six approved methods. Each option opens a separate workbench with that method selected, so you can focus on the decision and evidence it needs.
Due November 18 at the start of class
Requirements and gradingChoose one method
Downtown Vacancy and Opportunity
Useful when: Property, block, reuse, storefront, or activation decisions.
Plan to use: Field observation, parcel or address list, confirmed ownership or status, plans, and market or reuse context.
Keep in mind: Do not infer vacancy, ownership, condition, or feasibility from appearance alone.
Community Health and Access
Useful when: Access to services, food, recreation, care, or daily needs.
Plan to use: Population, destinations, travel conditions, service coverage, barriers, and affected groups.
Keep in mind: Do not make clinical claims or equate proximity with usable access.
Industry and Workforce
Useful when: Sector, employer, training, site, supply-chain, or workforce pathway decisions.
Plan to use: Employment and sector data, training capacity, sites, infrastructure, commuting, housing, and partner evidence.
Keep in mind: Do not invent employer commitments, demand, wages, or site readiness.
Multimodal Mobility
Useful when: Walking, biking, transit, crossings, safety, and destination connections.
Plan to use: Field audit, network and crash context, destinations, right-of-way, agency guidance, and users.
Keep in mind: A screening audit is not engineering design or a safety guarantee.
Street Master Plan Comparison
Useful when: Comparing two corridors or street segments for connectivity, frontage, safety, and public-realm action.
Plan to use: Street geometry, network context, frontage, field observation, users, destinations, and implementation constraints.
Keep in mind: This is optional and should not become a full corridor plan without scope approval.
Coded or Community-Use Tool
Useful when: A recurring local decision or task that can be improved by a modest accessible tool.
Plan to use: Defined user, current workflow, inputs, transparent rules, test cases, maintenance, and handoff capacity.
Keep in mind: Do not build a tool before confirming the user, decision, data, and maintenance responsibility.