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

Address Point Monthly Update (FY24 Q4) #350

Closed
ZachBeck opened this issue Mar 25, 2024 · 11 comments
Closed

Address Point Monthly Update (FY24 Q4) #350

ZachBeck opened this issue Mar 25, 2024 · 11 comments
Assignees
Labels
type: ongoing This is an ongoing task that is completed multiple times

Comments

@ZachBeck
Copy link
Member

Benefit

Current address points for Utah.

Acceptance Criteria

"Big 5" counties updated monthly along with rural counties who have submitted address points.

Notes

No response

Risks

Success depends on county participation, especially from rural counties. If county address points aren't received by the UGRC in a timely manner our update process suffers.

Issue Reference

refs #

@ZachBeck ZachBeck self-assigned this Mar 25, 2024
@ZachBeck ZachBeck added the type: ongoing This is an ongoing task that is completed multiple times label Mar 25, 2024
@nathankota nathankota changed the title Address Point Monthly Update Address Point Monthly Update (FY24 Q4) Mar 25, 2024
@nathankota
Copy link
Contributor

Sprint 2

@steveoh
Copy link
Member

steveoh commented Apr 16, 2024

What is wrong with the address point updates? Fixing those would be a pull request. How does it relate to #377?

@ZachBeck
Copy link
Member Author

@steveoh it's just updating the update history list, I noticed February and March were missing. I'll get it fixed.

@ZachBeck
Copy link
Member Author

Address point updates for April are ongoing. Waiting for some counties to send points, Summit has changed their schema which means a rewrite of their ETL script.

@nathankota
Copy link
Contributor

nathankota commented Apr 30, 2024

Sprint 3

  • Investigate Summit County incoming data and attempt to resolve some associated issues
    • affects Sweeper, Address Parser, and likely other processes - submit GitHub issues in respective repositories, as needed
  • Ultimately need to rewrite the ETL script

@steveoh
Copy link
Member

steveoh commented Apr 30, 2024

  • affects Sweeper, Address Parser, and likely other processes - submit GitHub issues in respective repositories, as needed

How does this affect sweeper?
What is the address parser?
Do we have a decent understanding of the other processes?

@ZachBeck
Copy link
Member Author

from sweeper.address_parser import Address is returning incorrect prefix directions when parsing an address like 2504 E South Fork Canyon Rd (returns S for the prefix). I've noticed some other issues as well that I'll put in a PR.

@steveoh
Copy link
Member

steveoh commented Apr 30, 2024

hmm, that's a model trained on Utah data. We might need to update the training as we don't own the logic to fix issues like that. @stdavis what do you think?

@ZachBeck
Copy link
Member Author

ZachBeck commented Jun 4, 2024

May address point updates are complete.

@ZachBeck
Copy link
Member Author

ZachBeck commented Jul 1, 2024

June address points are complete 4/1

@ZachBeck
Copy link
Member Author

ZachBeck commented Jul 1, 2024

done

@ZachBeck ZachBeck closed this as completed Jul 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: ongoing This is an ongoing task that is completed multiple times
Projects
Status: Done
Development

No branches or pull requests

3 participants