fix fill_empty method for field that end in XX or YYY #147
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
sambles
approved these changes
Oct 15, 2024
sambles
pushed a commit
that referenced
this pull request
Oct 31, 2024
* fix fill_empty method for field that end in XX or YYY
Merged
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.
fix default values for field ending in XX or YYY
Some OED field end with XX or YYY to allow users to specify several type of the same field (for example for GeogSchemeXX)
Because of the mismatch between the column name and the field name (GeogScheme1 vs GeogSchemeXX), default value were not applied.