Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Identify possible data model implementation #1

Open
lianilychee opened this issue Aug 7, 2022 · 0 comments
Open

Identify possible data model implementation #1

lianilychee opened this issue Aug 7, 2022 · 0 comments
Labels
Milestone

Comments

@lianilychee
Copy link
Member

Context

If awarded, the anti-displacement project will start in Fall 2022. In the anti-displacement project*, we have to identify areas** at-risk of Project Connect rail displacement.

*Project is in partnership with YWCA
**Area granularity to the “mailing addresses” level

Problem

We don’t know how to identify areas at-risk of Project Connect rail displacement. The city has made a displacement risk map, but the city’s map has a very binary evaluation of “at risk” — a neighborhood is either “at risk” or “not at risk.” There’s no nuance in-between.

Solution

In no particular order:

  • Identify the calculations and datasets that inform city’s displacement risk map
  • Identify established
    • transportation equity factors
    • displacement factors
  • Identify how to correlate this info into a working model

Acceptance criteria

  • A description of a data model that measures displacement risk (maybe formula?)
  • A rudimentary roadmap in order to create the data model (following the now/next/later framework)

Reference info

@lianilychee lianilychee added this to the Discovery milestone Aug 7, 2022
@lianilychee lianilychee added dev good first issue Good for newcomers and removed good first issue Good for newcomers dev labels Aug 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
No open projects
Status: No status
Development

No branches or pull requests

1 participant