Validation scripts #51
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
stdavis
previously approved these changes
Aug 8, 2024
|
Ok, I've updated it to include a separate schedule for the validation logic (which entailed updating the triggering function as per gen2 Cloud Function instructions). The check year is set automatically, and the validation sheet is emailed using Supervisor. |
steveoh
approved these changes
Aug 12, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR focuses on a validation script that generates a csv comparing changes year-over year for several metrics by facility, county, and statewide. This will be run manually and locally as needed, usually in spring as reports for the previous year are submitted.
The output will allow WMRC staff to identify large discrepancies year to year that might indicate typos or other situations that could make it difficult accurately identify long-term trends.
Tucked in the middle of this is a change to a live field name that got it's name truncated in length by AGOL during a manual update to add a new facility type.