feature/issue-52 Remove partial_f from data columns to obscure #53
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
torimcd
changed the title
frankinspace
approved these changes
Dec 4, 2023
# for free
to join this conversation on GitHub.
Already have an account?
# 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.
Github Issue: #52 Remove partial_f from data columns to obscure
Description
Running the load data script in UAT often fails due to partial_f not being represented consistently in the shapefiles. This field is a flag indicating partial coverage and does not need to be obscured.
Overview of work done
Removed partial_f from list of fields to obscure
Overview of verification done
Unit tests pass
Overview of integration done
PR checklist:
See Pull Request Review Checklist for pointers on reviewing this pull request