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

Equity Adjustments #656

Closed
awikstrom-ladot opened this issue Nov 20, 2020 · 6 comments · Fixed by #675
Closed

Equity Adjustments #656

awikstrom-ladot opened this issue Nov 20, 2020 · 6 comments · Fixed by #675
Assignees
Labels
enhancement Release Note: Shows as visual or user experience Enhancement feature: missing level: missing priority: MUST HAVE role: database Database Development Task size: missing

Comments

@awikstrom-ladot
Copy link

awikstrom-ladot commented Nov 20, 2020

Change maximum amounts of points for certain strategies if the project fulfills equity obligations. Most changes are to grant additional TDM points on top of existing maximum point values if developer allows the general public to use the amenity instead of just the people living/working at the finished project site.

Adjust the following strategies' point values as indicated:

Bicycle Facilities 5: Changing and Shower Facilities - 5 Max Points
N/A - 0 points
Private = 2 points
Publicly Accessible = 4 points
Publicly Accessible AND in a disadvantaged area = 5 points

Car Sharing 1: Car Share Parking - 4 Max Points
N/A - 0 points
Private = 3 points
Publicly Accessible = 4 points

Information 1: Transit Displays - 3 Max Points
N/A - 0 points
Internally visible = 2 points
Publically visible = 3 points

Transit Access 1: Neighborhood Shuttles/Microtransit Service - 9 Max Points
N/A - 0 points
Does not connect to HQTA = 3
Does not connect and if publicly available = 6 (+3)
Does not connect and if publicly available and in disadvantaged area = 7 (+4)
Connects to HQTA = 5
Connects to HQTA and if publicly available = 8 (+3)
Connects to HQTA and if publicly available and in disadvantaged area = 9 (+4)

@KPHowley @Dsomers74

@Dsomers74
Copy link
Member

@KPHowley I updated the issue based on your questions.

@entrotech entrotech self-assigned this Dec 7, 2020
@entrotech entrotech added role: database Database Development Task enhancement Release Note: Shows as visual or user experience Enhancement labels Dec 7, 2020
@entrotech
Copy link
Member

image

@Dsomers74
Copy link
Member

Dsomers74 commented Dec 8, 2020

@entrotech Overall, it works, though the Transit Access 1 points need further adjustment. I realize I didn't articulate the points well in my instructions. I put the delta point differential from the base in the parenthesis in order to provide if the option if there were a check box for either 'publicly available' or 'publicly available and in disadvantaged area'

For example, publicly available would be 3 additional points for a total 6 points (3 + 3) if the service does not connect to HQTA and 8 points if it does (5 + 3). The parentheses were only internal references. Sorry for the confusion.

Revise the following strategies' point values as indicated:

Transit Access 1: Neighborhood Shuttles/Microtransit Service - 3-9 Possible Points
N/A - 0 points
Does not connect to HQTA = 3
Does not connect and if publicly available = 6
Does not connect and if publicly available and in disadvantaged area = 7
Connects to HQTA = 5
Connects to HQTA and if publicly available = 8
Connects to HQTA and if publicly available and in disadvantaged area = 9

@Dsomers74
Copy link
Member

Dsomers74 commented Dec 8, 2020 via email

@entrotech
Copy link
Member

@Dsomers74 Got it. I re-deployed to the tdmdev site. Can you verify that it is correct now?

@Dsomers74
Copy link
Member

Dsomers74 commented Dec 9, 2020 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Release Note: Shows as visual or user experience Enhancement feature: missing level: missing priority: MUST HAVE role: database Database Development Task size: missing
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

6 participants