hackforla / hackforla/311-data

PRD - Obtain Most Recent NC Boundary Shapefile from DONE

Open
#1,897 7 comments 0 reactions 0 assignees View on GitHub
Complexity: Small Feature: Communication p-feature: data p-feature: Map Question ready for org rep Role: Product Management size: 1pt
Dominant language
JavaScript
Stars
73
Forks
74
PR merge metrics
No merged PRs in 30d

Description

### Overview

We need to update our Neighborhood Council (NC) boundary shapefiles because Service Requests (SR) are appearing in incorrect Neighborhood Councils, causing users to be confused if the map is showing accurate data.

### More Info
- We are noticing that some Service Requests are appearing outside the boundaries for their designated Neighborhood Councils (see Resources: Example of SRs appearing outside of NC Boundary)
- This observation suggests two possibilities:
- Our shapefiles are out of date and are failing to encapsulate the true area for which SRs can appear
- The 311 Data portal allows users to report a 311 Service Request where the specified address falls well-beyond the NC's boundaries

### Action Items
- [ ] Check to see if you can create a Service Request for a particular Neighborhood Council AND provide an address that falls well-beyond that NC's boundaries
- [ ] if so, create dev ticket for adopting the pruning logic in #1708, see Resources
- [ ] Obtain Contact for DONE
- [ ] Ask if there is a more recent version than the 2018 boundary data
- [ ] if so, ask them to email it to us
- [ ] (optional) ask to have ITA upload this version of the shapefiles to the LA City Open Data portal

#### Ticket Bookkeeping
- https://github.com/hackforla/311-data/issues/1814
- [ ] remove the dependency label
- [ ] move the ticket to New Issue Approval
- [ ] add "ready for dev lead" label

### References
- Related ticket: https://github.com/hackforla/311-data/issues/1708
- This ticket implemented Python to prune data that falls beyond NC boundary, however it is only useful for our Huggingface cron-job.
- We may need another dev ticket to adopt this logic into our frontend React if we cannot guarantee that data is being pruned at the source

Example of SRs appearing outside NC Boundary

Observe that some SRs are "floating out in space", rather than enclosed within a nearby NC's boundaries

![Image](https://github.com/user-attachments/assets/4c8ff55b-a6ca-459f-8c9d-59390fb68573)


- [Link to Los Angeles 311 Data portal](https://myla311.lacity.org/portal/faces/home;jsessionid=BWHsyfcIG8gDOqjcpsA2UH8v2ucrTD9--3dGQ9JqI5I9gYfUCjKx!-2086054008!1471208986?_afrLoop=8273789480585001&_afrWindowMode=0&_afrWindowId=null&_adf.ctrl-state=19mlaqel2e_1#!%40%40%3F_afrWindowId%3Dnull%26_afrLoop%3D8273789480585001%26_afrWindowMode%3D0%26_adf.ctrl-state%3D19mlaqel2e_5)
- Use this to determine if users are allowed to open SRs with an address that falls well-beyond the bounds of that Neighborhood Council
- [Link to LA City Open Data portal](https://data.lacity.org/)

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.