Address Point Monthly Update (FY24 Q4)

agrc / planning-queue

A place to manage issues that do not have a dedicated repository or code... yet.

MIT License

0 stars 0 forks source link

Address Point Monthly Update (FY24 Q4) #350

Closed ZachBeck closed 1 day ago

ZachBeck commented 3 months ago

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 #

nathankota commented 2 months ago

Sprint 2

Monthly address point updates are not correct on the website (#377), which needs some attention

steveoh commented 2 months ago

Monthly address point updates are not correct on the website (UGRC website phase 2 #377), which needs some attention

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

ZachBeck commented 2 months ago

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

ZachBeck commented 2 months ago

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 commented 2 months ago

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 commented 2 months ago

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 commented 2 months ago

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 commented 2 months ago

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 commented 4 weeks ago

May address point updates are complete.

ZachBeck commented 1 day ago

June address points are complete 4/1

ZachBeck commented 1 day ago

done