-
-
Notifications
You must be signed in to change notification settings - Fork 64
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
Adjust data cleaning script to prune data points outside of LA Neighborhood Districts #1708
Comments
Adjusting this ticket, most likely @mru-hub will pick this up once there is enough instructions to get started |
Note: I'm realizing that we may need to do work to prune old data. Adding a check into our cleaning logic will simply stop new data (e.g. requests falling outside NC boundaries) from being added -- we'll still need to handle old data that has the same problem. Follow up ticket: Make sure we are cleaning 2023 and prior data with the same logic |
Note for Ryan: provide an example resource of checking if a Lat/Long is within a provided boundary in Duckdb |
This ticket is ready to be picked up |
@mru-hub's update from this previous week is on the PR: #1736 (comment) |
Latest PR: #1744 |
Update: added dependency for needing 2024 NC boundary json file |
Dependency
Overview
We need to remove 311 Data service requests on our map that do not fall within the boundaries of a Neighborhood Council since they are inaccessible and mostly confuse the users
Action Items
Resources/Instructions
Screenshot of requests outside NC boundaries
Last Updated Date 10/23/2024:
Useful Links
The text was updated successfully, but these errors were encountered: