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

Implement community area metric for taxi trips #115

Open
2 tasks done
vingkan opened this issue Jul 23, 2021 · 1 comment
Open
2 tasks done

Implement community area metric for taxi trips #115

vingkan opened this issue Jul 23, 2021 · 1 comment
Assignees
Labels
api Work for backend API enhancement New feature or request

Comments

@vingkan
Copy link
Contributor

vingkan commented Jul 23, 2021

  • Metric Name: taxi_pickups_2021
  • Based on Table: taxitrips

Total number of taxi pickups per community area in 2021. Can also add number of dropoffs per community area.

  • Where will this metric be used in the app?
    • Community Area View
  • Which endpoint file should the metric be added to?
    • For community area metrics: api/endpoints/community.py

Read the documentation on how to add a new metric:

This task will involve at least two pull requests:

  • Implement metric (possibly including unit tests)
  • Publish metric (add to existing endpoint in backend and to config in frontend)

Once published, we can add another metric or move on to adding a data question in the frontend.

@vingkan vingkan added enhancement New feature or request api Work for backend API labels Jul 23, 2021
@vingkan
Copy link
Contributor Author

vingkan commented Jul 23, 2021

@alkatoutl @divyashie If you prefer, you could also implement a timeline metric for number of taxi trips per day or per week, but since we only have some of the 2021 data loaded, I thought it would be good to start with a per-community area metric.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api Work for backend API enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants