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

Feature: time to nth nearest ("dual" accessibility) #875

Closed
ansoncfit opened this issue Mar 20, 2023 · 2 comments · Fixed by #884
Closed

Feature: time to nth nearest ("dual" accessibility) #875

ansoncfit opened this issue Mar 20, 2023 · 2 comments · Fixed by #884
Assignees

Comments

@ansoncfit
Copy link
Member

Users from multiple organizations in California have requested "dual" accessibility measures (e.g. time required to reach some threshold number of opportunities, such as one school or three grocery stores). The TransitCenter Equity Dashboard includes these types of measures (specifically, the time needed to reach the 3rd Grocery Store, 3rd Pharmacy, 1st Urgent Care, 1st Hospital, and 1st College/University).

@ansoncfit
Copy link
Member Author

We also had a recent request for this feature in the Netherlands.

@abyrd
Copy link
Member

abyrd commented Aug 17, 2023

Users will often use this feature with many freeform destination layers at once (TransitCenter uses five layers). So we should explore allowing multiple freeform destinations in one regional analysis which may allow big efficiency gains (not running multiple regional analyses), or at least update documentation to explain why gridded destinations or combining all freeform destinations into a single layer is beneficial here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants