lucky-parking icon indicating copy to clipboard operation
lucky-parking copied to clipboard

Add coordinates for missing lat/lon

Open gregpawin opened this issue 5 years ago • 8 comments

Overview

We need to add lat/long coordinates to the data set we get from the city so that a higher % of parking violations and summary statistics display on the map.

Details

Around 15% of data points do not have coordinates. Analyze these missing data points and identify what % we could reliably tag.

Action items

  • [x] Download the data and remove the data with lat/long to make the new data set
  • [ ] Analyze dataset and missing coordinate records
  • [ ] Geocode using address information in batches to avoid paid tier
  • [ ] Save code and analysis as Jupyter notebook in Notebooks folder of citation analysis branch
  • [ ] Save dataset to Google Drive (add Drive link in Resource section below)
  • [ ] Map the data
  • [ ] Identify which addresses did not get properly geocoded
  • [ ] Discuss results with the team

Resources/Instructions

  • Citation analysis branch for getting access to Lucky Parking's cleaned data README: https://github.com/hackforla/lucky-parking/tree/citation-analysis
  • Notebooks folder: https://github.com/hackforla/lucky-parking/tree/citation-analysis/notebooks
  • Google Drive Folder for Lat / Long analysis: https://drive.google.com/drive/u/0/folders/1IgPOBy86s3kcDJ5cG3afqoTz4BtRwjdX
  • Possible package to use: https://geocoder.readthedocs.io/
  • Tutorial: https://towardsdatascience.com/geocode-with-python-161ec1e62b89

gregpawin avatar Nov 16 '20 11:11 gregpawin

Hey is this for public? If yes, Can i grab?

Praveenk8051 avatar Feb 06 '21 17:02 Praveenk8051

Hey Praveen, sure go ahead. Please join our slack channel and come to our meetings on Monday night so we can discuss it.

gregpawin avatar Feb 06 '21 20:02 gregpawin

@gregpawin This issue has not had an update since August 3, 2021. If you are no longer working on this issue please let us know. If you are able to give any closing comments related to why this issue stopped being worked on or if there are any other notes that never got added to the issue. We would appreciate it. If you are still working on the issue, please provide update using these guidelines

  1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
  2. Blockers: "Difficulties or errors encountered."
  3. Availability: "How much time will you have this week to work on this issue?"
  4. ETA: "When do you expect this issue to be completed?"
  5. Pictures (if necessary): "Add any pictures that will help illustrate what you are working on."

MichelleRT avatar Mar 16 '22 18:03 MichelleRT

@Seymour100 mentioned that a third party might be taking on this task and updating the official dataset. Will keep tabs on it.

gregpawin avatar Oct 14 '22 00:10 gregpawin

Previous: Raw and processed compilations of the data have been generated for work on this ticket. The sample size was set to 1.0, so it should be all of the current data that we have. Current: In data exploration mode to better understand the data I have available to complete the ticket. Blockers: None at the moment

COlivas26 avatar Mar 14 '23 01:03 COlivas26