Change metadata handling to be compatible with OpenVBI #66
Conversation
This file contains hidden or 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
…compatible B-12 metadata
…t OpenVBI-compatible metadata; Add migration script for converting to OpenVBI compatible metadata
|
@HaleyAddison Please give this PR as well as issue #65 a look when you have a chance as this will require changes the metadata files you use in your workflows. Let me know if you have any questions. Thanks! |
…N conversion since these are not required elements and we are now deep merging user metadata with the template, so non-required elements should not be in the template
brian-r-calder
approved these changes
May 1, 2025
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 changes metadata handling in
wibl-pythonwhen WIBL files are processed into GeoJSON files, as described in #65. This represents initial work to achieve compatibility with OpenVBI by implementing similar metadata handling directly inwibl-pythoncode (rather than making OpenVBI a dependency ofwibl-pythonand using OpenVBI's metadata handling code directly). This PR also includes an update to documentation in README.md describing the metadata format change, and provides a simple script to convert to the new OpenVBI-compatible format.In future work, the OpenVBI metadata handling code can be used directly by
wibl-python. However, doing so will ideally require that OpenVBI first be packaged via conda-forge (sincewibl-pythonis also packaged as conda-forge package). However, until this conda packaging work has been done for OpenVBI, the current PR will ensure compatibility.