Feat/extract notebook metadata#43
Open
firzaariany wants to merge 20 commits into
Open
Conversation
a657297 to
59059ea
Compare
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
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.
Summary
This PR contributes to #32 and is ready for review
What's changed
Notebook metadata convention
templates/: provide dict for metadata, set tagged cellspreview_imageandnotebook_metadatanotebooks/sentinel/sentinel-2/fire_and_disaster_monitoring/fire_boundary.ipynb: as a working example with metadata dictRecord generator and image extraction
algorithm_registration/populate_record.py: Python CLI to produce thumbnail and preview pictures, and to create OGC API records from tagged cellsalgorithm_registration/records_template.json: OGC API record templateHow to test this
fire_boundary.ipynbfrom top to bottomdevelopmentseed/apex_algorithmsrepoProblems
When running QA tests I received this error for
fire_boundaryrecords. It checks if the records exist in the main branch ofESA-APEx/apex_algorithms, which wouldn't be if the commit withfire_boundaryrecords are not yet merged to main.