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

Road data script troubleshooting and fixes (2024 Q3) #317

Closed
MichaelAGRC opened this issue Dec 19, 2023 · 8 comments
Closed

Road data script troubleshooting and fixes (2024 Q3) #317

MichaelAGRC opened this issue Dec 19, 2023 · 8 comments
Assignees
Labels
type: ongoing This is an ongoing task that is completed multiple times

Comments

@MichaelAGRC
Copy link
Member

Benefit

As road data comes in from the counties, occasionally they change their schema or add values to the data that is outside the expected domain. This causes our scripts to fail. Troubleshooting these error messages and fixing the issues will speed up the monthly road update process.

Acceptance Criteria

Getting the scripts to run after they throw an error message. This will require either altering the scripts a bit or the data.

Notes

Notes on troubleshooting script errors
The majority of the time, when a script throws an error it's because the county changed the schema. This could be a change in expected domain values or a field name change. Our county ETL scripts are hard-coded to expect certain values and when they change, the script throws an error.

The troubleshooting part is determining what changed and how to proceed. Here are some steps to take when troubleshooting and then fixing the issue:

Check the error message. It will often inform you of the unexpected value (domain change) or a missing or renamed field name.
Based on the error message, determine if it's easier to fix/update the script or the county data. Oftentimes, it's quicker to alter the county's data (fixing the wonky field values or the missing field). Other times, it's easier to alter the script to accommodate their new schema. It's a case-by-case situation.
When updating scripts, if the issue occurs in Step 1 or Step 3 you can update the script directly. If the issue occurs in Step 2, feel free to work with Greg the first couple times as these scripts are a slightly more complex, but not out of scope. Essentially, if it occurs in Step 2, you'll need to look for the county's name in UtransETL_FieldMappingFunctions.py and make the change there.

Risks

No response

Issue Reference

refs #

@MichaelAGRC MichaelAGRC self-assigned this Dec 19, 2023
@steveoh steveoh added the type: ongoing This is an ongoing task that is completed multiple times label Dec 19, 2023
@MichaelAGRC
Copy link
Member Author

MichaelAGRC commented Jan 8, 2024

Sprint 1

  • Sevier
  • Carbon

@MichaelAGRC
Copy link
Member Author

MichaelAGRC commented Jan 11, 2024

All counties processed for sprint 1. Davis was not processed - waiting on feature update on arcmap tool. Ref #316

@MichaelAGRC MichaelAGRC changed the title Road data and script troubleshooting and fixes (2024 Q3) Road data script troubleshooting and fixes (2024 Q3) Jan 11, 2024
@steveoh
Copy link
Member

steveoh commented Jan 16, 2024

@gregbunce are you planning on updating the arcmap tool quickly to allow for the counties to get processed if michael is waiting on it?

@gregbunce
Copy link

yeah, my plan is to have it updated before michael processes the roads next month.

@MichaelAGRC
Copy link
Member Author

MichaelAGRC commented Feb 7, 2024

Code wasn't quite ready and required further testing and installing. As such, Grand will be pushed to February processing.

@MichaelAGRC
Copy link
Member Author

Also, Davis will be processed using updated tool during sprint 3/4.

@MichaelAGRC
Copy link
Member Author

Sprint 4 Notes

Grand county is throwing an unknown error during the first script. Will need to work with @gregbunce to resolve the issue.

@MichaelAGRC
Copy link
Member Author

This is closed. New issue created for Q4.

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