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

Add reporting on city councils #941

Closed
8 tasks
mattyweb opened this issue Feb 10, 2021 · 3 comments
Closed
8 tasks

Add reporting on city councils #941

mattyweb opened this issue Feb 10, 2021 · 3 comments
Labels
Dependency An issue that includes dependencies P-feature: Reports Role: Backend Related to API or other server-side work Size: Missing Tech Stack: Old

Comments

@mattyweb
Copy link
Collaborator

mattyweb commented Feb 10, 2021

Dependency

post v2
get District Types API from Data Science community of practice hackforla/data-science#118

Overview

The goal of this feature is for users to be able to report on service requests within their City Council districts.

Assumptions

  1. city will provide city council geometries in a single GeoJSON file
  2. city councils will have a name and a shape
  3. we can use this: https://geohub.lacity.org/datasets/la-city-council-districts-adopted-2012

Development Work

  • Add city council table with ids/names (similar to the new councils table) | Backend | Need to modify migration that currently creates the councils table.
  • New migration to add geometries for city councils | Backend | We currently have long and lat columns and i think need to transform these into points
  • Add metadata endpoint for city councils (similar to the new councils endpoint) | Backend |  
  • New city council open-requests/counts endpoints | Backend | Not clear yet whether the counts would be included in /open-requests or would come from a separate endpoint
  • Modify /comparison endpoints and underlying services to accept list of city councils | Backend | Do we need city councils in the comparison reports? They are not uniform, contiguous, etc.
  • Include city council metadata in data we initially load from server | Frontend | This would be included in the general refactor we've been discussing where we load metadata from the API, and store it in redux, rather than taking it from a constants file
  • Add city council geojson to map as another layer | Frontend |  
  • Modify comparison-tool dropdowns to allow city council selection | Frontend |  

Resources

From the city of LA's open data website
Business Improvement Districts Map Interface
A business improvement district is a geographically defined area within the City of Los Angeles, in which services, activities and programs are paid for through a special assessment which is charged to all members within the district in order to equitably distribute the benefits received and the costs incurred to provide the agreed-upon services, activities and programs. The assessment money is collected by the City or by the County through a special contractual arrangement with the city. Because the assessment funds collected in a given district cannot legally be spent outside of that BID, the City creates a trust fund for each BID, with funds periodically released to support operations.

@mattyweb mattyweb added Enhancement New feature or request Role: Frontend React front end work Role: Backend Related to API or other server-side work Role: DevOps infrastructure, CI or related work labels Feb 10, 2021
@mattyweb
Copy link
Collaborator Author

Some commentary here: I'm not sure the value of including city councils is worth the confusion they cause. City councils do not share borders with Neighborhoods. That is, part of a Neighborhood A will be in City Council X and part will be in City Council Y. It's really a completely different way of mapping onto the data. Given more work to support both, supporting both would add confusion and our target is neighborhood councils it seems that just including Neighborhoods would be the better choice.

@mattyweb mattyweb added the Needs More Info Request for more info...Issue not clear label Mar 2, 2021
@github-actions

This comment was marked as off-topic.

@github-actions github-actions bot added the Stale label Jun 1, 2021
@EchoProject EchoProject added Role: Product Management and removed Role: Frontend React front end work Role: Backend Related to API or other server-side work Needs More Info Request for more info...Issue not clear Role: DevOps infrastructure, CI or related work Stale Feature: Missing labels Oct 14, 2021
@EchoProject
Copy link
Contributor

Adding this Issue to items for review for the product roadmap.

@ExperimentsInHonesty ExperimentsInHonesty added this to the Post v2 milestone Nov 9, 2021
@EchoProject EchoProject added Dependency An issue that includes dependencies and removed Milestone: Missing labels Nov 9, 2021
@EchoProject EchoProject added Role: Backend Related to API or other server-side work P-feature: Reports and removed Enhancement New feature or request Role: Product Management labels May 13, 2022
@EchoProject EchoProject removed this from the Post v2 milestone Dec 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Dependency An issue that includes dependencies P-feature: Reports Role: Backend Related to API or other server-side work Size: Missing Tech Stack: Old
Projects
Status: Done (without merge)
Development

No branches or pull requests

5 participants