-
Notifications
You must be signed in to change notification settings - Fork 0
Feat 69 extend viz workflow #114
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Draft
rushirajnenuji
wants to merge
14
commits into
main
Choose a base branch
from
feat-69-extend-viz-workflow
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
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
This ensures that if we pass an fsspec-compatible string representing a remote recipe directory (via GitHub) via the CLI, that directory gets copied to a local staging directory. This lets all other code that interacts with the recipe directory to access it directly on disk, without needing to know anything about the source file system protocol. Right now the staging directory is a tempdir that gets cleaned up at the end of program execution. I think that when we move to an architecture with a service in front of argo deployed to k8s, that we might want to stage the recpie to a PVC for archival/provenance. It can live in the same directory that workflow outputs live.
Rename makes it more clear that this function returns, as a json string, configuration for the viz workflow. Adds checks to ensure that configuration from a file is valid json. An error is raised otherwise.
Move to latest pdgworkflow package
Batch up file paths
Add support to run rasterization and 3dtiles
Use the default ogdc-runner image
Add rasterization and 3dtiles task to DAG execution
Add viz-workflow related docs
rushirajnenuji
added a commit
that referenced
this pull request
Dec 8, 2025
Add support for rasterization and 3dtiles initial work on this PR #114
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.
No description provided.