Skip to content

Conversation

@rushirajnenuji
Copy link
Member

No description provided.

trey-stafford and others added 14 commits October 23, 2025 14:36
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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants